W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2018

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

From: Jan Hellbusch <jan@hellbusch.de>
Date: Wed, 2 May 2018 11:18:17 +0200
To: <w3c-wai-ig@w3.org>
Message-ID: <003601d3e1f6$81fc33f0$85f49bd0$@hellbusch.de>
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
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>



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

Received on Wednesday, 2 May 2018 09:18:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:17 UTC