User Interface of a Home Page Reader
Chieko Asakawa, Takashi Itoh · 1998 · Proceedings of the Third International ACM Conference on Assistive Technologies (Assets '98) · doi:10.1145/274497.274526
Summary
This paper from IBM Japan's Tokyo Research Laboratory describes the design and evaluation of Home Page Reader, one of the earliest dedicated web browsers for blind users, which became an IBM Japan product in October 1997. The paper opens by framing the information access problem for blind people in Japan, who at the time had only braille books and cassette tapes as published information sources — with conversion taking six months to a year for braille and three months for tape. The authors, including Chieko Asakawa who is herself blind, first investigated existing nonvisual web access methods in Japan, which relied on DOS-based text browsers accessed through Bulletin Board Systems or Telnet to UNIX environments running Lynx. These approaches failed to exploit the Web's advantages: hyperlinks were hard to find, two-dimensional layouts couldn't be read correctly, and scrolling was extremely difficult nonvisually. Home Page Reader took a fundamentally different approach by analysing HTML tags directly rather than reading screen contents, running on Windows 95 with Netscape Navigator and the ProTALKER 97 text-to-speech engine. The system's entire navigation interface was built around a 17-key numeric keypad, with over 100 functions assigned through intuitive key combinations including an extended key modifier.
Key findings
The system introduced several innovative design decisions that influenced subsequent screen reader development. Hyperlinks were read in a female voice while plain text used a male voice, allowing users to instantly identify all links on a page while listening to continuous reading — a significant advantage over competitors that either prefixed links with the word "link" (described as irritating) or didn't differentiate them at all. HTML tags were parsed and converted to voice data rather than simply read, enabling access to tables (read column by column rather than line by line), clickable maps (reading ALT text or URLs from AREA tags), frames (reading frame names), and form elements. A fast-forward key allowed rapid scanning through content, slowing at natural stops like commas, periods, and hyperlinks. Evaluation with 60 blind users across three experience levels (beginner, intermediate, advanced) showed that beginners needed only 30 minutes to learn basic functions after grasping homepage concepts, intermediate users needed 20 minutes, and advanced users 17 minutes. Beginners required just eight keys for basic web reading. Advanced users learned nearly all functions within three days using the online manual and key-help mode. The system's synchronisation with Netscape Navigator enabled sighted volunteers to assist blind users — a practical consideration that broadened the support ecosystem.
Relevance
This paper is historically significant as one of the earliest descriptions of a dedicated nonvisual web browser that became a commercial product. Chieko Asakawa, the lead author and a blind researcher, went on to become one of the most influential figures in web accessibility, and Home Page Reader evolved through several versions at IBM. Many of the design principles introduced here became standard in modern screen readers: parsing HTML structure rather than reading screen pixels, using voice differentiation to convey semantic information (links vs. text), providing multiple navigation granularities (character, line, link), and fast-scanning modes. The paper's emphasis on designing for beginners — recognising that the Web was a new medium that blind users needed to learn conceptually, not just operationally — remains relevant for any new technology platform. The honest acknowledgement that the system couldn't solve problems caused by inaccessible content (images without alt text, complex layouts) anticipated the web accessibility standards movement that would soon produce WCAG 1.0 in 1999.
Tags: screen readers · web accessibility · blindness · text-to-speech · nonvisual web access · user interface design · assistive technology
Standards referenced: HTML 3.0