Accessibility
Derek Bridge
Department of Computer Science,
University College Cork
Accessibility
Aims:
- to understand universal design (design for all)
- to know what assistive technologies are available
- to appreciate some of the techniques that make web pages more accessible
Who is everyone
?
- People with visual,
auditory, physical, speech, cognitive, and neurological disabilities
- People with temporary 'disabilities'
- People of different ages
- People with different first languages
- People using different software (web browser, OS)
- People using different screens (resolution, size, colour) (see
http://www.thecounter.com/)
- People running on platforms with different I/O modalities
- People working in different environmental conditions
- ...
Assistive technologies for visual impairments
- Blindness
- screen readers, braille displays, text-based browsers, voice browsers
- Low vision (tunnel vision, central field loss, clouded vision, etc.)
- extra-large monitors, modified fonts & colours, screen magnifiers
- Colour blindness
- reader stylesheets
Assistive technologies for auditory impairments
- Deafness
- rely on captions and images
- Hard of hearing
- amplifiers, also benefit from captions and images
Assistive technologies for mobility impairments
- No use of hands
- specialised keyboards, keypads & switches, virtual keyboards,
specialised pointing devices (e.g. hand and mouth wands),
face and eye tracking devices, voice recognition
- Problems with fine motor control
- Similar technologies
Assistive technologies for cognitive impairments
- Visual and auditory perception, e.g. dyslexia, dyscalculia
- may rely on using multiple modalities at the same time
- Attention deficit disorder
- may need to switch off animations
- Intellectual disabilities, e.g. Down syndrom
- may rely more on graphics
Assistive technologies for more cognitive impairments
- Memory impairments
- may need consistency in the site
- Mental health disabilities
- may need to switch off animations
- Seizure disorders
- may need to switch off animations, blinking text or audio at certain frequencies
Web accessibility: reasons to care
- The legal argument
- There is national and international law
- The business argument
- Directly and indirectly, it may bring more customers
- The moral argument
- Simply, it's the right thing to do
The Web Accessibility Initiative (WAI)
-
In 1997, the W3C launched the WAI to help make the Web accessible to
people with disabilities
- The WAI publishes the Web Content Accessibility Guidelines (WCAG)
- WCAG 1.0 was approved in May 1999: stable
- WCAG 2.0 is being developed (for 2007?)
Logos from the WAI
Text equivalents to images
Relative versus absolute units of length
Use the right kind of markup
- Do not use presentational markup in place of structural markup
- E.g.
- Do not use structural markup in the hope of a certain presentational effect
- E.g.
- good: using
table
s for tables of data
- bad: using
table
s for layout
- good: using
ol, ul, li
for lists
- bad: using
ol, ul, li
just because (by default) they indent the text
- Class exercise: Who benefits?
Use colour intelligently
- Ensure proper contrast between foreground and background colours
- Avoid certain combinations
- Ensure information is not conveyed through colour alone
- Class exercise: Who benefits?
Consistency
- Use external stylesheets
- Use a consistent navigation scheme
- permanent navigation on each page
- same way of presenting local navigation on each page
- Class exercise: Who benefits?
Facilitate navigation around a page
Use the focus state for links
- We often highlight a link when the mouse is over it:
a:hover {background-color: rgb(100%, 70%, 70%);}
- Do the same when the link has focus:
a:focus {background-color: rgb(100%, 70%, 70%);}
- (And ensure a logical and useful tab order)
- Class exercise: Who benefits?
Think about your link text
Want to read more?
There are numerous other techniques (e.g. how to markup tables so that
they make sense when 'linearised').