Bug 195010 – AX: <headers> need to obey scoping role changes

• Status: RESOLVED
• Resolution: FIXED
• Component: Accessibility

[chris fleizach]

https://w3c.github.io/html-aam/#el-header-ancestorbody versus https://w3c.github.io/html-aam/#el-header.

<header> obey the same scoping as <footer>

[Radar WebKit Bug Importer]

<rdar://problem/48370244>

[Scott]

Created attachment 366813 [details]
VoiceOver is running and the landmarks router is displayed, showing there are 11 banner landmarks exposed, when there should only be 1.

test case screen shot was taken from: https://scottaohara.github.io/testing/banner-landmark/

tested with macOS 10.14.4, Safari 12.1

[Scott]

Additional note that iOS 12.3.1 similarly exposes too many banner landmarks.

[Yakim]

I encountered the same problem. In the following bug report I read that the banner role will only be removed from a <header> element if it is nested in an <article> or <section>: https://bugs.webkit.org/show_bug.cgi?id=78992
I have tested this and can verify that this behaviour seems to still seems to be in place. 

Looking at the Banner page on the ARIA Landmarks example website it defines the following - https://w3c.github.io/aria-practices/examples/landmarks/banner.html:

- The HTML header element defines a banner landmark when its context is the body element.
- The HTML header element is not considered a banner landmark when it is descendant of any of following elements:
 - article
 - aside
 - main
 - nav
 - section

It seems that <aside>, <main>, <nav>, and <section> are ignored when considering if a <header> element should have a role of banner.

Tested with macOS 10.15.5, Safari 13.1.1

[Joone Hur]

This issue was fixed in https://bugs.webkit.org/show_bug.cgi?id=242685
Please let me know if there are still problems with the voiceover.