| | | |  | GAAD 2026: Not Much to Celebrate, Yet | | | Read this article on LinkedIn to join the conversation | May 21st is Global Accessibility Awareness Day. If you are expecting a post full of colored banners, virtual events, and “let’s raise awareness!” energy, keep looking, this is not that post. Disability advocates across the US are exhausted, and we have more than enough reasons to be. GAAD exists to raise awareness. The goal, always, was to make GAAD unnecessary. We were supposed to be working toward a world where accessibility is so embedded in how we build, buy, and govern that we no longer need a special day to remind anyone that disabled people exist. We are nowhere near that finish line. And in several important areas, we have lost ground. The celebrations this year are quieter. Some have not happened at all. That is not a coincidence; it is a signal. AI-Generated Code Is Making the Web Less Accessible, Not More The accessibility community was cautiously hopeful when AI coding assistants became mainstream. The promise was real: developers who had never considered accessibility might finally receive nudges in the right direction if the tools they used surfaced accessible patterns by default. That is not what happened. Instead, developers are now shipping AI-generated code at unprecedented velocity, without the accessibility review that was already insufficient before these tools existed. GitHub Copilot, ChatGPT, Claude, Gemini, and their competitors produce markup that routinely lacks meaningful alternative text, omits or misuses ARIA roles, generates inaccessible form patterns, and fails basic keyboard navigation. The tools are trained on the existing web, which has an accessibility failure rate of almost 96 percent according to the WebAIM Million annual study. You cannot train a model to output accessible code when the overwhelming majority of training data is inaccessible. ... | | | | | | | | | |
