ISSUE-647: Should aria-hidden=false put things in the tree, or stay a no-op as it is now, and done in the 1.1 timeframe?

Should aria-hidden=false put things in the tree, or stay a no-op as it is now, and done in the 1.1 timeframe?

State:
CLOSED
Product:
ARIA 1.1 Core Mapping Specification
Raised by:
Joanmarie Diggs
Opened on:
2014-03-11
Description:
Given the associated issues upon which there will need to be some serious thought, discussion, consensus building, etc.
- *if* the wider group (PFWG/ARIA TF) thinks this is a 1.1 issue.
- *then* we should start talking about it now in general and w.r.t. the UAIG.
- if it's a 2.0 issue, then we can relax some.

See also:
https://bugzilla.mozilla.org/show_bug.cgi?id=945194
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

Closing since Mozilla will not implement this functionality, namely, that element with aria-hidden="false" will be forced into the a11y tree. There is a note in the spec for aria-hidden that describes the inconsistency among user agents in this regard.

Joseph Scheuhammer, 13 Dec 2016, 20:53:35

Display change log ATOM feed


Joanmarie Diggs <jdiggs@igalia.com>, James Nurthen <nurthen@adobe.com>, Chairs, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $