- From: Joshue O Connor <joshue.oconnor@cfit.ie>
- Date: Tue, 26 Nov 2013 10:52:40 +0000
- To: David MacDonald <david100@sympatico.ca>
- CC: 'HTML Accessibility Task Force' <public-html-a11y@w3.org>, 'WCAG WG' <w3c-wai-gl@w3.org>
[trimming cc list] David MacDonald wrote: > For a moment I will take off my "objectivity hat" and put forth my major concern. An accessibility problem which I've seen in the wild among developers who are beginning to learn about ARIA is they don't understand that the computation of the accName in accessibility API's, is an OR algorithm Agreed, they don't know that - and why would they? This is very new to many. Anything that we can do to help a developer understand the algorithms hierarchy is a good thing. Many won't have any interest, they'll just want a robust solution (at best), at worst something that they just don't have to think about but will do. > - if aria-labelledby references one or more id elements in the page, pass it to the accName OR > -if the aria-label attribute is present, pass it to the accName OR > -if the alt attribute is present, pass it to the accName OR > -if the title attribute is present, pass it to the accName > > So they do things like this: > <img scr="eiffelTower.jpg" alt="Eiffel tower" labelledby="123"> > <p id="123"> The tower stands 324 metres (1,063 ft.) tall</p> > > In this example the screen reader user would not know that it is the Eiffel tower because the ALT text is not read since the labelledby got to the accName first. This is a crude example where many of us in this field would easily know how to fix it. I wouldn't make assumptions about that. Please mail us the fix as you see it, or please add it to a relevant technique wiki page - nice teachable moment. Thanks Josh
Received on Tuesday, 26 November 2013 17:52:49 UTC