This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
(In reply to Cynthia Shelly from comment #0) > 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. thanks Cynthia, have moved bug over to the html-aam spec (this one is for old spec)