10424 2010-08-25 01:54:18 +0000 Permit <details> to take "roles that use the aria-expanded state" 2010-12-15 14:37:10 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products-(aria) a11y, aria P3 normal LC 1 xn--mlform-iua faulkner.steve ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37824 0 xn--mlform-iua 2010-08-25 01:54:18 +0000 REQUEST: clarify that <details> can take _all_ roles that use the aria-expanded state. Bug 9623 added strong semantics to <details> by linking presence/absence of the @open attribute to the aria-expanded="true/false" state. The new spec text says: ]] (The role can be changed as described in the next table, but is restricted to roles that use the aria-expanded state.) [[ But the above sentence is unclear: Is it the _complete_ subset of "roles that use the aria-expanded state" that makes up the permitted roles? Or is it "the next table" that decides? The list in "the next table" anyhow permits only a subset-of-the-subset of roles that use the aria-expanded state: ]] Role must be either form, group, navigation, note, or search [[ Thus the table e.g. forbids <details role="img" >. Despite that role="img" _does_ use the aria-expanded state. It is unclear whether "the second table" simply fails to list all the roles that use the aria-expanded state. Or whether the spec simply fails to describe the principles/criteria behind the selection of permitted roles. 37942 1 ian 2010-08-26 18:57:40 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: Clarified. 37943 2 contributor 2010-08-26 18:58:18 +0000 Checked in as WHATWG revision r5361. Check-in comment: Clarify non-normative sentence. http://html5.org/tools/web-apps-tracker?from=5360&to=5361 43380 3 cooper 2010-12-15 14:37:10 +0000 Big triage sub-team thinks the ARIA mapping team should review and update this bug as the mappings are prepared, but no need for entire HTML A11Y TF to review. Assigning to Steve Faulkner to track.