BUILDING A CONCEPTUAL MODEL OF THE WORLD WIDE WEB FOR VISUALLY IMPAIRED USERS

Similar documents
Accessing the World Wide Web By Telephone

WEB BROWSING FOR THE VISUALLY IMPAIRED

Today. Web Accessibility. No class next week. Spring Break

Web site with recorded speech for visually impaired

VMware AirWatch 8 VPAT

What is ADA Website Compliance?

Web Accessibility Model for elearning Website

Seven Steps to Creating an Accessible PowerPoint Slideshow

VMware vrealize Code Stream 6.2 VPAT

Three Steps to Creating an Accessible PDF file (without Adobe Acrobat)

A Semi-automatic Support to Adapt E-Documents in an Accessible and Usable Format for Vision Impaired Users

VMware vrealize Code Stream 1.0 VPAT

Blackboard. Voluntary Product Accessibility Template Blackboard Learn Release 9.1 SP11. (Published January 14, 2013) Contents: Introduction

Seven Steps to Creating an Accessible Microsoft Word document

LetterScroll: Text Entry Using a Wheel for Visually Impaired Users

VPAT. Voluntary Product Accessibility Template. Version 1.3

Salesforce Lightning Dialer

EqTD AUDIT Manual. (Equivalent Text Descriptions Accessibility and Universal Design Information Tool)

What is Accessibility

This is an oral history interview conducted on. October 30, 2003, with IBM researcher Chieko Asakawa and IBM

The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.

Adaptable and Adaptive Web Information Systems. Lecture 1: Introduction

Browsing the Web from a Speech-Based Interface 1

WEBSITE ACCESSIBILITY

Service Cloud Lightning

VPAT. Voluntary Product Accessibility Template. Version 1.3

Marketplace Simulations Accessibility Conformance Report Based on Voluntary Product Accessibility Template (VPAT ) 1

Salesforce Lightning Experience Analytics (Dashboard and Reports)

VPAT. Voluntary Product Accessibility Template. Version 1.3

Universal Design for Learning Tips

CUSTOMIZING HTML BY FILTERING: techniques for making the Internet accessible to the visually handicapped

Salesforce Service Cloud Snap-Ins for Web

Voluntary Product Accessibility Template PowerBroker Identity Services

Teamcenter Voluntary Product Accessibility Template. Summary Table Voluntary Product Accessibility Template

Wimba Voice VPAT. Date: March 25, 2008 Name of Product: Wimba Voice Tools version Contact for more Information:

WHAT BUSINESSES SHOULD KNOW ABOUT WEBSITE ACCESSIBILITY LAWSUITS UNDER THE AMERICANS WITH DISABILITIES ACT

From Electronical Questionnaires to Accessible Maths on Web

Web Content Accessibility Guidelines (WCAG) 2.0 Statement of Compliance

Voluntary Product Accessibility Template

ACCESSIBLE DESIGN THEMES

VPAT. Voluntary Product Accessibility Template. Version 1.3

Sales Cloud Lightning

Voluntary Product Accessibility Template (VPAT )

Adding semantics in web-based digital libraries to support information seeking of blind people

Designing Accessible Websites

I. INTRODUCTION ABSTRACT

California Open Online Library for Education & Accessibility

All Adobe Digital Design Vocabulary Absolute Div Tag Allows you to place any page element exactly where you want it Absolute Link Includes the

Salesforce Lightning Experience

Introduction to Infographics and Accessibility

Agilix Buzz Accessibility Statement ( )

Glasgow eprints Service

VMware vcenter Orchestrator 5.5 VPAT

Wimba Classroom VPAT

VPAT for View 5.1 Server

Voluntary Product Accessibility Template Business Support System (BSS)

Handshake Accessibility Overview

,,NewsReader" - A Comfortable Digital Newspaper and Bookreading System

VPAT Web Content Accessibility Guidelines 2.0 level AA

California Open Online Library for Education & Accessibility

VPAT for VMware vcloud Networking and Security 5.1

UKAAF minimum standards: Accessible PDFs For Assessment

Adding Usability to Web Engineering Models and Tools

Adobe Omniture Discover Voluntary Product Accessibility Template

Salesforce1 - ios App (Phone)

Accessibility FAQ PRESENCE. West Corporation. 100 Enterprise Way, Suite A-300 Scotts Valley, CA

SecurityCenter 508 Compliance

Voluntary Product Accessibility Template (VPAT)

Aspects Regarding the Need of Accessible Information Technology in Computer Assisted Learning for Persons with Disabilities

Accessible and Usable PDF Documents: Techniques for Document Authors Fourth Edition

VMware vcenter Site Recovery Manager 6.1 VPAT

Section 508 Wizard Behdad Payami VP, Sales & Marketing Cerenade

VPAT. Voluntary Product Accessibility Template (VPAT) Summary Table VPAT. Voluntary Product Accessibility Template

Cognitive Disability and Technology: Universal Design Considerations

MULTIMODAL ENHANCEMENTS AND DISTRIBUTION OF DAISY-BOOKS

An Audio View of (L A )TEX Documents Part II

Providing Interactive Site Ma ps for Web Navigation

Ten Ways to Share Your Publications With the World: A Guide to Creating Accessible PDF Documents in Adobe Acrobat Professional 7.

The Practical Side of Teaching the Elderly Visually Impaired Users to Use the

Creating Accessible Adobe PDF Files. A Guide for Document Authors

Web Content Accessibility Guidelines 2.0 Checklist

Guide for Creating Accessible Content in D2L. Office of Distance Education. J u n e 2 1, P a g e 0 27

The Second African UNESCO-UNEVOC TVET Summit E-learning Africa May 2008 GHANA

VMware vsphere Client 6.5 VPAT

Adobe Dreamweaver CS5/6: Learning the Tools

CBORD s Response to Voluntary Product Evaluation Template For GET

Note: This document describes normal operational functionality. It does not include maintenance and troubleshooting procedures.

VPAT FOR WINDCHILL 11.X

HCI: ACCESSIBILITY. Dr Kami Vaniea

VPAT Summary. VPAT Details. Section Web-based Internet information and applications - Detail

Adobe LiveCycle Rights Management ES3 Voluntary Product Accessibility Template

Multimedia for the Web: Creating Digital Excitement. Planning the Multimedia Web Site

VMware ESXi Host Client 6.5 VPAT

Vision Impairment and Computing

Access to Technology: Questions & Challenges

Criteria Status Remarks and Explanations Section Software Applications and Not applicable Not applicable

Introduction. Abstract

Criteria Status Remarks and Explanations Section Software Applications and Not applicable Not applicable. Supports with exceptions

Section Software Applications and Operating Systems - Detail

Section Software Applications and Operating Systems - Detail Criteria Supporting Features Remarks and explanations (a) When software is design

Transcription:

1 of 7 17/01/2007 10:39 BUILDING A CONCEPTUAL MODEL OF THE WORLD WIDE WEB FOR VISUALLY IMPAIRED USERS Mary Zajicek and Chris Powell School of Computing and Mathematical Sciences Oxford Brookes University, Gipsy Lane Campus, Headington, Oxford OX3 OBP, UK Tel: +44 1865 483683 Fax: +44 1865 483666 Email: mzajicek@brookes.ac.uk There has been a discernible shift on the World Wide Web from basic text pages to the use of more complex information structuring techniques such as lists, tables and frames, and multimedia elements such as imagemaps, video and virtual reality. These advances make the interface more information rich for the sighted user, but make life more difficult for the visually impaired user who can only read the textual part of the interface using speech synthesis. The aim the project is to present as much real information contained in the Web page to the visually impaired user as possible. The experimental work described in this paper was aimed at determining how best to sort, group, and annotate the information contained in a Web page to promote the most effective conceptual model in the user. Introduction This paper describes experiments conducted using a helper application WebChat, developed within the project, to find an optimum method for representing the contents of a World Wide Web page for visually impaired users using speech. The modality of WebChat changed in order to incorporate the different features described below and evaluate them for effectiveness and usability. Currently available screen reading products allow the visually impaired user to read the screen using speech synthesis or Braille display hardware. Most of these applications are only capable of reading one line of the screen at a time and the document is accessed in a sequential manner. They are also general purpose and not specifically designed for Web use. However as graphical interface technology develops uninterpreted screen reading becomes less cost effective or effectual as has been shown by the following authors, Laux, McNally, Paciello and Vanderheim (1996), Petrie, Fabrizi and Homatas (1993), Stephanidis, Savidis and Acoumianakis (1995). Our system provided access to conceptually different parts of the Web page using a function key system

2 of 7 17/01/2007 10:39 and different synthesised voices to indicate conceptually different features of text such as headings, links and multimedia objects. Existing facilities for visually impaired access to the Web Web pages are created by the Internet Browser (Netscape Navigator, Mosaic or Internet Explorer are examples) from HyperText Markup Language (HTML) code. HTML incorporates an increasing number of multimedia elements and multimedia presentation can be further enhance by incorporating Java Applets. Software such as WebChat must run alongside the Internet Browser and intercept the HTML code to interpret it for speech output. Problems with inaccessible HTML code Screen readers and WebChat itself rely on HTML code being written in a standard and accessible manner. Sadly many Web sites provide code which is far from accessible as described in O Brien 1996. It is argued that Web sites should be legally bound to provide only standard accessible HTML in the same way that buildings must be accessible for disabled people. Attempts have been made to improve the access of vision impaired users to HTML code as described in Polovina (1996). The International Committee for Document Design (ICADD) was set up to establish a standard Document Type Declaration by which textual information can be successfully transformed for print disabled users into the more accessible ICADD format. This format includes the contextual information that would enable conversion into the existing alternative formats such as Braille, but in a way that can now be interpreted by alternative output software. Alternatively the W3 Access for Blind People (W3ABP) approach exploits the Web s Proxy Server Technology. Web pages can be read via the W3ABP s server. The server automatically changes the format of the Web page, adding certain contextual information, so that it can become meaningful to a user who needs a screen reader. How we presented the pages The aim of these experiments was firstly to investigate ways of orientating visually impaired users to the contents of a Web site and then to present as much real information contained in the Web page as possible. The focus of the work `is on determining how best to sort, group, and annotate elements of the Web page to this end. For sighted users orientation to the contents of a Web site is cognitively demanding. We make decisions like what it is about?, does it really contain the information I am seeking? as quickly as we can by scanning the page to build up a working picture of its contents. Sighted users were observed in active scanning i.e. consciously searching the text (passive scanning will be discussed later) and it was found that they tended first to look for headings, images and links to orientate themselves to the page. If these did not provide a sensible picture they then investigated paragraphs in the main text. The aim was to provide functionally equivalent facilities for active scanning for

3 of 7 17/01/2007 10:39 visually impaired users. The Web page was presented conceptually as a collection of textual objects (consisting of heading and accompanying paragraph) and links. These were ordered hierarchically within heading and sequentially down the page. As HTML headings allow for six levels, in a well designed document they describe a tree structure. This feature is used by WebChat to subset the document and give the user the ability to examine only the subtrees of interest. Navigation of the Web page was achieved by easily locatable keys. By use of the Select headings menu (F7), a heading is selected. The sub-document described by the subtree associated with that heading can then examined by the user with the shifted F2 to shifted F5 keys described below. The tables below show the functionality of the keys used. Table 1. Control Keys Function Key Normal Function Shift Function F1 Read document title Load a URL F2 Read all links Read links under selected heading F3 Read Headings Read headings under selected heading F4 Read entire document Read document under selected heading F5 Read entire dictionary Read dictionary of words under selected heading F6 Select link menu F7 Select heading menu Search for a user-specified word F8 Select bookmark menu Search for interesting words Table 2. Menu Keys Key Function

4 of 7 17/01/2007 10:39 Esc Cancel any menu and return to ready state, Stop any speech Spacebar Pause/resume speech Page up Go to 10th link/heading/bookmark before current position Page down Home End Cursor up/right Cursor down/left Return Go to 10th link/heading/bookmark after current position Go to first link/heading/bookmark Go to last link/heading/bookmark Go to previous link/heading/bookmark Go to next link/heading/bookmark Select the current menu item The links (i.e. anchors) and headings (H1 to H6) in a document are extracted from the document and placed in the Link and Heading lists respectively. These lists are available to the user as an aid to navigation and summarisation. The Menu keys above provide a keyboard-operated menu system where feedback to the user is vocal (Fig. 1). For example, pressing F6 selects the links menu. The first link is read out. Pressing the down cursor key causes the second link to be read out. Once the required link is located using the cursor and page keys, pressing Return will load the associated document (equivalent to clicking on an anchor in a standard web browser). Pressing escape will cancel the menu and return WebChat to its ready state. The Heading and Bookmark menus are used in the same way.

5 of 7 17/01/2007 10:39 Figure 1. Selecting from a menu. Dictionary/Audio scanning The dictionary consists of words from the document after noise words (and, the, to, where etc.) have been removed. Additionally, stem-stripping is used to normalise words before insertion into the dictionary. This avoids the duplication of words where the root is the same, but the suffix is different (e.g. browsing, browsed). The dictionary has two functions : 1) To provide a word index into the document for performing word searches. 2) To provide a summary of the document (passive scanning). The word index can be used by the user to look for a specific word in the document (shift F7), or to scan for any words which match those in the user-maintained interesting word database (a list of words which the user commonly searches for, i.e. those which relate the users interests). The summary can be used to read-out to all the non-noise words in the document. This reduces the time taken to review a document (experiments show around 50% less), enabling the user to scan the document, actively or passively, for anything of interest. This audio scanning attempts to provide the non-sighted user with the audio equivalent of visual scanning. Site orientation using function keys Users could build a model of the information content of the page by trying out the lists of headings, subheadings and links simply by pressing the function keys. Evaluation of Web page structure presentation Inevitably the time taken by the user to orientate themselves to the information content of a Web site was significantly more than the time taken using visual scanning. Therefore evaluation of effectiveness was based purely on information gathered rather than time taken. Three aspects of Web page presentation were evaluated using six user subjects for each aspect. (1) Function key evaluation - Users were observed using the function keys and asked about the functionality they offered. It was found that the system worked well. The facility for locating and selecting a heading and reviewing its associated text was particularly time saving. However users could be

6 of 7 17/01/2007 10:39 disorientated if they became distracted due to the serial nature of speech and the lack of refresh. This is a common problem with speech driven systems which will be addressed in the next version by incorporating a message tagging system. (2) Web site orientation - Users were asked to familiarise themselves with a whole (small) Web site ready to answer questions on what it was about rather than questions about specific information. They were asked general questions designed to determine the extent of their conceptual model of the information available at the site. It was found that the six subjects had built a conceptual model of the information content of the page comparable to that of a sighted user after scanning. (3) Information retrieval - Users were required to use the site as an information source and were given the task of retrieving specific information. It was found that the design of the Web site and length of sentences were major factors in the level of success, mainly due to the uninteresting nature of synthesised speech. Conclusion It is hoped that the results of the work described above will be relevant for both those designing Web pages and those providing extensions to the HyperText Markup Language (HTML) which forms the Web page. By exploring the presentation of data in a different context we also hope to provide insights for those presenting information to sighted users. It cannot be stressed enough that without goodwill on the part of Web page providers who use accessible code, visually impaired users will not be able to use helper applications. The work was funded by the Higher Education Funding Council Executive under the Widening Access to Higher Education initiative. References Laux, L., McNally, P., Paciello, M., Vanderheim, G., 1996, Designing the World Wide Web for People with Disabilities: A User centred Design Approach, Proceedings of ASSETS 96, The Second Annual ACM Conference on Assistive Technologies, ACM, New York O Brien, S., 1996, Multimedia and hypertext, Ability: The Journal of The British Computer Society Disabled Group, Issue 18 Petrie, H., Fabrizi, P., Homatas, G., 1993, Report on user requirements for the accessibility of graphical user interfaces by blind people, Report to the CEC for TIDE Pilot Action Project 103: Graphical User Interfaces for Blind Persons, London, Royal National Institute

7 of 7 17/01/2007 10:39 for the Blind. Polovina, S., 1996, Weaving the Web: Designing for Universal Access, Ability: The Journal of The British Computer Society Disabled Group, Issue 18 Stephanidis, C., Savidis, A., Acoumianakis, D., 1995, Tools for User Interfaces For All, Proceedings Second TIDE Congress, Amsterdam, IOS Press Back to publication list.