A Prototype of Google Interfaces Modified for Simplifying Interaction for Blind Users
Patrizia Andronico, Marina Buzzi, Carlos Castillo, Barbara Leporini · 2006 · Proceedings of the 8th International ACM SIGACCESS Conference on Computers and Accessibility (Assets '06) · doi:10.1145/1168987.1169048
Summary
This demo paper from Italy's National Research Council and Università di Roma presents a prototype that restructures Google's search and results pages to be more usable for blind screen reader users. Previous research had shown that blind users took 2.5 times longer than sighted users to find information via search engines, with blind participants spending twice as long exploring results and three times as long exploring corresponding web pages. The prototype uses Google APIs to retrieve search results via SOAP/XML, then applies XSLT transformations to restructure the content according to eight guidelines the researchers had previously developed for accessible search engine interaction. Critically, the visual appearance of the modified pages was kept identical to the original Google — only the underlying HTML structure and code order were changed. The home page was reorganized into four logically grouped sections with heading levels, while the results page was subdivided into seven clearly labeled sections. Results were numbered and separated by blank lines (rather than being visually run together), access keys (tab shortcuts) were added for rapid navigation, and audio tones were introduced to signal events like "focus on search box" and "search successful."
Key findings
Remote user testing with 12 totally blind JAWS users across 10 tasks showed strong positive results. All participants declared the modified home page simplified the search setup, and 11 of 12 found the modified results interface clearer and easier to use. The most skilled user reported a 20-30% reduction in time to reach desired results compared to the original Google interface. Of 12 participants, 11 acknowledged that simplified interaction and greater clarity in result exploration reduced the time needed to carry out searches. Participants valued the numbered results with clear separation, heading-level structure for section navigation, tab-key shortcuts, hidden labels, and different visiting order assigned to links. The audio feedback tones for key events were also positively received. The XSLT transformation processing time was always less than 0.1 seconds, and the modified pages were sometimes faster than the standard Google site since the transmitted data was smaller.
Relevance
This paper demonstrates a powerful principle: the accessibility of web applications for screen reader users can often be dramatically improved by restructuring the HTML without changing the visual design at all. The gap between visual and structural presentation — where a page looks fine but is poorly organized for sequential audio navigation — remains one of the most common accessibility failures today. The specific techniques used (logical heading hierarchy, numbered results, section grouping, keyboard shortcuts, audio feedback) are best practices that apply far beyond search engines to any content-rich web application. The finding that blind users experienced 2.5x slower information retrieval highlights the real productivity cost of inaccessible interfaces. While Google has since developed its own Accessible Search tool (which prioritizes accessible result pages), this research focused on the search interface itself — arguing correctly that both the search tool and the results it returns need to be accessible. The prototype's approach of using XSLT to transform existing pages into accessible versions without modifying the original also anticipated modern accessibility overlay concepts, though this implementation was more rigorous in its structural restructuring.
Tags: search engine accessibility · blind users · screen readers · JAWS · usability · Google · XSLT · heading structure · keyboard navigation