Author
Benjamin Morton
Founder, A11yFlow
Benjamin builds A11yFlow, a WCAG 2.2 accessibility scanning API that runs real Chromium and axe-core, and writes the engineering guides on this blog. His focus is the practical side of accessibility for developers: wiring automated checks into CI/CD, mapping violations to WCAG success criteria, and meeting obligations under the European Accessibility Act and the ADA without slowing teams down.
Writes about
- Web accessibility
- WCAG 2.2
- Automated accessibility testing
- axe-core
- European Accessibility Act
- ADA compliance
- CI/CD accessibility gates
Articles by Benjamin Morton
Free vs Paid Accessibility Testing Tools: A Feature Matrix
Free tools catch about 57% of accessibility issues; paid guided testing reaches ~80% (Deque). What you actually pay for, and when free is enough.
Accessibility Testing for Startups: API-First on a Budget
64% of companies sued for web accessibility in 2025 had under $25M revenue (UsableNet). The $0 testing stack and a phased process for startups.
How Accessibility Scores Are Calculated (Lighthouse, axe, Custom)
Lighthouse weights binary pass/fail audits by axe impact, and a perfect 100 still isn't "accessible". How accessibility scores are really calculated, and what they miss.
Focus Management in SPAs: Accessibility Patterns
SPAs break focus on route change: the browser stops moving it, and 71.6% of screen reader users navigate by headings (WebAIM). The patterns and CSS to fix it.
Color Contrast WCAG 2.2: A Developer's Fix Guide (CSS)
Low-contrast text fails 83.9% of home pages, the web's #1 accessibility issue (WebAIM, 2026). The exact WCAG 2.2 ratios and the CSS to fix them.
WCAG 3.0: What Developers Need to Know in 2026
WCAG 3.0 is still a Working Draft (its 9th, March 2026) and won't be a standard before 2028. It won't deprecate WCAG 2.2. Here's what actually changes.
ARIA Mistakes Developers Make (and How to Fix Them)
Pages using ARIA average 40.7% more accessibility errors than pages without it (WebAIM, 2026). Here are the eight mistakes behind it, with code to fix each.
Web Accessibility Statistics 2026: The Numbers That Hold Up
95.9% of home pages fail WCAG, the first rise since 2020 (WebAIM, 2026). Every stat here is traced to a primary source, and five famous ones are debunked.
ADA Title II Deadline Extended: What It Does Not Excuse
DOJ delayed the Title II web deadline to 2027/2028, four days before it landed. But for 15+-employee HHS recipients, Section 504 already bit first anyway.
ADA Website Lawsuits: The Statistics Developers Need in 2026
Federal website accessibility lawsuits jumped 27% to 3,117 in 2025. Six machine-detectable failures cause 96% of detected errors. What to fix first.
Automated vs Manual Accessibility Testing: The Data
Automated tools catch 57% of accessibility issues by volume but only 13% of WCAG criteria with high accuracy (Deque; Accessible.org, 2025).
Next.js Accessibility Best Practices (2026)
Next.js pages average 40.9 accessibility errors, the best of any framework but not zero (WebAIM, 2026). The build patterns every Next.js app needs, with code.
React Accessibility: Complete Testing Guide (2026)
React pages average 43.5 accessibility errors, below most frameworks but not zero (WebAIM, 2026). A complete guide to testing React accessibility, with code.
How to Fix the 10 Most Common WCAG Violations (with Code)
Six error types cause 96% of accessibility failures (WebAIM Million, 2026). Here is how to fix the 10 most common WCAG violations, with copy-paste code.
WCAG 2.2 Compliance Checklist for Developers (2026)
WCAG 2.2 adds 9 success criteria and drops 4.1.1 Parsing. A developer's Level AA checklist with code-level pass/fail checks for each new criterion.
European Accessibility Act: Developer Compliance Guide (2026)
The European Accessibility Act applies as of June 28, 2025. What it covers, the WCAG level it requires, transition deadlines, and per-country penalties.
Web Accessibility Compliance: The Developer Guide (2026)
95.9% of top sites fail WCAG checks. Map ADA, EAA, Section 508, and AODA to the exact WCAG version, level, deadline, and penalty each one requires.
How to Set Up Accessibility Testing in GitHub Actions (2026)
CI gates catch ~57% of accessibility issues (Deque). A step-by-step GitHub Actions setup with axe, Playwright, and pa11y-ci, using current 2026 versions.
Why Accessibility Overlays Fail: Data, Lawsuits, and Alternatives
22.6% of accessibility lawsuits in H1 2025 targeted sites with overlays installed. The FTC fined accessiBe $1M. Here's what the data actually shows.
Best Accessibility Scanning API for Developers (2026)
7 accessibility scanning APIs compared on WCAG coverage, pricing, and CI/CD integration. 94.8% of sites still fail basic checks, find the right API.
axe vs Lighthouse vs WAVE vs Pa11y: Which Should You Use?
axe-core runs its full WCAG rule set with zero false positives. Lighthouse checks a subset. WAVE shows issues visually. Pick the right tool for your workflow.
Developer's Guide to Web Accessibility Testing (2026)
94.8% of top sites fail WCAG (WebAIM, 2025). A developer's guide to the full testing lifecycle: automated scans, manual review, assistive tech, and CI/CD.
Accessibility Testing Tools Compared (2026)
94.8% of top sites fail WCAG (WebAIM 2025). Compare axe-core, Lighthouse, WAVE, Pa11y detection rates, CI/CD setup, and find the right tool for your team.
Introducing a11yFlow: API-Based WCAG Scanning for Developers (2026)
5,000+ ADA lawsuits filed in 2025 (UsableNet). Learn how API-based WCAG 2.2 scanning catches violations in CI/CD pipelines without enterprise contracts.