Interface Core A1 · Official standard Platform: Web

Landmark

A landmark is a major area of a page. Assistive technology lets people jump straight to that area.

See how it works
You might call it landmark regionpage region

See how it works

Original worked exampleLandmark

Another example

On an insurance dashboard, a keyboard user opens the landmark list. They jump from the page banner to the main claims area, then to the area labeled “Policy help.”

Main parts

  1. 01Region role
  2. 02Accessible label
  3. 03Unique scope

Use it when

Mark each major page area with the right native element. Give repeated landmarks different, clear labels.

Do not use it when

Do not make every container a landmark. Too many landmarks make quick navigation harder.

Name used in code

header, nav, main, aside, footer, form, or an ARIA landmark role

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 Landmark to solve this user need without losing the current context. User context: On an insurance dashboard, a keyboard user opens the landmark list. They jump from the page banner to the main claims area, then to the area labeled “Policy help.” Recommended pattern: Landmark. Why it fits: Mark each major page area with the right native element. Give repeated landmarks different, clear labels. Do not use it when: Do not make every container a landmark. Too many landmarks make quick navigation harder. 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 Landmark. Definition: A landmark is a major area of a page. Assistive technology lets people jump straight to that area. 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 landmark roles
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 — Landmark Roles Landmark Roles Scope: Web accessibility semantics; direct scope: Landmark Roles 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

Copy it yourself

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