• Share on Facebook
  • Share on Facebook
  • Share on Linkedin
  • Share by email
  • Share on Facebook
  • Share on Facebook
  • Share on Linkedin
  • Share by email

The Disability Discrimination Act of 1995 applies to websites, but this need not be the sole motivation for reviewing access on a site, writes Hans de Kretser.
As well as being a requirement from funders such as the Arts Councils, there are also legal, ethical and business reasons why making a website accessible is essential. Accessibility is closely linked with usability, which has been proven to increase profitability for many commercial websites. Despite this, with a few notable exceptions, most arts websites are simply shutting the door to some of their online visitors.

When tackling issues of website accessibility, visual impairment issues tend to be the first to arise. Concerns might include a reliance on colour to convey information, fonts that can?t be re-sized by a browser and complicated page layouts that cannot be interpreted by text-to-speech programmes. However, the issue of web accessibility goes wider than this. People with motoral disabilities may have difficulties using complicated navigation, having to rely on the keyboard instead of a mouse to move around the website. Those with cognitive or neurological disabilities may have problems with inconsistent navigation, verbose copy, lack of illustrative non-text materials and overly complicated presentations; and people with hearing loss may suffer if a site relies on audio and video soundtracks to get information across without an accompanying transcript. As voice activation becomes more commonplace, it will also be necessary to consider people with speech disabilities.

By addressing these issues it is possible to improve a site for all. For example, many people find using keyboard stokes quicker than using a mouse: simplified copy helps those who scan-read. Making a website accessible doesn?t mean compromising on design or spending a fortune to re-build. Understanding the issues is the first step in developing a creative approach to finding cost effective solutions. This benefits everyone and helps to create a website that an organisation can justifiably take pride in.

10 step learning curve:

1. Imagine how different groups of people experience your website. To see an interactive demonstration, visit http://www.drc-gb.org/newsroom/website.asp.
2. Open your website in a browser such as Internet Explorer. In the View menu try to make the text size larger ? the design of some websites prevents this function from working.
3. Download a 30-day free trial of a text-to-speech reader at http://www-3.ibm.com/able/solution_offerings/hpr.html. Use it on your website. Does it make sense?
4. Check your website with real users. I worked for a company where a colleague with visual impairment could test new web projects with me.
5. Look at Bobby for a quick audit of accessibility issues on your website
http://bobby.watchfire.com/bobby/html/en/index.jsp
6. Find comprehensive guidelines at the Web Accessibility Initiative (http://www.w3.org/wai/) and the RNIB (http://www.rnib.org.uk/digital/hints.htm)
7. Look at what other sites do ? here are three to get you started:
The National Gallery: http://www.nationalgallery.org.uk
The Hampstead Theatre: http://www.hampsteadtheatre.com/
WorldWideDanceUK: http://www.worldwidedanceuk.com
8. Check that your web developers or designers understand the issues and that you have reached consensus on the priorities.
9. Work toward the RNIB?s ?See It Right? logo scheme, which lets people know that you?ve considered their issues.
10. Review your site regularly: websites evolve, technology changes, new access issues arise.

Hans de Kretser is Head of Digital Marketing for M + H Communications Ltd, e: hans@mandh.co.uk

Quick tips
? Use Alternative Text Tags (alt tags) that describe images to someone using text only browsers
? Forms and navigation should work using the tab and return keys on your keyboard to move from field to field or hyperlinks
? Indicate if a link opens a pop up window or programme to display content.
? Use Style Sheets to separate style from content and allow users to substitute their own if they prefer
? Use Flash with care as it can be very inaccessible