Web Accessibility Issues from the User Perspective

Jenny Craven, Research AssociateCentre for Research In library and

Information Management (CERLIM)Manchester Metropolitan University

j.craven@mmu.ac.uk

Introduction – awareness ofthe following?

• Web accessibility and/or Web usability

• Design for All – Universal Design

• W3C/WAI

• Web Content Accessibility Guidelines (WCAG)

• PAS 78: Guide to good practice in commissioning accessible websites

• Jakob Nielsen’s Usability Heuristics

What is accessibility?

Ensuring systems and interfaces can be visited, understood and interacted with by

all users through:

• Access to hardware and software

• Use of appropriate assistive technology

• Ensuring information can be interpreted by the user and the technology.

What is accessibility?

• Accessibility between technologies– o/s – application – assistive technology

• Accessibility between technology and humans– o/s – application – AT – user (interface)

• Accessibility between humans and the context where technology is used– e.g. interlending transactions

Source: Holbye, S. T4P conference, Kristiansand Norway. June 25-27 2007

Typical Web Interface

HTML, XML and CSS Coding

Potential accessibility and usability issues

Why make information accessible?

• Information increasingly being provided in electronic formats via PCs, smart phones, TV, hand held computers etc

• The business case: accessibility = commercial success

• Inclusive society - information for all• Legislation e.g. UK Disability Discrimination Act,

1995, SENDA, 2001, Disability Duty, 2006

From a user perspective, it helps people ………..

• With disabilities e.g. visual, mobility, learning, hearing.

• Working in a noisy environment• Using a PC with a slow connection• Using small screen web-based devices e.g.

smart phones, hand-held computers etc

Accessible design helps people to independently access and interact with

web-based content

Alternative ways to access web services

Assistive, Adaptive, Access Technology:• Screen readers• Magnifiers• Scanners• Braille output• Voice recognition• Alternative mouse devicesAlso:• Mobile and Handheld access

Accessible Web Design

Based on W3C/WAI Recommendations:• Text descriptions for all images and sound• Contrasting colours• Plain fonts • Adjustable font sizes• Properly labelled frames and tables• Appropriate text for hypertext links (avoid ‘click here’)• Alternatives for scripts, applets, plug-ins etc.• Use of Accessible Style Sheets (CSS)

Source: http://www.w3.org/WAI/

Usability issues

• Unambiguous language

• Clear and consistent layout

• Logical navigation of forms, search screens etc

• Warning of new windows opening

• User control, e.g. to adjust screen display

• Dynamic interaction: online chat, quizzes, Web 2.0

Web Accessibility in Context:Some relevant inter lending issues

• Access to library materials:– Library website and catalogue– Online databases

• Inter lending request forms:– Downloadable– Online

• Other issues:– Online payments– Electronic document delivery– Notification – email, text messaging– Digital signatures

Access to Library Materials

• Library website and catalogue– Adhere to web accessibility guidelines and recommendations– Terminology should be meaningful to general public– Avoid repeated link descriptions to different targets– Cut down on multiple links to the same place– Avoid over use of acronyms

• External resources– Is there a policy for the selection of external resources?– Are there guidelines for selection of accessible resources?– Are users provided with a description of how best to access the

resource as well as resource description?

• E-materials (to be covered in other presentations)

Interlending Request FormsDownloading forms• Problems:

– PDF can be inaccessible, can lead to…– Loss of independence– Confusing presentation/download instructions

Online request forms• Problems:

– No logical order when using Tab key– Poor navigation when using drop-down menus– Form labels (e.g. name) not placed next to form

element (e.g. edit box)– Mouse dependent

Interlending Request Forms

Downloading forms• Solutions:

– Accessible PDF (tagged for navigation)– Providing choices (PDF, Word, HTML, etc)– Clear presentation/download instructions

Online request forms• Solutions:

– Keyboard accessible, logical, easy to use– Adhere to guidelines on creating accessible online

forms; conduct user testing– Reporting mechanism for problems (email, telephone,

online etc)

Example of an online form

Example of an online form

Other issues

• Online payments – similar to online form issues

• Electronic document delivery (covered in other presentations)

• Notification – email, text messaging - similar to web accessibility issues (but on a small screen)

• Digital signatures – un-resolved?

User Perspective (1)• Present information in a logical order, using

simple and relevant language• Keep users informed about what is going on

e.g. if they need to go back to complete a field, if they have to click on a copyright agreement box, the number of pages in a form

• Follow standard conventions e.g. terminology, order of information, command buttons (search, submit)

• Give users choices e.g. download options, screen display

Adapted from: www.useit.com/papers/heuristic/heuristic_list.html

User Perspective (2)

• Error prevention – ask users to confirm important actions before submitting

• Provide helpful error messages e.g. an example of how a date or ISBN number should be submitted

• Make objects, actions and options visible so the user doesn’t have to remember them e.g. provide a breadcrumb trail to allow them to track back; consistent layout

• Simple design• Helpful help documentation!

Adapted from: www.useit.com/papers/heuristic/heuristic_list.html

Simple Evaluation:

• Look and feel – colours, language, terminology, structure

• Look for good navigational aids, e.g. search facility, return to home page

• Adjustable font sizes and styles

• Choice of downloadable forms

• Navigating around online forms using Tab key

Other ways to evaluate

• Automated checking tools: WebXact, WAVE, Cynthia Says

• Validation e.g. HTML Tidy• Expert testing• Accessibility and Usability Audits• User testingSee also: W3C/WAI Evaluating Web

Sites: http://www.w3.org/WAI/eval/

Conclusion

• 'Design for all' can be difficult to achieve – be prepared to prioritise

• Evaluate your website using a combination of manual and automated tools, but also….

• … Include users in your assessments and feedback mechanisms

• Participate in accessibility related discussion groups and forums

• Take advantage of all the free advice and guideance available…

Advice on accessibility/usability

• World Wide Web Consortium - Web Accessibility Initiative: http://www.w3.org/WAI/

• PAS 78: http://www.drc-gb.org/library/website_accessibility_guidance/pas_78.aspx

• Jakob Nielsen’s Usability website: http://www.use-it.com

• Just Ask: Integrating Accessibility Throughout Design (includes usability issues): http://www.uiaccess.com/accessucd/index.html

• CERLIM research on accessibility and usability: http://www.cerlim.ac.uk/projects/index-accessib.php

Jenny Craven, Research Associate

Centre for Research In library and Information Management (CERLIM)

Manchester Metropolitan University

j.craven@mmu.ac.uk