Re: Why are conflicts between native markup semantics and WAI-ARIA so complicated?

On 02/05/2018 09:04, Jan Hellbusch wrote:
> Hi Tobias,
>   
>> I always assumed that WAI-ARIA will always override native semantics.
>> But now I found <https://protect-
>> au.mimecast.com/s/NJ9ICXLKZoim18NAt6d9eS?domain=w3.org>.
> 
> ARIA overrides Information on it's way from the DOM to the accessibility tree. So
> 
>> Some examples:
>>
>> - `<div role="button"></div>` has role "button" (ARIA wins)
>> - `<div aria-label="foo">bar</div>` has label "foo" (ARIA wins)
> 
> In these two cases ARIA is being used to override information. I'm not sure if the second example will work, though. Changing the name of an element will work with most interactive elements and some other elements, but not necessarily with all.

This short note from Léonie Watson may be helpful 
https://developer.paciellogroup.com/blog/2017/07/short-note-on-aria-label-aria-labelledby-and-aria-describedby/

>> - `<div aria-hidden="false" hidden></div>` is hidden (native wins)
> 
> Actually, this code is doing something different: "Hide something from the accessibility tree (aria-hidden="true"), although it is already hidden ("hidden" hides it from screen and the accessibility tree). Since the hidden property is already doing what aria-hidden="true" is intended to do, aria-hidden="true" is not needed. See also test cases at
> http://stevefaulkner.github.io/HTML5accessibility/tests/hidden-2016.html

Note that the example given was using aria-hidden="false". So it was a 
hidden element, and the attempt was being made to unhide it from AT. 
Which won't work.

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

Received on Wednesday, 2 May 2018 08:38:37 UTC