Case study

We Ran an Accessibility Check on Our Own 142 Pages: What It Found and What We Fixed

Before telling anyone else how to check a website for accessibility problems, we ran the check on our own. These are the real numbers, the real fixes, and the long list of things an automated check cannot see.

Published 6 November 2026 · 4 min read · Numbers from our own run, repeatable
Disclosure: this is an automated first-pass check of a few machine-checkable rules. It is not an audit, not a certification and not evidence of WCAG, ADA or European Accessibility Act compliance. We sell no accessibility service today; the only product mentioned is a penalty reference workbook, linked at the end.

What we ran

Our checker reads each page's HTML and looks for faults a program can detect reliably: form fields that are labelled only by placeholder text, hidden decoy fields that a screen reader would still announce, pages with no top-level heading, and heading levels that jump (for example from a main heading straight to a minor one). Each finding names the WCAG 2.2 criterion and the line where it occurs.

Before and after

  • First run (118 public pages): 0 errors and 22 warnings: 11 form fields labelled only by placeholder text, 5 hidden spam-trap fields still announced to screen readers, 3 pages with no h1 and 3 skipped heading levels.
  • After the fixes (142 public pages, run on 6 November 2026): 0 errors and 0 warnings.

What we changed

  • Gave every form field a real label instead of relying on placeholder text.
  • Hid the spam-trap fields from assistive technology as well as from sight.
  • Made the main title of each page a real h1, keeping the look of the page the same.
  • Turned footer column titles from a minor heading level into a level that follows the page structure.
What 0 warnings does not mean. The check does not test keyboard access or visible focus, colour contrast, whether alt text actually describes the image, captions, focus and reading order, error messages in forms, how the page behaves with a screen reader, or content that scripts add after the page loads. A clean result here says only that the machine-checkable rules we run found nothing.

Do the same on your own site

  1. Run a free browser tool such as axe or WAVE on your most visited pages and on every form.
  2. Fix the structural findings first: labels, headings, missing page titles.
  3. Then test by hand: tab through the page without a mouse and see whether you always know where you are.
  4. Keep a dated record of what you ran and what changed, as we did here.

Why it matters if you sell into the EU

The European Accessibility Act has applied since 28 June 2025 to e-commerce and other consumer services offered in the EU, and each member state sets its own penalties. We read the penalty provisions of eleven countries in their own legal texts and put the maximum for your company size in one workbook.

See what the penalties are in eleven EU countries

Enter your turnover and company size and get the statutory maximum per country, with the provision and a link to the official text for every figure. Not legal advice.

European Accessibility Act Penalty Exposure Checker ($19)
One-time purchase, Excel workbook with a PDF guide.