FA-11435 / Accessibility interaction semantics / Member archive

A nested header is exposed as a page-wide banner landmark · case 05

Section-local headers and footers appear in the page landmark inventory, or unnamed sections create noisy regions.

Member previewVariant 5 · 3 implementations · 10 checks per implementation

Case contract

This deliberately bounded native landmark adapter accepts tag, accessible name, and nearest-first ancestor tag names. main/nav/aside map to main/navigation/complementary. Named form/section map to form/region; empty or ASCII-whitespace-only names yield None. header/footer map to banner/contentinfo only outside every article, aside, main, nav or section ancestor. Other tags yield None. This adapter does not implement author role overrides or full HTML semantics.

Why this case matters

A controlled offline accessibility-data model. It isolates the stated contract; it does not simulate browser accessibility APIs or claim full ARIA conformance.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
deep local header	`"banner"`	`null`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.