225066 2021-04-26 12:06:56 -0700 AX: Determine correct behavior for Unicode Private Use Area characters 2025-02-03 15:57:14 -0800 1 1 1 Unclassified WebKit Accessibility WebKit Nightly Build All All NEW https://bugs.webkit.org/show_bug.cgi?id=184586 InRadar P2 Normal --- 1 jcraig webkit-unassigned ap mmaxfield vitor.roriz webkit-bug-importer wenson_hsieh oldest_to_newest 1754294 0 jcraig 2021-04-26 12:06:56 -0700 The accessibility behavior for Unicode's private use area https://www.compart.com/en/unicode/block/U+E000 is currently ambiguous. Some web icon font packages are using (possibly misusing) this area for custom icon fonts... For example, FontAwesome uses U+F700 as an "otter" icon... https://fontawesome.com/icons?d=gallery&p=2&q=otter&c=animals FWIW, despite the FontAwesome site claiming "Accessibility-Minded, Font Awesome loves screen readers!" it does not appear that they've attempted to make it accessible, so I would not expect VoiceOver to speak "Otter" However, VoiceOver speaks literally "link " , but pronounces it as "link Up Arrow" and renders to the VO caption panel as "link ↑"). This also isn't right, so its worth investigating the behavior. It's not immediately apparent to me where the replacement "↑" character or its spoken "Up Arrow" string is coming from. https://www.compart.com/en/unicode/U+F700 I get the same behavior with both Alex and Samantha voices, so it doesn't appear to be coming from the speech engine either. 1754295 1 webkit-bug-importer 2021-04-26 12:07:12 -0700 <rdar://problem/77169314> 1754306 2 jcraig 2021-04-26 12:23:33 -0700 Related to bug 159022