Ideas and guides about making the web work for everyone.
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.
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.
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.
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.
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.
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.
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.
Every AI coding tool can find accessibility issues. Almost none can prove they were fixed. That gap is where compliance falls apart.
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 overlay widgets promise instant compliance, but they create more problems than they solve. Here's what actually works.
Why we built an accessibility tool that works through your AI coding assistant — and what makes it different from everything else.