Automated accessibility testing catches 30 to 40 percent of issues. Here's the other 60.
Automated scanners set a capability floor for accessibility, not a ceiling. Here's what they catch, what they can't, and how to cover the rest.
Blog
Ideas and guides about making the web work for everyone.
What AI coding tools can (and can't) fix on your Shopify or WooCommerce store
Small founders on Shopify and Woo lean on Cursor, Copilot, and Claude Code for the custom bits of their store. Here's the map of what AI tools can actually fix, what they can't, and which parts of accessibility are yours to own in the first place.
What AI just gave accessibility professionals back
For two decades, accessibility specialists have spent a meaningful slice of their week on the boring 30–40% — missing alt text, wrong heading levels, ARIA in invalid combinations. In the last 60 days, that layer started handling itself. Here's what that frees them to do.
The AI coding tools finally noticed accessibility. Now what?
GitHub shipped its own accessibility scanner. A community pack shipped 79 specialised agents. The lane is no longer empty. Here's what those tools do, what they miss, and where evidence still has to come from.
Accessibility MCP servers for AI coding agents (2026)
A practical comparison of accessibility MCP servers and tools that work with Claude Code, Cursor, and Windsurf — what each one does, what it doesn't, and when to pick which.
Preparing for the 2026 accessibility deadlines: HHS, DOJ Title II, and the EAA, ten months in
HHS's May 2026 healthcare accessibility deadline still stands, DOJ extended Title II by a year, and the EAA is enforcing in Europe. What changed, what didn't, and what evidence regulators want.
An accessibility check that runs on every pull request
The Jeikin Accessibility app is on the GitHub Marketplace. Install it on a repo and every pull request gets a WCAG review before it merges.
The accessibility tree is the new API
AI agents don't see your website. They read the accessibility tree. The same structure built for screen readers is now the interface for every AI agent on the web.
The in-house illusion: why hiring an accessibility lead isn't a compliance strategy
Forbes just put a number on it. Settlements run $25k to $100k per case, before legal fees. One person can't merge every PR. Compliance isn't a role, it's a pipeline.
The enforcement gap: why finding issues was never the problem
Every AI coding tool can find accessibility issues. Almost none can prove they were fixed. That gap is where compliance falls apart.
Accessibility belongs where developers already work
AI coding assistants can follow instructions. But instructions without enforcement are just suggestions. Here's what changes when accessibility has a system behind it.
Accessibility overlays: why painting over problems doesn't fix them
Accessibility overlay widgets promise instant compliance, but they create more problems than they solve. Here's what actually works.
Introducing Jeikin: accessibility compliance for AI-assisted development
Why we built an accessibility tool that works through your AI coding assistant — and what makes it different from everything else.