[Webkit-unassigned] [Bug 220534] New: AX: expose focusable elements even if element or ancestor has aria-hidden=true
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jan 11 23:02:03 PST 2021
https://bugs.webkit.org/show_bug.cgi?id=220534
Bug ID: 220534
Summary: AX: expose focusable elements even if element or
ancestor has aria-hidden=true
Product: WebKit
Version: WebKit Nightly Build
Hardware: All
OS: All
Status: NEW
Keywords: InRadar
Severity: Normal
Priority: P2
Component: Accessibility
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jcraig at apple.com
CC: webkit-bug-importer at group.apple.com
The AX tree inclusion section of ARIA now includes this line:
The accessibility tree inclusion section includes this line:
> [include in the accessibility tree…] "Elements that are focusable even if the element or one of its ancestor elements has its aria-hidden attribute set to true."
https://w3c.github.io/aria/#tree_inclusion
The ARIA WG discussed the "focusable" vs "expose only when focused" difference and came to the consensus that there were too many instances where authors did hidden focusable elements accidentally (including one recent report on the Benevity site).
So as I understand it, the way to hide focusable elements would be to make not rendered, or explicitly not focusable.
Visible, but explicitly not focusable
<button tabindex=“-1" aria-hidden=“true">
Not rendered, and therefore implicitly not focusable.
<button style=“display:none;">
Also, once WebKit implements @inert, that would also be sufficient:
<div inert>
<button aria-hidden=“true">this is inert, so not focusable among other things.. The aria-hidden is likely redundant here.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210112/3eb1b8cc/attachment-0001.htm>
More information about the webkit-unassigned
mailing list