Having done some further reading, according to the spec (http://www.w3.org/TR/wai-aria/roles#textalternativecomputation point 3) JAWS is actually doing the right thing here. Font awesome claims to be screen reader accessible, but it appears this accessibility is based on screen readers not rendering text ::pseudo elements, which practically has been true for a while but isn't what the spec dictates (and isn't what JAWS is now doing).
Adding role=presentation or aria=hidden (or both) might be the only way to consistently alleviate the issue (see http://john.foliot.ca/aria- hidden/) for a discussion of which of those would be appropriate. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1484781 Title: Font Awesome icons cause screen reader weirdness Status in Mahara: New Bug description: With the new Font Awesome icons in Mahara 15.10, the JAWS screen reader reads each icon as "Unknown character". This also messes up link order when using JAWS' "List links" feature. Since the icons use the :before CSS pseudo-element, I suspect this is unfixable (and a problem with JAWS), but it's worth looking into whether there is a solution which allows Font Awesome icons to be used but doesn't compromise screen reader accessibility. It's also worth testing with NVDA to see if the same problem exists. Affects latest master To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1484781/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
