Web accessibility and policy

1
Web accessibility and policy

• Dr Neil Witt

2
Some myths about web accessibility

• An accessible web page is dull, boring text
• A text based version of the site is all you need
  to provide
• Accessible web authoring is expensive and
  time-consuming
• Web accessibility is too difficult for the
  average web designer

3
Some myths about web accessibility

• People with a disability don't use the web
• Web accessibility only helps people with
  disabilities
• Assistive technology can solve all accessibility
  problems
• Users should view a site the way the designer
  intended

4
Myths about web accessibility

• Accessibility issues can be solved using software
• Organisation X has THE answer
• Nowadays everyone has Internet Explorer
• If I use this logo my site is accessible

5
Demystifying some myths

• Is a text based version the solution?
• Colours, fonts, and margins can be specified
  using style sheets
• Users who prefer, or require, their own styles
  can view the page in a manner suited for them
• Video, sound, images, and Java applets can all
  have alternative content provided to those who
  are unable or unwilling to experience these
  features.

6
Demystifying some myths

• Is a text based version the solution?
• Authors can use multimedia nature without
  sacrificing accessibility.
• One way of alienating your users
• Ask the user!

7
Demystifying some myths

• My logo means Im accessible

8
Beware the logo

• Diagnostic software is a starting point
• Automatic testing does not provide a
  comprehensive solution
• Dont expect a technological solution for a
  social issue
• Diagnostic and evaluation tools and their
  associated icons are perceived to represent an
  achievable standard towards web accessibility.

9
Beware the logo

• The tools are able to flag areas for concern BUT
  they cannot ensure that these are acted on
  appropriately or that all WAI Priority
  checkpoints are complied with.
• Accessibility is a business consultants dont
  always have THE answer, just possible solutions

10
Beware the logo

• Developers must comprehend that the evaluation
  process is based on an interpretation of the WAI
  checkpoints developed by a particular software
  company
• These evaluations must then be acted upon
• in accordance with the developers own
  understanding of the checkpoints
• with some appreciation of how their remedial
  actions are likely to impact on a user with a
  disability

11
The logo and the institution

• Decide on a level of compliance that is
  achievable
• All stakeholders to sign up to the accessibility
  policy
• Strive towards rather than an absolute
  statement
• Understand relevant legislation
• Education and training is vital

12
Implementing the policy

• Decide on level
• Audit
• Implement
• Embed
• Evaluate
• Review