skip to main content
10.1145/1028630.1028662acmconferencesArticle/Chapter ViewAbstractPublication PagesassetsConference Proceedingsconference-collections
Article

Accessibility designer: visualizing usability for the blind

Published:01 September 2003Publication History

ABSTRACT

These days, accessibility-related regulations and guidelines have been accelerating the improvement of Web accessibility. One of the accelerating factors is the development and deployment of accessibility evaluation tools for authoring time and repair time. They mainly focus on creating compliant Web sites by analyzing the HTML syntax of pages, and report that pages are compliant when there are no syntactical errors. However, such compliant pages are often not truly usable by blind users. This is because current evaluation tools merely check if the HTML tags are appropriately used to be compliant with regulations and guidelines. It would be better if such tools paid more attention to real usability, especially on time-oriented usability factors, such as the speed to reach target content, the ease of understanding the page structure, and the navigability, in order to help Web designers to create not simply compliant pages but also usable pages for the blind. Therefore, we decided to develop Accessibility Designer (aDesigner), which has capabilities to visualize blind users' usability by using colors and gradations. The visualization function allows Web designers to grasp the weak points in their pages, and to recognize how accessible or inaccessible their pages are at a glance. In this paper, after reviewing the related work, we describe our approach to visualize blind users' usability followed by an overview of Accessibility Designer. We then report on our evaluations of real Web sites using Accessibility Designer. After discussing the results, we conclude the paper.

References

  1. Section 508 of the Rehabilitation Act; see http://www.section508.gov/.Google ScholarGoogle Scholar
  2. Bobby, Watchfire Corporation; see http://bobby.watchfire.com/.Google ScholarGoogle Scholar
  3. LiFT, http://www.usablenet.com/.Google ScholarGoogle Scholar
  4. A-Prompt, University of Toronto, http://aprompt.snow.utoronto.ca/Google ScholarGoogle Scholar
  5. Asakawa, C. et al, Automatic Web Content Accessibility Compliance Tool for Section 508, Proc. Technology and Persons with Disabilities conference (CSUN 2002), 2002.Google ScholarGoogle Scholar
  6. Asakawa, C., Itoh, T., User Interface of a Home Page Reader, Proc. the 3rd international ACM SIGCAPH conference on Assistive Technologies (ASSETS '98), pp.149--156, 1998. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. JAWS, Freedom Scientific Inc., http://www.freedomscientific.com/Google ScholarGoogle Scholar
  8. Asakawa, C., Takagi, H., et al. Maximum listening speeds for the blind, Proc. Conf. of International Community for Auditory Display 2003, 2003.Ivory, M.Y.Google ScholarGoogle Scholar
  9. Hearst, M.A, The state of the art in automating usability evaluation of user interfaces, ACM Computing Surveys (CSUR), Vol. 33 Issue 4, pp. 470--516, 2001. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. Vischeck, http://www.vischeck.com/Google ScholarGoogle Scholar
  11. Maeda, J., Fukuda, K., Takagi, H., Asakawa, C., Web accessibility technology at TRL, IBM Research and Development Journal, 2004. (on press) Kasday, L.R., A Tool to Evaluate Universal Web Accessibility, Proc. the 2000 conference on Universal Usability (ACM), pp. 161--162, 2000. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. WAVE 3.0 Accessibility Tool, see http://www.wave.webaim.org/Google ScholarGoogle Scholar
  13. Theofanos, F.M., Redish, J., Bridging the gap: between accessibility and usability, Interactions, Vol 10, Issue 6, pp. 36--51, 2003. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. aDesigner, http://www.alphaworks.ibm.com/tech/adesignerGoogle ScholarGoogle Scholar
  15. Standard Widget Toolkit, http://www.eclipse.org/swt/Google ScholarGoogle Scholar

Index Terms

  1. Accessibility designer: visualizing usability for the blind

          Recommendations

          Reviews

          Susan Loretta Fowler

          When is a Web site actually usable by people who are fully or partially blind__ __ Is it enough to pass accessibility compliance tests__ __ Programs like Bobby (http://bobby.watchfire.com) do check that all pictures have ALT text, and that headings are compliant with regulations and guidelines. However, as the authors point out, rote compliance isn't enough. For example, developers know to provide alternate descriptive text for all pictures, but they often insert meaningless descriptions, such as "blank space" or "photo." Since most accessibility checkers look only for missing ALT text, but not for inappropriate ALT text, you can have a compliant Web site that is neither useful nor usable. This is where aDesigner steps in (you can download a copy from http://www.alphaworks.ibm.com/tech/adesigner). The program uses a new method that the authors call blind usability visualization. This method lets sighted Web developers tell at a glance how usable their entire site is for blind or partially sighted users. There are three parts to the evaluation process: Showing how long it takes to reach each part of the page, by using background colors. The darker the color, the more inaccessible that part of the page is. Showing which areas are accessible or inaccessible, and the order in which a voice browser will read each one, by filling them with lighter and darker colors. Showing which text is either extracted or generated by standard voice browsers without changing the layouts. Examples are ALT text, notification messages for the start and end of forms, and skip-links, which let voice browser users jump directly to various parts of the page. The paper describes the program, a set of evaluations against actual news sites, and a description of what happened when the authors used the program on one of their own intranet sites. This site had over 200 JavaServer Pages (JSPs), and a few static hypertext markup language (HTML) pages; with the help of aDesigner, the authors reduced the time needed to fix the site from months to a few weeks. If your sites need to comply with Section 508 rules, you would do well to read this paper. Takagi, Asakawa, Fukuda, and Maeda do an excellent job of describing problems most sighted designers and usability engineers may not have thought of. Better yet, they may have provided the solution as well. Online Computing Reviews Service

          Access critical reviews of Computing literature here

          Become a reviewer for Computing Reviews.

          Comments

          Login options

          Check if you have access through your login credentials or your institution to get full access on this article.

          Sign in
          • Published in

            cover image ACM Conferences
            Assets '04: Proceedings of the 6th international ACM SIGACCESS conference on Computers and accessibility
            October 2004
            202 pages
            ISBN:158113911X
            DOI:10.1145/1028630
            • cover image ACM SIGACCESS Accessibility and Computing
              ACM SIGACCESS Accessibility and Computing Just Accepted
              Sept. 2003 - Jan. 2004
              192 pages
              ISSN:1558-2337
              EISSN:1558-1187
              DOI:10.1145/1029014
              Issue’s Table of Contents

            Copyright © 2003 ACM

            Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

            Publisher

            Association for Computing Machinery

            New York, NY, United States

            Publication History

            • Published: 1 September 2003

            Permissions

            Request permissions about this article.

            Request Permissions

            Check for updates

            Qualifiers

            • Article

            Acceptance Rates

            Assets '04 Paper Acceptance Rate25of47submissions,53%Overall Acceptance Rate436of1,556submissions,28%

          PDF Format

          View or Download as a PDF file.

          PDF

          eReader

          View online with eReader.

          eReader