10. ®
Copyright 2008 Adobe Systems Incorporated. All Rights Reserved. Adobe Con dential.
Tuesday, February 10, 2009
11. ®
http://flickr.com/photos/joebeone/2085528370/
Copyright 2008 Adobe Systems Incorporated. All Rights Reserved. Adobe Con dential.
Tuesday, February 10, 2009
12. ®
Copyright 2008 Adobe Systems Incorporated. All Rights Reserved. Adobe Con dential.
Tuesday, February 10, 2009
13. ®
Copyright 2008 Adobe Systems Incorporated. All Rights Reserved. Adobe Con dential.
Tuesday, February 10, 2009
19. Visual (including blind, low vision,
and color blind)
Spectrum of Disability
Tuesday, February 10, 2009
20. Visual (including blind, low vision,
and color blind)
Hearing
Spectrum of Disability
Tuesday, February 10, 2009
21. Visual (including blind, low vision,
and color blind)
Hearing
Motor/Physical
Spectrum of Disability
Tuesday, February 10, 2009
22. Visual (including blind, low vision,
and color blind)
Hearing
Motor/Physical
Speech
Spectrum of Disability
Tuesday, February 10, 2009
23. Visual (including blind, low vision,
and color blind)
Hearing
Motor/Physical
Speech
Cognitive/Learning
Spectrum of Disability
Tuesday, February 10, 2009
24. “JavaScript can’t be
used if you want an
accessible solution.”
Accessibility Myths
Tuesday, February 10, 2009
25. Generally, if we make
it easy to use for
people with
disabilities, we make
it easier to use for
everyone.
Universal Design
Tuesday, February 10, 2009
26. Old school techniques:
•accesskeys
•tabindex
•place-holder characters in
text boxes
•text-only versions
•use onkeypress with
onclick
Outdated Methods
Tuesday, February 10, 2009
27. New things that people are
doing that we also shouldn’t
do:
•putting content in CSS/
background images
•focusing entirely on
JavaScript on/o
Outdated Methods
Tuesday, February 10, 2009
40. •Design Stage: test for colour contrast,
general layout
Accessibility Testing
Tuesday, February 10, 2009
41. •Design Stage: test for colour contrast,
general layout
•Functional Testing: all functionality must
work with a keyboard and do be easy to
use; may do some testing with assistive
technology for technical compatability
Accessibility Testing
Tuesday, February 10, 2009
43. •Demo Testing: all alt text must be
accurate appropriate; Test with screen
reader emulators; Turn o CSS.
Accessibility Testing
Tuesday, February 10, 2009
44. •Demo Testing: all alt text must be
accurate appropriate; Test with screen
reader emulators; Turn o CSS.
•Final Testing: test with real people with
disabilities with varied needs, including
assistive technology (ease of use)
Accessibility Testing
Tuesday, February 10, 2009
58. “Which screen reader should
we buy for our testing lab?”
Testing Tips
Tuesday, February 10, 2009
59. Use the resources you have
on campus, in your district,
or from local associations for
people with disabilities.
Testing Tips
Tuesday, February 10, 2009
Discuss tester that was having trouble with this particular task - “Find out the contact number for the department of X” after three minutes of trying to say the words “contact us” differently, with different inflection, the tester stopped, and asked his father for a drink of water. He looked at me and said he was sorry, that he thought he was getting tired, and that his voice recognition software wasn’t tuned into his voice as his throat was dry, and we’d been testing for a while. He was blaming himself. It was something to do with him, not the web site.
The real reason the voice recognition software wouldn’t work? The alt text was wrong, so the VR didn’t select that link.