E-mail List Archives
Re: Font Icons and Pseudo-elements
From: Patrick H. Lauke
Date: Apr 13, 2016 12:04PM
- Next message: Morin, Gary (NIH/OD) [E]: "Re: should you or should you not tell partners about theaccessibility issues on their sites?"
- Previous message: Joseph Sherman: "Re: Font Icons and Pseudo-elements"
- Next message in Thread: deborah.kaplan@suberic.net: "Re: Font Icons and Pseudo-elements"
- Previous message in Thread: Joseph Sherman: "Re: Font Icons and Pseudo-elements"
- View all messages in this Thread
On 13/04/2016 18:51, Joseph Sherman wrote:
> I read that guide, but it's not correct. In the section on "If an
> icon represents an interactive element", it relies on the Title
> attribute to provide an accessible alternative name for the element.
> In my testing, the screen reader just says "link" and does not read
> the Title when: using JAWS and the "H" key; or having NVDA or JAWS
> list the elements; or when on a Mac using VoiceOver.
According to the Name Computation algorithm, title should be taken into
account (as a last resort) to provide an accessible name
https://www.w3.org/TR/wai-aria/roles#textalternativecomputation - it
could be argued that AT that do not use/expose title are not quite
following the recommended algorithm.
Of course, there are more elegant ways of providing the extra label,
such as using actual aria-label, or using the same approach as in the
previous section of that guide, namely the visually hidden content.
I may push for an expanded explanation/suggestion in that guide, to
cover some alternatives.
P
>
>
> Joseph
>
>
>
>
- Next message: Morin, Gary (NIH/OD) [E]: "Re: should you or should you not tell partners about theaccessibility issues on their sites?"
- Previous message: Joseph Sherman: "Re: Font Icons and Pseudo-elements"
- Next message in Thread: deborah.kaplan@suberic.net: "Re: Font Icons and Pseudo-elements"
- Previous message in Thread: Joseph Sherman: "Re: Font Icons and Pseudo-elements"
- View all messages in this Thread