Accessibility belongs where developers already work
A developer I spoke with recently said something that stuck with me: "I can just add accessibility rules to my CLAUDE.md. Why would I need a tool for that?" He's right that you can. You can write "...

Source: DEV Community
A developer I spoke with recently said something that stuck with me: "I can just add accessibility rules to my CLAUDE.md. Why would I need a tool for that?" He's right that you can. You can write "follow WCAG AA" in your AI instructions and your coding assistant will try. It will add alt text sometimes. It will use semantic HTML when it remembers. It will suggest aria attributes in contexts where it has seen them before. But try this: ask the same AI to review a codebase for accessibility tomorrow. It won't remember what it found yesterday. Ask it whether a fix it applied last week actually passed. It can't tell you. Ask it to prove to your compliance officer that every component was reviewed. There's nothing to show. Instructions without enforcement are suggestions. And suggestions don't survive deadlines, team changes, or the EAA inspector who shows up asking for evidence. The enforcement gap Since June 2025, the European Accessibility Act has been in active enforcement. France issue