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

Jan, there is a historic Firefox bug that may provide some clues
https://bugzilla.mozilla.org/show_bug.cgi?id=945194

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>

On 2 May 2018 at 10:18, Jan Hellbusch <jan@hellbusch.de> wrote:

> Hi Patrick,
>
> > > 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.ht
> > > ml
> >
> > 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.
>
> Noted. Do you by any chance have a good reference (such as a "Short note")
> on why unhiding hidden elements (including elements in subtrees) doesn't
> work? The question arises quite often and developers try and try again. On
> https://developer.paciellogroup.com/blog/2012/
> 05/html5-accessibility-chops-hidden-and-aria-hidden/
> it is explained, that aria-hidden="false" is not mapped, but I'm thinking
> of something like
> <div aria-hidden="true">
> <p aria-hidden="false">I am hidden from screen readers.</p>
> </div>
>
> Jan
>
>
>
> Jan
>
>
>
> --
> Hellbusch Accessibility Consulting
> Chemnitzer Str. 50, 44139 Dortmund
> Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925
> --
> Accessibility-Consulting seit 15 Jahren
> Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de
> Blog: https://www.hellbusch.de
>
>
>
> >
>
>
>