131920 2014-04-20 15:04:52 -0700 AX: expose (heading) level based on heading elements outline depth 2015-02-17 06:44:38 -0800 1 1 1 Unclassified WebKit Accessibility 528+ (Nightly build) All All NEW InRadar P2 Normal --- 1 faulkner.steve webkit-unassigned faulkner.steve jcraig m.goleb+bugzilla mike webkit-bug-importer oldest_to_newest 1002422 0 faulkner.steve 2014-04-20 15:04:52 -0700 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 1002423 1 webkit-bug-importer 2014-04-20 15:05:20 -0700 <rdar://problem/16671435> 1002516 2 faulkner.steve 2014-04-21 01:58:49 -0700 related HTML spec bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003 1002704 3 jcraig 2014-04-21 15:45:30 -0700 There is some ongoing discussion in the W3C bug that should be addressed before we consider changing WebKit. 1002817 4 faulkner.steve 2014-04-21 23:00:58 -0700 (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