Skip to main content

Annual-style snapshot

State of Web Accessibility

This page reads like a lightweight industry memo. The numbers below are illustrative: they summarize how we describe blended public-web samples in training and product copy. They are not a live census of the internet and should not be cited as verified market statistics. Use them to orient teams, then run a free scan on your own URLs.

Get your own baseline

Executive read

  • Automated scores cluster in the 55–75 band for many marketing and content sites until templates pick up labels, contrast, and heading discipline.
  • The same few themes—non-text content, contrast, form labels, and keyboard traps—account for a large share of what scanners flag first.
  • Trend lines move slowly; regression often follows theme or plugin updates rather than one-off content edits.

Deep dives: issue library, audits by site type, WCAG in plain English.

Top issues distribution (illustrative)

Grouped by WCAG pillar-style themes. Bar length is relative within this mock dataset, not a raw rule count.

Most common automated findings

Approximate share of flagged rules in blended illustrative samples.

Trends over time (mock)

Illustrative average automated scores by quarter—useful for narrative only. We keep the curve gentle to reflect how template-level fixes lag behind content churn.

Average score ranges (0–100)

How we describe axe-style summaries—not legal compliance.

  • 0–49

    Usually many serious/critical automated findings; prioritize templates and navigation.

  • 50–74

    Mixed severity; often contrast, labels, and heading order on key flows.

  • 75–89

    Fewer blockers; remaining items may be moderate/minor or context-dependent.

  • 90–100

    Automated clean-up—still verify keyboard, forms, and dynamic content manually.

WCAG themes that show up often

Criteria often implicated when automation and quick manual checks overlap.

  • 1.1.1 Non-text ContentImages and icons
  • 1.4.3 Contrast (Minimum)Visual design
  • 2.4.4 Link Purpose (In Context)Content
  • 3.3.2 Labels or InstructionsForms
  • 4.1.2 Name, Role, ValueComponents and ARIA

Accessibility score badge (after you publish a report)

Replace the slug with your public report path. Base URL for this build: https://testaccessbility.com

  • HTML link badge

    <a href="https://testaccessbility.com/report/your-report-slug" rel="noopener" style="font:600 14px system-ui,sans-serif;color:#0f766e">TestAccessibility public report</a>
  • Markdown

    [TestAccessibility accessibility report](https://testaccessbility.com/report/your-report-slug)

Explore further