Accessibility Designer: Visualizing Usability for the Blind
Hironobu Takagi, Chieko Asakawa, Kentarou Fukuda, Junji Maeda · 2003 · Proceedings of the 6th International ACM SIGACCESS Conference on Computers and Accessibility (Assets '04) · doi:10.1145/1028630.1028662
Summary
This paper from IBM's Tokyo Research Laboratory presents Accessibility Designer (aDesigner), a tool that goes beyond conventional accessibility checkers by visualising the usability of web pages for blind screen reader users rather than merely checking HTML compliance. The authors identify a critical gap: existing accessibility evaluation tools focus on syntactic correctness (e.g., whether images have alt text) but cannot assess whether a technically compliant page is actually usable by a blind person. Three key problems are identified with current checkers: they focus too much on compliance rather than real usability; they rely only on static HTML syntax checking; and they pay no attention to "time-oriented" usability factors. aDesigner addresses these by introducing "Blind Usability Visualization," which uses background colour gradations to represent the estimated time it takes a screen reader user to reach each element on a page — white for immediately accessible content and progressively darker colours through to black for content requiring 120 seconds or more. The tool calculates these reaching times by modelling the voice browser's reading order, analysing intra-page link structures as a shortest-path graph problem, and accounting for heading navigation and skip links. The tool retains the visual layout of the original page while overlaying this time-based colour coding, allowing sighted web designers to immediately grasp usability problems they would otherwise need to experience through a screen reader.
Key findings
Evaluation across twelve major newspaper websites (six US, six Japanese) revealed dramatic differences in reaching times to main content areas: the most accessible site (Tokyo Nikkei) allowed users to reach articles in about 10 seconds, while the least accessible sites took one to three minutes. Sites with heading tags and skip links showed consistently lighter (faster) visualisations. A skip-link audit of six accessible websites found that while most pages had skip links, 6% of IBM's and CNN's pages had broken skip links (non-functional anchors), which the authors argue is enough to erode blind users' trust in the feature. The tool also detects inappropriate alt texts ("spacer", "line", "button"), redundant texts (duplicate alt text and link text near images), and null alt texts that voice browsers cannot suppress. In a practical deployment developing an intranet web application of over 200 JSP pages, aDesigner reduced what was estimated to be months of compliance work to just a few weeks, while achieving a higher level of actual usability than mere compliance would have provided. Non-accessibility-specialist developers were able to participate effectively in repairs using the visual feedback.
Relevance
This paper articulates a distinction between accessibility compliance and accessibility usability that remains one of the most important challenges in web accessibility practice today. The insight that a page can pass every automated check while still being practically unusable for a screen reader user anticipated the limitations that the accessibility community continues to grapple with two decades later. The reaching-time visualisation concept — making the invisible experience of screen reader navigation visible to sighted designers — is a powerful approach to building empathy and understanding without requiring designers to become screen reader experts. The tool's graph-based model for calculating reaching times, which accounts for skip links, heading navigation, and intra-page links as a shortest-path problem, provides a quantitative framework for what is usually assessed qualitatively. For practitioners, aDesigner's findings about broken skip links (6% failure rate on major sites) highlight the importance of not just implementing accessibility features but maintaining them over time. The practical deployment showing that visual usability feedback enabled non-specialist developers to make effective repairs validates the tool's approach and suggests that visual representations of screen reader experience can democratise accessibility work beyond specialist teams.
Tags: web accessibility · accessibility testing · screen reader · blindness and low vision · accessibility tools · usability · automated testing · skip navigation · alt text · heading hierarchy · accessibility evaluation
Standards referenced: Section 508 · WCAG