Blogs

July 12-14, 2001. Fourth Advance for Design Summit, Arizona. With Eugene Chen and Steve Krug (who presented for me, since I could not make the trip). See Role: Usability Specialist.

Presented at OCLC, March 12, 2001, with Kat Hagedorn and Chairra Fox, Argus Associates.

Tutorial presented at HFWeb conference, June 19, 2000, Austin, Texas.

Originally prepared for the Web '98 conferences (Boston, September 26, 1998 & San Francisco, June 25, 1998) and used a few times since. Portions of this presentation were also used as part of a panel at an AIP Cleveland meeting, May 15, 2001.

Short presentation that was part of the FedWeb '98 Seminar on Universal Access, July 7, 1998, Washington, DC.

Goal: People accessing Information and Services

User Interface Hurdles

Usability Viewpoint on Accessibility

• Accessibility one aspect of usability
• Understanding users, tasks
• Disabled only part of audience for accessibility
• Techniques to make it easy to use can also be used to make it accessible

Example: "The Online Disabled"

Some groups of users "behave disabled" online:

• Slow connections, browse without graphics
• No sound cards, not installed properly
• Older browsers, undetected features
• User settings, features turned off
• Poor input devices (WebTV)
• Poor output devices (PDAs)
• You, sitting in the audience right now

Usability Engineering for the Web

1. Walk a mile in my users' shoes
2. Take a ride on their shoulders
3. Embrace the Web
4. Do usability sweeps
5. Assume I will get it wrong the first time
6. Sleep with the technology but do not marry it

Webmaster Needs

1. Easier to do special configurations
2. User testing with "online disabled"
3. Accessibility is a feature, not a bug
4. Checklists, guidelines (tools)
5. Still iterative design
6. Accessibility tradeoffs of each technology