Web Site Accessibility: Too Difficult To Implement?

1
Web Site Accessibility Too Difficult To
Implement?

• Contents
• Implementation Challenges
• Beyond The Theory
• Current State Of UK HEI Web Sites
• The Problems Encountered
• Beyond The Accessible Page
• Issues
• Issues For General Discussion

• Brian Kelly
• UK Web Focus
• UKOLN
• B.Kelly_at_ukoln.ac.uk

2
Implementation Challenges

• In the real world we are faced with several
  implementation challenges
• Deficiencies in specs, tools, etc.
• Migration and support implications
• Addressing user needs resourcing implications

Implementation Challenges
External Issues
Publisher Issues
User Issues
3
The Real World Web

• In the real world Web we need to recognise
  several external factors
• Due to the rapid development of Web specs ("the
  Web year") the specs themselves may be flawed,
  ambiguous or over-ambitious
• Software has bugs (the cockup theory)
• Software vendors have their own agendas
  (conspiracy theory)
• Together with local factors
• Inertia / unwillingness to act as guinea pigs
• Licensing costs
• Support issues

Implementation Challenges
4
UK HEIs - A Case Study

• In Sept 2002 a survey of accessibility of 160 UK
  HEI entry points was carried out
• Used Bobby tool (to report on problems which
  could be spotted using an automated tool)
• How many WAI AA entry points were found?
• The survey found
• 4 entry points complied with WAI AA
• One was a JavaScripted site (so isn't accessible)
• The UK HEI Web management community is aware of
  importance of accessibility and wants to
  implement accessibility. What are the
  difficulties?

Implementation Challenges
See lthttp//www.ariadne.ac.uk/issue33/web-watch/gt
5
UK HEIs - A Case Study (2)

• An example of a AA-approved site is the
  University of Bristol

6
UK HEIs - A Case Study (3)

• Typical problems found
• Missing DOCTYPES
• Missing ALT attributes in IMG tags
• Use relative sizing and positioning ( values)
  rather than absolute (pixels)
• The first two problems could be fixed with little
  effort on a single page
• The third problem may conflict with usability
  criteria
• Let us now
• Look at the challenges in accessible Web sites
  (and not just pages)
• Consider the usability issues

Implementation Challenges
7
WAI Implementation Challenges

• Many University Web managers want to comply with
  WAI but have encountered implementation
  challenges
• Limitations of authoring tools
• Browser bugs (e.g. Netscape 4)
• Apparent conflicts between usability and
  accessibility
• Resource implications of deploying new tools,
  training, etc.
• The scope of large institutional Web sites
• Finding the funding

Implementation Challenges
8
WAI Implementation Challenges

• One Web manager commented that " I too have
  recently been struggling with just how rigorously
  the WAI guidelines should be implemented. I
  certainly aspire to comply as fully as I can with
  the WAI guidelines but "
• Some guidelines are too theoretical
• Will have a pragmatic approach
• Use tables for positioning
• Will not associate form controls for search boxes
• Not necessarily nest headers correctly

Implementation Challenges
9
Supporting People - Not WAI Compliance

• We should be addressing users' needs, and not
  simply striving for WAI compliance
• Is the 'universal design' mantra always valid?
• "Click here" considered bad practice as not
  everyone uses a mouse
• But what about the user with learning
  difficulties?
• Is there a need to design for specific concerns?
• Blind
• Colour-blind
• Physically impaired
• Learning difficulties

10
Alternatives To W3C's Vision

• The W3C's vision is for universal access based on
  open standards.
• Sound great, but
• Is this practical? (I'm using PowerPoint!)
• Should we rule out pragmatic solutions (our users
  will use Microsoft software, Flash PDF formats)
  if proprietary formats can be accessible is
  this a problem?
• Should WAI (indirectly) impose its views rather
  than leaving organisations to chose appropriate
  strategies?

11
Beyond The Web

• There is life beyond the Web
• Web applications may be inherently inaccessible
  or very costly to make accessible (e.g. 3D
  visualisation, mapping, fine art, etc.)
• "I have a Flash animation illustrating the effect
  of the HIV virus. How can I make this
  accessible? How can I fund this?"
• If a real world solution to a Web problem is
  provided, the user will be happy, even though the
  Web site is inaccessible

12
Accessibility Policies

• You may wish to have an institutional
  accessibility policy

All resources on the University Web site will
comply with WAI AA
Implementation Challenges

• But
• Is this practical
• All Web sites?
• What about MS Word / PowerPoint documents?
• How will compliance be audited?
• What about difficult areas (e.g. 3D maps)?
• What about people? What about usability?
• How will this be funded?
• Is this policy intended to be rigorously
  enforced, or does it define an aspiration?

13
Issues

• Some issues for discussion
• What limit should we place on making resources
  accessible?
• Does W3C WAI drive our accessibility policies or
  inform it?
• If the latter, what is done outside of the WAI?
• Is adopting WAI guidelines within a legal
  framework wise?