How to Use AI to Make Software Development Accessible

AI generates code faster than humans ever could. If that code is inaccessible by default, the problem is not getting smaller. It is getting bigger. Fast. I am a screen reader user. I use AI coding tools every day. And every day I fight for the basics. Label the inputs. Trap focus in the modal. Use a button, not a div. Add a live region so the screen reader knows something changed. On Friday night I had enough. I built 6 specialized AI agents that enforce accessibility in Claude Code. I published the repo, shared a writeup, and went to bed. By Saturday morning, Jeffrey Bishop was already pushing code. Jeff is blind, like me. He did not ask can I help. He started building. 43 commits in 5 days. He ripped out the part that was not working and replaced it with something better. 5 days later: 47 agents across 4 teams. 3 platforms. 30 pull requests merged. 360 files changed. 73,000 lines of code. 34 security vulnerabilities identified and resolved. One command to install. Free. MIT licensed. It runs on Claude Code, GitHub Copilot, and Claude Desktop. It supports macOS, Linux, and Windows. This is not an overlay. It does not touch your website. It does not inject JavaScript. It does not promise compliance. There is no widget, no badge, no fee. It is a developer tool that raises the floor. Code that comes out of AI with these agents active will have labels, focus trapping, proper ARIA, and contrast checks before you even start testing. That is not a magic fix. That is a better starting point. 95.9% of the top million websites have detectable accessibility failures. AI tools are automating those same mistakes at scale. Two blind developers and a community decided to stop waiting for someone else to fix it and built something that fights back. The project lives under a GitHub organization called Community Access because this is bigger than any one person. The more lived experiences that go into these agents, the better they serve the people who need them. Star it. Try it. Break it. Tell us what is missing. Full story: https://lnkd.in/gKzbYJ93 Press release: https://lnkd.in/gtjtiYD4 GitHub: https://lnkd.in/gMJqKXWc #accessibility #a11y #OpenSource #WebAccessibility #WCAG #ClaudeCode #GitHubCopilot #AI #DevTools #AssistiveTechnology #ScreenReader #WebDev

In our new #CHI25 paper, we studied how #GenAI coding assistants like GitHub Co-pilot impact developers with visual impairments. Despite progress in accessibility for developers who are visually impaired, generative AI coding assistants like GitHub Copilot introduce new challenges and opportunities that remain underexplored. We studied how developers who are visually impaired use GitHub Copilot and found a complex relationship: AI provides powerful new capabilities but also introduces new accessibility challenges. Key finding: AI coding assistants like Github Co-pilot give developers who are visually impaired more CONTROL by handling tedious tasks (like generating documentation) and allowing them to focus on higher-level strategic decisions - much like a pilot overseeing an aircraft's systems. However, it introduces new CONTEXT SWITCHING problems. The dynamic nature of AI suggestions and new Co-pilot features disrupts the sequential workflows that developers with visual impairments rely on. Or if I say the other way around, their mental model for coding. Developers were overwhelmed by constant AI suggestions. The constant stream of suggestions (especially ghost text) can create information overload for screen reader users. Imagine all these ghost text suggestions getting rendered on your screen reader. We propose "AI timeouts" - periodic breaks from AI intervention that allow developers to focus and think without disruption, especially important for screen reader users facing information overload. Despite challenges, Developers experienced significant productivity gains! AI assistants proactively anticipated coding needs and generated relevant code, reducing the need to navigate multiple documentation pages - a process that's especially challenging with screen readers. Co-pilot-like assistants can act as an "always-available coding partner," providing non-judgmental support. This reduced reliance on asking colleagues for help, valuable in workplace environments where developers might feel hesitant to frequently request assistance. Using Activity Theory as our framework, we identified key contradictions between AI tools' design and the needs of visually impaired developers. Most AI-enabled IDEs assume visual scanning of information, a significant accessibility barrier. We introduce a concept, "AI Timeouts," to reduce cognitive load and enable temporary pauses in AI interventions. Our research findings inform not just coding assistants but provide valuable insights if you are designing agentic AI systems that preserve user autonomy and can effectively support diverse user groups with varying levels of interaction. Thanks to my amazing collaborators, Claudia Flores-Saviaga, PhD, Ben Hanrahan, Steven Clarke, and Dr. Saiph Savage and for making this work possible! Catch us presenting our work at the ACM CHI Conference in Japan on Wednesday, April 30.

Why does it seem like accessibility is often treated as an afterthought? 🕒 In my experience, companies wait until audits or legal pressures force them to act, but this reactive approach costs time, money, and damages user trust. Why let it come to that? I’ve seen forward-thinking organizations start to shift accessibility left—embedding it directly into every stage of development. 🌍 From the requirement phase to testing, accessibility checks can now be automated, flagging and resolving issues in real-time. This isn’t just about ticking boxes for compliance; it’s about creating a seamless, inclusive experience for every user from the start. Today’s AI-driven accessibility tools don’t just identify issues—they help solve them. With checks happening within the developer’s IDE, real-time feedback ensures accessibility is built into the code before it even reaches production. 🛠️ This approach saves on manual work, lowers costs, and empowers developers to meet standards like WCAG and ADA efficiently. By making accessibility part of the core development platform, we’re not just avoiding fines—we’re building a brand that prioritizes inclusion and usability for everyone. It’s time to make accessibility a key business principle, not just a checkbox. 🔍💡

🦸🏻 Accessibility Skills For Accessible AI Interfaces (https://lnkd.in/envRSTuT), a thorough set of accessibility-focused instructions and guidelines for AI tools to build with accessibility in mind to meet WCAG 2.2 AA and ADA standards — even when dealing with quick fixes. Put together by Felipe A. Carriço. --- 🔹 1. AI-Generated Interfaces Are Inaccessible By Default Most AI systems model what code *looks* like, not what code *means* to assistive technologies. Accessible code is quite underrepresented in training data, and feedback loops typically involve visual output, not semantic failures. As a result, most LLMs optimize for visual output while generating near-zero semantic information for the layer that assistive technologies actually read. Improvements are slowly coming in, but they are inconsistent, and the default output remains inaccessible enough to require systematic enforcement. You can find a 5-layer enforcement system of prompt constraints — with examples and useful pointers — in a neat article “AI-Generated UI Is Inaccessible by Default” (https://lnkd.in/eirA7xSd) by Durgesh Rajubhai Pawar. --- 🔸 2. Inclusive Design Skills If you are looking for AI skills specifically focused on inclusive design, Marie-Claire Dean has put together Inclusive Design Skills (https://lnkd.in/exsrRuDA). It's a set of 40 skills and 18 commands across 6 plugins, covering cognitive accessibility, inclusive interactions, accessible content, inclusive personas, adaptive interfaces and accessibility decisions (!). --- 🔺 3. AI Can’t Replace Manual Accessibility Testing It’s always worth noting that no level of automation can replace human accessibility testing. Even if a product is fully compliant, it doesn’t mean that it’s usable for people with various accessibility needs. The best way is to regularly bring people with accessibility needs for testing. No magical Claude skill can be more efficient than that. And as always, thanks to everyone putting these wonderful little helpers together to benefit from. 🙏 ↓