Dashboard

Sign out?

You'll need to sign in with Google again to open your dashboard.

Check explainer · v1

Web accessibility: landmarks, duplicate ids and the baseline

Automated

Last reviewed

Accessibility failures are structural before they are visual: a page without landmarks, two elements fighting over one id, or a form whose fields have no names.

How this check works

Two axe-only rules can fail a page. Landmark structure fails when the rendered page has no main landmark, exposes content outside a landmark, or repeats landmark roles ambiguously; duplicate ids fail when two elements share an id, including ids referenced by ARIA. Both report na when axe did not run. Around them the audit reports an accessibility baseline: heading order (exactly one h1, no level skips), a contrast inventory that records color declarations and never fails on its own, and whether focus styles are declared. Hygiene rules cover the document language, the accessible name of links and buttons, form labels and image alt text. This page explains what the audit observes; it is not a WCAG or European Accessibility Act conformance audit and issues no certification.

What does a failure look like?

A page whose article sits outside every landmark; two search widgets sharing one id; a heading outline that jumps from h2 to h4; a form input with a placeholder but no label — the first two fail the axe rules, the rest are baseline warnings or notes.

How to fix it, step by step

  1. Wrap the page in header, nav, main and footer landmarks, keep exactly one main, and give repeated landmarks a distinct label.
  2. Make every id unique and update the ARIA references that pointed at the duplicates.
  3. Close the baseline gaps: one h1 with no heading skips, visible focus styles, a label for every field, alt text for informative images and a valid document language.

What does a pass or fail look like?

Good

One main landmark, no content outside landmarks, unique ids, a clean heading outline and labelled fields — axe reports no landmark or duplicate-id hits.

Fail

The article sits outside any landmark and two panels share id="search" — both axe rules fail before the contrast inventory is even read.

Frequently asked questions

Does this certify WCAG or EAA compliance?

No. The audit reports specific structural checks and a baseline inventory. It does not run a conformance review, does not cover every success criterion, and issues no certificate for WCAG or the European Accessibility Act.

Does a contrast note fail the page?

No. The contrast item is an inventory of color declarations, not a rendered contrast calculation, so it never fails on its own. Treat it as a pointer for manual review rather than an automated verdict.

Why do landmarks and duplicate ids fail the page?

Those two are axe-only rules: a hit is a concrete structural failure, so the rule fails. The baseline items keep their own severities — heading order and focus styles are graded, the contrast inventory stays a note, and hygiene rules report what they find.

This rule is one of the checks the page scan runs. Run the free page scan

Free preview; no account needed.

Visdenda check explainers · one page per published ruleAccessibility · v1