Bug 131920 – AX: expose (heading) level based on heading elements outline depth

• Component: Accessibility
• Status: NEW

[Steve Faulkner]

Currently the HTML5 outline algorithm [1] is not implemented, propose implementing and exposing as a DOM method  so developers and 3rd part software such as assistive technology can provide a document outline to users. 

The HTML5 outline algorithm is implemented in conformance checkers:
http://validator.w3.org/nu/ 
https://github.com/validator/

and browser extensions:
https://chrome.google.com/webstore/detail/html5-outliner/afoibpobokebhgfnknfndkgemglggomo?hl=en

[1] http://www.w3.org/html/wg/drafts/html/master/sections.html#outlines

Implement 'heading role, with the aria-level property set to the element's outline depth' as per  
http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics

Acc API mappings
http://rawgit.com/w3c/html-api-map/master/index.html#el-h1-h6

* MSAA + IAccessible2 *
Role:  IA2_ROLE_HEADING 
Object attributes:  level:<heading_level> 
Interfaces:  IAccessibleText2; IAccessibleHypertext2; 

*ATK*
Role:  ATK_ROLE_HEADING 
Object attributes:  level:<heading_level> 
Interfaces:  AtkText; AtkHypertext  

*AX*
AXRole: AXHeading 
AXSubrole: (nil) 
AXRoleDescription: "heading" 
Properties: Use AXLevel to expose the heading level

[Radar WebKit Bug Importer]

<rdar://problem/16671435>

[Steve Faulkner]

related HTML spec bug
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003

[James Craig]

There is some ongoing discussion in the W3C bug that should be addressed before we consider changing WebKit.

[Steve Faulkner]

(In reply to comment #3)
> There is some ongoing discussion in the W3C bug that should be addressed before we consider changing WebKit.

There is also an issue with outline depth calculation as currently specced that needs to be resolved
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25394