Web Accessibility:
Who is it for?
What are the Guidelines?

Dr Andrew Arch
Accessible Information Solutions

OZeWAI 2005

Web Accessibility

"The power of the web is in its universality. Access by everyone regardless of disability is an essential aspect."
"One web for anyone, everywhere, on anything"

Tim Berners-Lee, W3C Director and inventor of the World Wide Web, October 1997 and October 2004

"Accessible design is good design."

Steve Ballmer, President of Microsoft, August 2001

Definition

Web accessibility means that people with disabilities can use the Web, more specifically, it means they can:

perceive, understand and navigate the Web
interact with the Web
contribute to the Web

http://www.w3.org/WAI/intro/accessibility.php

How People with Disabilities use the Web

Meet:

Gordon
Cutis
Peter
and others

How People with Disabilities Use the Web - References

Scenarios & Personas:

www.w3.org/WAI/EO/Drafts/PWD-Use-Web/
www.ittatc.org/technical/access-ucd/personas_eg.php

Video: Keeping Web Accessibility in Mind

www.webaim.org/info/asdvideo/

Video: Websites that Work

Download:
http://ftp.fit.fraunhofer.de/bika/WebSitesThatWork/english/
Steaming (old version):
http://video.strath.ac.uk/streams/rnib.wvx

Video: Microsoft Case Studies

www.microsoft.com/enable/casestudy/videos.aspx

Accessibility is Experiential

Person is able to use data, information and services as effectively as someone without a disability
Compliance with technical rules (Web Content Accessibility Guidelines) is necessary, but not sufficient

Components of Web Accessibility

The develops Web accessibility guidelines for the different components:

ATAG)
WCAG)
UAAG)

WAI guidelines are based on the fundamental technical specifications of the Web, and are developed in coordination with:

(HTML, XML, CSS, SVG, SMIL, etc.)

http://www.w3.org/WAI/intro/components.php

Web Content Accessibility Guidelines (WCAG 1.0)

Collaborative International Program of the W3C - Web Accessibility Initiative (WAI)
The Content Guidelines are a 'stable' document (released May 1999)

Techniques, Notes and Errata updated (slightly) to keep pace with technology

Complimentary Guidelines for:

Authoring Tools
User Agents

WCAG 1.0

14 Guidelines:

Text equivalents for non-text elements
Do not use colour alone
Use markup and stylesheets properly
Specify natural language
Tables that transform gracefully
New technologies that transform gracefully

WCAG 1.0 … Cont.

User control of time sensitive material
Accessibility of embedded interfaces
Device independent
Use interim solutions for older technologies
Use W3C technologies
Provide context and orienting information
Clear navigation
Documents are clear and simple

1. Text equivalents

Provide content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content.
5 checkpoints

Not just about images, also multimedia, PDF and other non-text elements

2. Colour

Ensure that text and graphics are understandable when viewed without colour.
2 checkpoints

Don't use colour alone as an indicator

BUT, colour is very useful for most people

Ensure sufficient contrast

3. Markup and Style Sheets

Mark up documents with the proper structural elements. Control presentation with style sheets rather than with presentation elements and attributes.
7 checkpoints

Use markup and CSS properly
Allow for graceful degradation

4. Language indicators

Use markup that facilitates pronunciation or interpretation of abbreviated or foreign text.
3 checkpoints

Language changes
Default language
Acronyms and Abbreviations

5. Tables

Ensure that tables have necessary markup to be transformed by accessible browsers and other user agents.
6 checkpoints

Correct data table markup
Care with layout tables

6. New technologies

Ensure that pages are accessible even when newer technologies are not supported or are turned off.
6 checkpoints

Graceful degradation for style sheet support
Pages usable when scripting, applets and plugins not supported
Dynamic content is accessible, or alternative information is updated appropriately

7. Time sensitive changes

Ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped.
5 checkpoints

Flickering and blinking
Moving content
Auto-refresh and Auto-redirect

8. Embedded interfaces

Ensure that the user interface follows principles of accessible design: device-independent access to functionality, keyboard operability, self-voicing, etc.
1 checkpoint

Compatibility with assistive devices and technology

9. Device independence

Use features that enable activation of page elements via a variety of input devices.
5 checkpoints

Client-side image maps
Logical event handlers

keyboard accessible

Logical tab order
Keyboard shortcuts

10. Interim solutions

Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly.
5 checkpoints

Pop-ups and new windows
Label positioning in forms
Separating adjacent links
2 checkpoints deprecated

Place holding text & Alternatives for layout tables

11. Use W3C technologies

Use W3C technologies (according to specification) and follow accessibility guidelines.
4 checkpoints

Use the latest version (HTML, CSS)
Text-only pages not an option

12. Context and orientation

Provide context and orientation information to help users understand complex pages or elements.
4 checkpoints

Frames
Dividing information into groups
Explicit label association in forms

13. Clear navigation

Provide clear and consistent navigation mechanisms to increase the likelihood that a person will find what they are looking for at a site.
10 checkpoints

Clear links
Metadata
Sitemaps and 'table of contents'
Navigation bars and 'skip to content'
Front loaded information (links, headings, text)

14. Clear & simple documents

Ensure that documents are clear and simple so they may be more easily understood.
3 checkpoints

Clear and simple language
Use graphics (and auditory files)
Consistent presentation style

WCAG 1.0 - Priorities

65 Checkpoints

Priority 1 Checkpoints the "musts"
Priority 2 Checkpoints the "shoulds"
Priority 3 Checkpoints the "mays"

Priority also determined by function & context

WGAC 1.0 - Conformance

Conformance can be claimed at three levels:

Level "A" (All P 1 checkpoints)
Level "Double A" (All P 1 PLUS all P2 checkpoints
Level "Triple A"
(All P1 PLUS all P2 PLUS all P3 checkpoints)

Need to achieve a minimum of conformance at Level Double A to be effective

We also recommend a few key P3 checkpoints

Thankyou

Andrew Arch

Accessible Information Solutions
Vision Australia
454 Glenferrie Road, Kooyong Vic 3144

03 9864 9282

Andrew.Arch@nils.org.au