This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
+++ This bug was initially created as a clone of Bug #29031 +++ In UIA, headings and heading levels are mapped as a text attribute on a text run within the text pattern. The correct mapping is to add heading styleID to the text pattern run for the heading, according to this guide https://msdn.microsoft.com/en-us/library/windows/desktop/hh437309(v=vs.85).aspx. Edge implements these styles h1 = styleID 70001 h2 = styleID 70002 h3 = styleID 70003 h4 = sytleID 70004 h5 = styleID 70005 h6 = sytleID 70006 The easiest way to test this is using Windows 10 Narrator. Turn on verbose mode (capslock+a) and switch to heading navigation (capslock+up arrow). Navigate through the headings on this test page http://thepaciellogroup.github.io/AT-browser-tests/test-files/h1-h6.html (Hi, Steve!) using capslock+right arrow. Narrator will announce the heading level in verbose mode.
Hi Cynthia, for the heading mapping the AAM points to the ARIA core aam so should this bug be filed against core?
this sentence in the HTML-AAM needs to change as well: "heading role, with the aria-level property set to the element's outline depth" since there is no heading role/control type in UIA. I have created issues for the Core-AAM Core-AAM ISSUE-738: UIA mapping for heading incorrect Core-AAM ISSUE-739: UIA doesn't support heading without level, how should we map role=heading without aria-level?
Links: https://www.w3.org/WAI/PF/Group/track/issues/738 https://www.w3.org/WAI/PF/Group/track/issues/739
(In reply to Cynthia Shelly from comment #2) > this sentence in the HTML-AAM needs to change as well: "heading role, with > the aria-level property set to the element's outline depth" since there is > no heading role/control type in UIA. The mention of @aria-level aside, shouldn't that sentence in HTML-AAM remain? It's just identifying the relevant WAI-ARIA role, which is heading. The UIA mapping for HTML heading elements is the same as the UIA mapping for the ARIA heading role, so it will be in CORE-AAM that the UIA mapping using styleID on the text control pattern is specified, as per Cynthia's issue 738 [1]? [1] https://www.w3.org/WAI/PF/Group/track/issues/738
HTML AAM is no longer an ARIA Deliverable. If you wish to pursue this issue please file at https://github.com/w3c/html-aam/issues