Bug 195010 - AX: <headers> need to obey scoping role changes
Summary: AX: <headers> need to obey scoping role changes
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: Other
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-02-25 11:05 PST by chris fleizach
Modified: 2024-01-18 14:31 PST (History)
6 users (show)

See Also:


Attachments
VoiceOver is running and the landmarks router is displayed, showing there are 11 banner landmarks exposed, when there should only be 1. (88.53 KB, image/jpeg)
2019-04-05 06:20 PDT, Scott
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description chris fleizach 2019-02-25 11:05:39 PST
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>
Comment 1 Radar WebKit Bug Importer 2019-02-25 11:21:18 PST
<rdar://problem/48370244>
Comment 2 Scott 2019-04-05 06:20:01 PDT
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
Comment 3 Scott 2019-08-06 10:21:39 PDT
Additional note that iOS 12.3.1 similarly exposes too many banner landmarks.
Comment 4 Yakim 2020-07-21 14:49:59 PDT
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
Comment 5 Joone Hur 2024-01-18 14:31:14 PST
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.