WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Icon instead of text > open in new window

for

From: Patrick H. Lauke
Date: May 15, 2017 3:50PM

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