12053 2011-02-13 19:18:10 +0000 The current default ARIA role for the summary element in HTML5 is nonsensical 2012-01-13 09:52:14 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED FIXED P2 normal --- 1 faulkner.steve ian ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 45450 0 faulkner.steve 2011-02-13 19:18:10 +0000 change default role of summary from heading to none It is starting to become clear that the summary element will be the interactive part of the details/summary disclosure widget. in this case it needs to convey useful name/role and state information to AT. below is the info i sent in response to question for advice on summary/details implementation: the key points are that depending on the platform accessibility API the summary element will have a different role, as an interactive control it needs to convey that interactivity not a heading semantic. http://lists.w3.org/Archives/Public/public-html/2011Feb/0238.html: in order for the details/summary to be accessible to people with disabilities it needs to be hooked up to be able to receive focus, be operable with the keyboard and have role, name and state information exposed via accessibility APIs below are some suggestions these: I would suggest the summary content act as the label for the disclosure triangle; Clicking on the summary with a mouse will open/close the details element. The summary should be keyboard focusable and when the spacebar is pressed it will open/close the details element. as should a tap on a touch screen. The summary element should be mapped to AXDisclosureTriangle[1] role in the Mac accessibility API. the accessible name (AXTitle) for the disclosure triangle is the text content of the summary element. when the details element open attribute is present, set AXValue property to 1 on the summary element. when the details element open attribute is absent, set AXValue property to 0 on the summary element. On windows where there is no disclosure triangle role map it to the ROLE_SYSTEM_PUSHBUTTON in MSAA [2] the accessible name (accName) for the button is the text content of the summary element. when the details element open attribute is present set STATE_SYSTEM_EXPANDED on the summary element. when the details element open absent is present set STATE_SYSTEM_COLLAPSED on the summary element. [1] http://developer.apple.com/library/mac/#documentation/Accessibility/Reference/AccessibilityCarbonRef/Reference/reference.html%23//apple_ref/doc/uid/TP40001082-CH1g-BAJGFBAF [2] http://msdn.microsoft.com/en-us/library/dd373608(v=VS.85).aspx http://msdn.microsoft.com/en-us/library/dd318466(v=VS.85).aspx 45598 1 w3c 2011-02-15 16:11:39 +0000 The bug-triage sub-team thinks this is a Accessibility Task Force priority, adding the a11yTF keyword. 47885 2 ian 2011-05-03 19:53:24 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 47887 3 contributor 2011-05-03 19:54:18 +0000 Checked in as WHATWG revision r6054. Check-in comment: Update ARIA role for <summary>. http://html5.org/tools/web-apps-tracker?from=6053&to=6054 52443 4 mike 2011-08-04 05:01:32 +0000 mass-moved component to LC1 62656 5 faulkner.steve 2012-01-13 09:52:14 +0000 removing keywords as is fixed