Search This Blog

Translate

Showing posts with label algorithmic bias. Show all posts
Showing posts with label algorithmic bias. Show all posts

Sunday, 29 March 2026

AI Mandates, Coding Shortcuts, and the Quiet Rise of Technoableism

A black and white editorial cartoon titled "TECHNO-ABLEISM OFFICE" illustrates a conflict over accessible design. A menacing robot labeled "ZABARDASTI AI" spews bubbles like "INACCESSIBLE" and "NO ARIA LABELS," while a shouting manager commands a stressed young programmer, "USE IT! MANDATORY ZABARDASTI! WE DON'T NEED YOUR 'ACCESSIBILITY' SLOWDOWN!" The programmer points to a computer, with a thought bubble quoting an article from The Hindu about forcing AI code making it brittle. An older man in a wheelchair reading THE TIMES comments that "WIPE CODING" for speed only "wipes the inclusion part."
The "Zabardasti AI" Mandate: A Cartoon on Corporate Techno-Ableism and Inaccessibility

Across the technology sector, organisations are beginning to mandate the use of AI coding tools. The argument is simple: AI increases productivity, accelerates software development, and allows companies to do more with fewer people. But something important is missing from this conversation. Most AI coding systems generate software that focuses on functionality and speed. Accessibility rarely appears in the default output. As a result, developers often receive machine-generated code that works visually but fails for screen readers, keyboard navigation, and other assistive technologies. 

 Over the last two decades, accessibility advocates have worked hard to teach developers that inclusive design must be built into software from the start. However, when AI tools become mandatory and productivity metrics dominate development workflows, accessibility risks being pushed to the margins again. This raises a deeper question: Are AI mandates quietly spreading technoableism within digital infrastructure? 

If accessibility is not integrated into AI coding systems themselves, organisations may unknowingly scale exclusion across the web. In the full article, I respond to a recent discussion on forced AI adoption and examine why accessibility must be part of the AI development pipeline itself. 

 Click below to read the full article.