The Cost of Accessibility in AI — Jemima Abu, CAIS @aiDotEngineer
The Cost of Accessibility in AI — Jemima Abu, CAIS  @aiDotEngineer
Uploaded October 2026 | Updated November 2026, 2 days ago
The same Figma implementation prompt runs twice: once without accessibility guidance and once with an accessibility skill. In Jemima Abu's small experiment, the second run costs 58% less and finishes in about a third of the time. She immediately explains why that uncontrolled comparison cannot prove that accessible development is always cheaper. What it does expose is a familiar failure mode: an agent invents a verbose custom component when a native HTML element could supply much of the required behavior. Recreating semantics, keyboard interaction and expected browser behavior adds code and testing that a better starting point can avoid.

Abu connects that example to the context agents inherit. An inaccessible codebase teaches the wrong conventions, and a vague design prompt leaves too many product requirements unstated. Accessibility therefore begins with business requirements, design decisions and reusable components, then continues through implementation and QA. Her guidance includes auditing existing interfaces, packaging explicit accessibility instructions into agent skills, preferring semantic HTML and checking keyboard interaction. ARIA can help where necessary, but it does not replace correct native behavior. Waiting until the product is complete creates avoidable refactoring and regression work. Automated checks also leave gaps that require human review. The talk gives teams a concrete way to improve the instructions and patterns that shape generated interfaces while retaining responsibility for the finished experience. Its cost figures remain an illustration from one experiment; the broader argument is to make accessibility a normal requirement throughout the work rather than a repair at the end.


Speaker info:
- github.com/jemimaabu
- linkedin.com/in/jemimaabu
- jemimaabu.com

Timestamps:
00:00 - The question of accessible AI generated interfaces
1:14 - An uncontrolled accessibility skill experiment
3:42 - Agents inherit the codebase's conventions
4:31 - Native HTML instead of verbose custom components
5:45 - Accessibility from business requirements through QA
7:27 - Audits, reusable patterns and agent skills
The Cost of Accessibility in AI — Jemima Abu, CAISDont Vibe Code Your Agent Infrastructure - Akshat Bubna, ModalHow to Know When an AI Agent Can Work Unsupervised — Evan Kormos, CoinbaseYou Cant Tell What an Agent Skill Will Do by Reading It - Roey Ben Chaim, ZenityGive Your On-Call Its Own AI Teammate - Swaapnika Motapothula, Chinmay Gandhi & Vlad Tsvang, MetaWhy AI Writing Still Reads Like Slop — Louis-François Bouchard, Towards AIHow a Trading Firm Ships New AI Models the Same Day - Noyan Tokgozoglu, OptiverWhy Frontier Models Fail as Buy-Side Analysts - Janie Gu, Google DeepMind & Suyeol Yun, LinqAlphaA Bank Built Its Own Coding Agent. It Took Off — Felippe Felisola Caso & Francesco Galletta, MonzoAI Engineer NYC Livestream | Bridgewater, Two Sigma, Arize, Coatue, Nous (Hermes), Gen. IntuitionDoes Code Quality Still Matter? It Depends on This — Max Kanat-Alexander, Capital OneStop Shipping LLM Settings That Only Win on Paper - Rohan Pandey & Balaji Varadarajan, DigitalOcean
AI Engineer |

The Cost of Accessibility in AI — Jemima Abu, CAIS

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER