Accessibility bugs are notoriously easy to ship and expensive to fix after the fact. GitHub is tackling this head-on with an experimental general-purpose accessibility agent built on top of GitHub Copilot , and the numbers are already compelling. To date, the agent has reviewed 3,535 pull requests, with a 68% resolution rate.

The agent has two jobs: providing engineers with reliable, just-in-time answers to accessibility questions in the GitHub Copilot CLI and the Copilot VS Code integration, and catching and automatically remediating simple, objective accessibility issues before they go to production. For the second goal, it is set to automatically evaluate changes that modify front-end code.

The problem no linter can fully solve

WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility, organized into success criteria at levels A, AA, and AAA. Most teams rely on automated checkers to catch violations , but those tools have a hard ceiling. Of the 55 total WCAG level A and AA success criteria, only 35 can be detected via deterministic automated code checkers, meaning roughly 36% cannot be discovered automatically.

LLM-powered agents are making inroads on that 36% gap, but it is not a perfect science. This makes it important to manually identify accessibility barriers earlier during design and prototyping , the stage where the majority of accessibility issues originate.

There's also a legal tailwind here. The European Accessibility Act is now in effect, and Title II of the Americans with Disabilities Act is set to establish WCAG 2.1 AA as the legal definition of done in April 2027. Organizations that haven't invested in accessibility infrastructure are going to feel that deadline.

Why generic LLM prompts fail at accessibility

One of the most important findings in GitHub's writeup is that you can't just tell an LLM to "be accessible." Vague instructions in a skill file won't cut it , telling an LLM to "use accessibility best practices" with a short list of examples won't work well. The reason is structural: every major LLM is trained on decades of inaccessible code, so their default outputs tend to reproduce the same antipatterns.