Interface Core A1 · Official standard Platform: Web

Banner Landmark

A banner landmark is the main header area for a whole website. A wide announcement strip may also be called a banner, but it is a different design pattern.

See how it works
You might call it Banner Landmark

See how it works

Original worked exampleBanner Landmark

Another example

A site repeats its logo, full-site search, and account controls on every page. One top-level banner landmark groups them so screen-reader users can jump there. Headers inside articles should not all become banner landmarks.

Main parts

  1. 01site identity
  2. 02global controls
  3. 03banner landmark

Use it when

Use this term for the main site-header landmark. If you mean a visual announcement strip, say so clearly.

Do not use it when

Do not make several top-level banner landmarks or assume every wide box is a semantic banner.

Name used in code

<header> at document scope → role=banner

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Banner Landmark to solve this user need without losing the current context. User context: A site repeats its logo, full-site search, and account controls on every page. One top-level banner landmark groups them so screen-reader users can jump there. Headers inside articles should not all become banner landmarks. Recommended pattern: Banner Landmark. Why it fits: Use this term for the main site-header landmark. If you mean a visual announcement strip, say so clearly. Do not use it when: Do not make several top-level banner landmarks or assume every wide box is a semantic banner. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Banner Landmark. Definition: A banner landmark is the main header area for a whole website. A wide announcement strip may also be called a banner, but it is a different design pattern. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

A1
How official is this term?

Official standard

A named standard sets the rules described on this page.

The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example.

Scope
WAI-ARIA banner landmark semantics
Document status
recommendation
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 — banner role banner role Scope: Web accessibility semantics; direct scope: banner role Role here: Direct term reference Source covers: canonical name, definition, semantics, implementation Authority source · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 Scope: Web accessibility semantics Role here: Authority within stated scope Source covers: canonical name, definition, semantics, implementation Term reference WAI-ARIA 1.2 Role here: Direct term reference

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.