Open
Description
Main issue detailing the ARIA/core-aam change for role="sectionheader"
and role="sectionfooter"
: w3c/aria#1931.
It looks like html-aam WPTs were also written for these new roles to test that they act as implicit roles for <header>
/<footer>
(https://github.com/web-platform-tests/wpt/blob/f3be5f1e7435ecf568f0e778b63eb240df93fd60/html-aam/roles-contextual.tentative.html) however, this also needs needs to be updated in html-aam as they are currently mapped as generic
:
<header>
: https://w3c.github.io/html-aam/#el-header<footer>
: https://w3c.github.io/html-aam/#el-footer
Metadata
Metadata
Assignees
Labels
No labels
Activity
scottaohara commentedon Jun 3, 2025
@rahimabdi this is the work i was talking about on friday. i'd like this PR to include an update to what being "scoped to the body" means - to better clarify that it's more about whether these elements are accessibility children of the "document"
e.g., the following isn't really "right" in what the intent of this "scoped to body" meant to accomplish - but per the current spec text browsers are all doing this
rahimabdi commentedon Jun 6, 2025
After discussion with @scottaohara, this issue/PR should only tackle behavior of
<header>
/<footer>
when they are descendants of native sectioning elements. To summarize:<header>
is a descendant of<article>
,<main>
,<nav>
,<section>
or<aside>
, it should be exposed as a navigable region withrole="sectionheader"
if it has an accessible name<footer>
is a descendant of<article>
,<main>
,<nav>
,<section>
or<aside>
, it should be exposed as a navigable region withrole="sectionfooter"
if it has an accessible name<header>
is "sectionheader", and<footer>
is "sectionfooter"Related but separate issue for when
<header>
/<footer>
are descendants of ARIA roles that are sectioning element equivalents (e.g.,role="main"
): #586.