Accessible Web Development: Opportunities to Improve the Education and Practice of web Development with a Screen Reader
Claire Ferrari, Amy Hurst · 2021 · ACM Transactions on Accessible Computing · doi:10.1145/3458024
Summary
This paper investigates accessibility barriers faced by blind web developers in both educational and professional contexts. The researchers employed a Comprehensive Literature Review (CLR) methodology—synthesizing academic literature, blog posts by blind programmers, email list threads, and observations from accessible web development workshops—followed by interviews with 12 blind programmers (averaging 12 years of experience). The study identifies five broad accessibility issue categories: (1) visual information without accessible equivalents, (2) orienting/knowing one's location in code, (3) navigation challenges, (4) lack of support from instructors and colleagues, and (5) knowledge and use of supportive technologies. Web development presents unique challenges beyond general programming accessibility: wireframing software is largely inaccessible, demonstrations of CSS and visual design concepts lack accessible explanations, blind developers cannot independently verify computed CSS outputs, and browser-based developer tools have poor screen reader support.
Key findings
All 12 interview participants reported encountering visual information without accessible equivalents, making this the most prevalent issue category. Eleven participants struggled with navigation, and 10 reported lack of support from educators and employers. Notably, participants used creative workarounds: many (n=7) deliberately avoid front-end development, focusing on back-end work where visual design verification is unnecessary. Others use CSS frameworks like Bootstrap to create layouts with grid systems while minimizing direct CSS work, collaborate with sighted colleagues for design feedback, or use services like AIRA for visual interpretation. Nine participants reported using both Braille and speech synthesis when coding—speech provides quick overview while Braille enables detailed examination of syntax. The majority of students reported being largely self-taught, spending approximately 70% of their learning time finding alternative resources online rather than using course materials. Participants suggested future tools leveraging AI for design verification, tactile interfaces for spatial layout understanding, and collaborative communities of practice.
Relevance
This research has direct implications for CS education, tool development, and workplace practices. For educators, the findings highlight that web development curricula—particularly CSS and visual design instruction—systematically exclude blind learners through inaccessible demonstrations, wireframing software, and validation tools. Institutions must apply accessibility best practices to course materials and test tools with screen readers before requiring their use. For tool developers, browser-based developer tools, IDEs, and design software need significant accessibility improvements; the NVDA Developer Toolkit was cited as a useful but limited solution for CSS inspection. For employers, the research reveals that blind developers often gravitate toward back-end roles not by preference but because front-end work requires inaccessible visual verification—organizations should provide collaborative workflows and accessible tooling. The 44.2% employment rate for people with visual disabilities versus 75.5% for those without underscores the urgency of removing these barriers to web development careers.
Tags: blind programmers · screen readers · web development · CSS · accessible education · IDE accessibility · visual impairment · inclusive curriculum · developer tools
Standards referenced: WCAG · ATAG