Characterizing Visual Accessibility Issues in AI Developer Tools: An Empirical Study
2026-08-05 • Software Engineering
Software EngineeringHuman-Computer Interaction
AI summaryⓘ
The authors studied how AI tools that help programmers can create visual challenges for people who are blind, have low vision, or have trouble with colors. They looked at discussions and reported problems in five popular AI coding tools and found 600 clear cases of visual accessibility issues. These problems fell into three groups: difficulties with screen readers and assistive tech, problems with visual design like contrast, and issues with reading or controlling AI-specific features. The authors also found that these problems depended on the type of interface and how the tool communities handle reports and fixes.
AI developer toolsvisual accessibilityscreen readersassistive technologyuser interface designtopic modelingGitHub Copilotaccessibility reportinginteraction surfacescode editor
Authors
Sabrina Haque, Christoph Csallner
Abstract
AI-assisted developer tools increasingly mediate programming through chat panels, terminal agents, generated diffs, and streaming status output. These interaction surfaces may create visual accessibility barriers for blind, low-vision, and color-vision-deficient developers, yet little is known about how such barriers are reported in public tool ecosystems. We analyze issues and forum discussions from five AI developer tool ecosystems: GitHub Copilot in VS Code, Cursor, Claude Code, OpenAI Codex, and OpenCode. From 2,652 keyword-retrieved candidates, a three-model ensemble identified 600 unanimously positive visual accessibility reports. A stratified manual sanity check supported this conservative selection. Topic modeling and qualitative analysis identified three recurring categories: screen-reader and assistive-technology barriers; visual presentation, contrast, and differentiation problems; and readability, scaling, and control limitations in AI-specific interfaces. The relative prominence of these concerns varied across ecosystems and reflected differences in editor, terminal, chat, diff, and agent interaction surfaces. An exploratory metadata analysis further identified differences in reporter activity and, across the GitHub-based ecosystems, maintainer participation and closure processes. These findings show that the accessibility record of AI developer tools is shaped by both their interaction design and the reporting and maintenance practices of their surrounding ecosystems.