7434 2009-08-26 14:11:37 +0000 Everything with role=heading should also have an associated aria-level that indicates the level of the heading. The level of the heading should probably be based on the outline algorithm. 2010-10-04 13:54:29 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All VERIFIED FIXED http://whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products NE, NoReply P3 normal LC 1 contributor ian annevk hsivonen mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 26696 0 contributor 2009-08-26 14:11:37 +0000 Section: http://whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products Comment: Everything with role=heading should also have an associated aria-level that indicates the level of the heading. The level of the heading should probably be based on the outline algorithm. Posted from: 83.85.115.44 26697 1 hsivonen 2009-08-26 14:58:39 +0000 What problem does using role=heading aria-level=2 solve compared to using <h2>? Making the outline algorithm sensitive to attributes can turn out to be a major perf problem. (Consider developing a selector for outline depth and caching stuff on heading nodes in the DOM.) 26698 2 annevk 2009-08-26 15:05:19 +0000 I'm not suggesting to influence the outline algorithm with attributes. I'm suggesting to influence AT with the proper "implicit" attributes. One could argue that ARIA should have never introduced role=heading and aria-level in the first place because HTML adequately solves the use case, but it did. And since it was decided to provide the implicit mapping between HTML and ARIA, we should probably use all the features it provides, including aria-level. 26699 3 annevk 2009-08-26 15:06:32 +0000 (Having said that, ARIA can still be changed in theory and support for heading could be dropped in favor of people using actual elements.) 27431 4 ian 2009-09-21 23:09:35 +0000 Looks like I did this already. 33339 5 mjs 2010-03-14 14:50:10 +0000 This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.