WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Icon instead of text > open in new window

for

From: Jonathan Avila
Date: May 16, 2017 7:07AM


> The whole set of documents/specs around accessible name and accessible description are, to put it mildly, confusing and obtuse. Lots of overlapping, cross-referencing separate docs

Yes, and the language about concatenation can trip up some people as well. There are also a number of ambiguities that need to be cleared up. For example, what happens with aria-label="" (null) or an aria-label=" " (a space or non-breakable space)? Is a space the accessible or name or does the algorithm consider that there is no valid aria-label and move on to the next step?

There are also a number of edge cases around sub-tree and referenced content that is hidden with different techniques and don't forget to include pseudo content as well!

> In the case of links, I'd recommend looking at https://w3c.github.io/html-aam/#a-element

I'd second this as a great resource.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
<EMAIL REMOVED>
703.637.8957 (Office)

Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Download our CSUN Presentations Here!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Patrick H. Lauke
Sent: Monday, May 15, 2017 5:51 PM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] Icon instead of text > open in new window

The whole set of documents/specs around accessible name and accessible description are, to put it mildly, confusing and obtuse. Lots of overlapping, cross-referencing separate docs, with some very dense and confusing algorithm sections that aim for brevity but simply result in more questions than answers. (plus there's both editor's drafts and working drafts, mixed in with some outdated/deprecated/superseded ones).

I've already vented about this https://github.com/w3c/aria/issues/544
... feel free to add a voice of support / a +1 :)

In the case of links, I'd recommend looking at https://w3c.github.io/html-aam/#a-element (the HTML specific guidance on how things should be mapped), as this splits out the name and description calculations into separate algorithms which are much clearer to parse for a reader. And if you look at "5.12.2 a Element Accessible Description Computation" the steps are much more straightforward (and support what was said on list earlier about title and how it should map to the accessible description, regardless of accessible name):

"1, If the element has an aria-describedby attribute the accessible description is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings 1.1.
2. Otherwise use the title attribute if it wasn't used as the accessible name 3. If none of the above yield a usable text string there is no accessible description"

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke