Some content sits outside page landmarks
63.1%
of the 609 sites we scanned fail this
Ranging from 55.1% of US local government to 77.3% of Shopify DTC stores. Pooled across five targeted cohorts, so treat it as a convenience sample rather than a rate for the web.
What it means and how to fix it
A best-practice rule rather than a WCAG failure, and the single most frequent finding in our entire corpus. Content sitting outside any landmark is not a conformance breach, but it is the difference between a screen-reader user being able to jump to the main content and having to read past the header every time.
Content outside landmark regions is harder to navigate by heading/landmark for screen reader users.
The fix. Place all visible content inside clear page regions (header, navigation, main, footer) so it's easy to navigate.
What it looks like in code
HTML<a href="/path">Text</a><body>
<header>...</header>
<nav>...</nav>
<main>
<p>All content belongs to a landmark</p>
</main>
</body>Content outside any landmark cannot be reached by landmark navigation, so it is only findable by reading the page top to bottom.
The failing example is real markup from a site in our research cohorts. Class, style and data attributes are removed, and ... marks a value we elided. The structure is unchanged, because the structure is the failure.
How often it fails
Share of scanned sites in each cohort. These are five targeted studies, not a random sample of the web, so read the contrast between cohorts rather than any one figure as a web-wide rate.
Who fails it most3 cuts by CMS vendor, sector, regulated category
By CMS vendor
By sector
By regulated category
Groups smaller than 8 sites are not shown: a rate over a handful of sites moves by tens of points on a single result.
What this does not measureLimits of these figures, and where the corpus came from
- This rule maps to no success criterion, so a site failing it is not failing WCAG. It is still worth fixing: these are the patterns that decide whether assistive technology can navigate a page efficiently rather than merely read it.
- These are five targeted cohorts, not a random sample of the web. Per-cohort rates are the figure to quote; the pooled rate is a convenience sample.
- Denominators count sites that produced a result. Sites that were blocked or errored are excluded rather than counted as passing.
- Occurrence counts are floors: the engine records at most 25 occurrences of a rule per page.
- The EU and Indian cohorts retained only the primary success criterion per finding, so a rule mapping to several criteria contributes to one of them in those two cohorts and to all of them in the other three.
| Cohort | Scanned | Attempted |
|---|---|---|
| Shopify DTC stores | 75 | 75 |
| US local government | 158 | 221 |
| US healthcare providers | 208 | 218 |
| EU e-commerce | 107 | 170 |
| Indian financial services | 61 | 72 |
Corpus generated 2026-09-18.
Check your own site
A free scan reports this check alongside everything else, with the exact elements that fail.
Run a free scan