Transcript Non-Traditional Access to a Traditional Interface

Non-Traditional Access
to a Traditional Interface
…one more user scenario
CHI Atlanta | February 2003 | [email protected]
Overview of Presentation

Why another perspective on design?



What process modifications?



Context of access considerations
Physical vs. Virtual
Design it right
Retrofit (“This Old Website”)
Resources


The Web as Ultimate Reference
Concepts | Coding
Why more design effort?

Information presents access barriers
comparable to the build environment

Current technology enables universal access.
However, universal design is not easy to
accomplish without both awareness of
disability constraints and sophisticated use of
technology
Original Design | Clever Fix?
Context: access consideration

“Traditional” design is often inaccessible
Context: transportation
Context: hotel (Radisson)
The public areas feature ramps, elevators with braille,
convenient handicap parking, and a wheelchair accessible
ramp which connects to the shopping area. Upon request
the following are available to hearing-impaired guests:
telephone visual ringing device, a visual door knock light,
close-captioned television decoder, a special alarm clock
and Telecommunications Device for the Deaf (TDD).
Seeing eye dogs are permitted. Should a situation
warrant, special emergency procedures place disabled
travelers on priority status.
All suites, restaurants and lounges are handicap
accessible, while a select group of suites are fullyequipped to meet the special needs of these travelers.
These barrier-free suites also contain a security peep hole
at wheelchair level, an adjustable shower head and a
smoke detector visual alarm.
As a service to guests, the resort has designated 165
suites for non-smoking and 11 suites are built to
accommodate the physically disabled.
Access: conference proceedings
Context: digital information

Challenges




Mobility impairments
Vision impairments
Hearing impairments
mouse
GUI
Solution

Design for text-level access
audio / beeps
Context: digital information

Challenges




Mobility impairments
Vision impairments
Hearing impairments
Solution

Design for text-level access
mouse
GUI
audio / beeps
Information Architecture

User-Centric / Various Audiences:




High-bandwidth vs. Low-bandwidth
International / language issues
Access issues (multiple devices, platforms)
Design for the separation of:



Content
Structure
Format
Information Architecture
Jakob Nielsen's Alertbox, January 27, 2003:
Voice Interfaces: Assessing the Potential
Summary:
Visual interfaces are inherently superior to auditory
interfaces for many tasks. The Star Trek fantasy of speaking
to your computer is not the most fruitful path to usable
systems.
Voice interfaces will not replace screens as the medium of choice for most
user interfaces.
Traditional steps in Design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Traditional steps in design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Is Access by People
with Disabilities a
Requirement?
Traditional steps in design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Are People with
Disabilities in the User
Profiles?
Traditional steps in design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Do we have a
mouse-only scenario?
Traditional steps in design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Is the site essentially
hierarchical?
Traditional steps in design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Clear separation of
content and
presentation?
“Flash” used for core
functions?
Traditional steps in design

Macro Design








Gather requirements
Develop user profiles
Develop user scenarios
Initial structure
Aesthetic considerations
Usability considerations
Implement
Test
Do we have inclusive
usability evaluations?
(Paper / interactive model)
How to experience site access




User interviews
(interview people with disabilities)
Lynx
(text only browser)
Netscape / Internet Explorer with images off
(semi-text only browser)
IBM’s Home Page Reader
(download demo)
I.E.
Lynx
Begin
Dropdown
Lynx
I.E.
No images
No CSS
Reasonable accommodation

Usable vs. Useful

Usable with synthetics speech is enough…
Useful is a client-side issue
(assistive technology)
Essential techniques

http://www.w3.org/WAI/References/tips.gif
Essential techniques




Images: Use the alt attribute to describe the function of each visual
Image Maps: Use client-side MAP and text for hotspots
Multimedia: Provide captioning and transcripts of audio and descriptions of video
Links: Use text that makes sense when read out of context. For example, avoid
“click here.”

Page Organization:

Charts and Graphs: Summarize or use the longdesc attribute.
Scripts, applets & plug-ins: Provide alternate content in case active

Use headings, lists, and consistent structure. Use CSS for
layout and style where possible.
features are inaccessible or unsupported.
 Frames: Use noframes and meaningful titles.


Tables: Make line-by-line sensible. Summarize.
Check Your Work: www.w3.og/TR/WAI-WEBCONTENT
References for Universal Design

The World Wide Web Consortium's Web Accessibility
Initiative (WAI) (http://www.w3.org/WAI/)


Federal IT Accessibility Initiative
(http://www.section508.gov/)





The standards bearer, publishes working and final drafts of the "WAI Accessibility
Guidelines: Page Authoring"
Section 508 requires that Federal agencies' electronic and information technology is
accessible to people with disabilities. The Federal Information Technology Accessibility
Initiative is a Federal government interagency effort to offer information and technical
assistance to assist in the successful implementation of Section 508.
IBM Accessibility Center (http://www.ibm.com/able/)
Sun Java Accessibility Guidelines
(http://java.sun.com/products/jfc/jaccess-1.0/doc/FAQ.html)
Apple Disability Guidelines
(http://www.apple.com/education/k12/disability/)
Microsoft Accessibility and Disabilities Site
(http://www.microsoft.com/enable/)
References for Universal Design

National Center for Accessible Media (www.wgbh.org/ncam)


The Trace Reseach & Development Center
(http://trace.wisc.edu/)


The CPB/WGBH National Center for Accessible Media (NCAM) is a research and development
facility that works to make media accessible to underserved populations such as disabled
persons, minority-language users, and people with low literacy skills.
An interdisciplinary research, development and resource center on technology and disability.
It is part of the Waisman Center and the Department of Industrial Engineering at the
University of Wisconsin - Madison.
GA Tech Center for Assistive Technology & Environmental
Access (CATEA) (http://www.catea.org/)

Where Arthur and Bill used to work. An established interdisciplinary research and design
center devoted to applications of technology to alleviate problems of human need, providing
service, research, and education under the auspices of a world class academic institution –
Georgia Tech.
Questions / Comments
Sender
Generation & Production
Receiver
Storage & Serving
Transmission
Presentation of Information
Graphic: William A. Curtis
CHI Atlanta | February 2003 | [email protected]