Back to Blog
·6 min read·A11yScope Team

1 in 3 Websites Has a Critical Accessibility Barrier: A Severity Breakdown of 244 Real Sites (2026 Data)

AccessibilityWCAGData StudySeverityResearch

# 1 in 3 Websites Has a Critical Accessibility Barrier: A Severity Breakdown of 244 Real Sites (2026 Data)

It is one thing to know that most websites have accessibility issues. It is another to know how bad those issues are. A skipped heading level is a nuisance; a button a screen reader cannot name is a wall. So we went back through our scan dataset and sorted every violation by the one thing that matters most to a real user: severity.

This is a companion to our study of the most common accessibility violations. That one answered what breaks most. This one answers how serious it is.

Key findings

  • 34.4% of websites have at least one critical violation — an issue that, by axe-core's own impact rating, can completely block a task for someone using assistive technology.
  • 82.4% have at least one serious-or-worse violation. The large majority of sites are not failing on minor technicalities; they are failing on issues that materially degrade the experience.
  • The average site carries 4.1 distinct violation types; the median is 4, and the worst single site had 13.
  • Not one site in the sample scored a perfect 100 — every single site had at least some checks that failed outright or needed human review.
  • The critical barriers are concentrated in a short, fixable list: missing image alt text, unnamed buttons, blocked zoom, and broken ARIA.

Methodology (read this before quoting us)

  • Sample: 244 distinct domains, deduplicated from more than 1,000 scans (latest scan per domain), collected through June 2026 via A11yScope's free scanner.
  • Engine: axe-core by Deque Systems — the same engine behind Google Lighthouse — run in a fully rendered headless browser against WCAG 2.1 AA and best-practice rules.
  • Severity = axe-core impact: each violation carries an impact rating of critical, serious, moderate, or minor, assigned by axe-core based on how much it blocks an assistive-technology user. We report a site as "having a critical violation" if any element on the scanned page triggered a critical-impact rule.
  • A note on the score: A11yScope's 0–100 score is the share of automated axe checks a page passes cleanly (passes ÷ [passes + violations + checks needing manual review]). It is not a WCAG-conformance percentage. That is why a site can have zero flagged violations and still not score 100 — there are almost always checks that require a human to confirm.
  • Selection bias, stated plainly: these are sites whose owners cared enough to run a check. The broader web is likely worse.

How severe are the failures?

| Severity reached | Share of sites |

|---|---|

| At least one critical violation | 34.4% |

| At least one serious or critical violation | 82.4% |

| Zero detectable violations | 7.0% |

The headline most people quote — "most sites have accessibility issues" — undersells the problem. The more honest framing is that four out of five real websites carry a serious-or-worse barrier, and one in three carries an outright critical one.

The critical barriers: a short, fixable list

Critical-impact violations are the ones that can fully block a task. The encouraging news is that they cluster around a handful of rules — and the most common ones are among the cheapest fixes in web development.

| Critical violation (axe rule) | % of sites |

|---|---|

| Images without alt text (image-alt) | 11.1% |

| Buttons without an accessible name (button-name) | 9.4% |

| Zoom/scaling blocked by viewport (meta-viewport) | 8.2% |

| Disallowed ARIA attribute (aria-allowed-attr) | 5.3% |

| Missing required ARIA children (aria-required-children) | 4.9% |

| Form field without a label (label) | 4.1% |

| Unnamed