Creating Accessible Teaching and Support

Web pages can be designed so that they can be navigated and read by everyone regardless of disability, experience or the type of computer technology available and still be visually appealing.  Accessibility should be an integral part of the design philosophy of web developers with accessibility features incorporated in to all aspects of the design process. The W3C guidelines provide a useful starting point for ensuring accessibility.

Accessible web design is the practice of designing web pages so that they can be navigated and read by everyone regardless of disability, experience or the type of computer technology available. If the principles of accessible web design are not implemented when developing a website people with vision impairments for example will find it difficult or impossible to access web pages.

Manyearly accessible web sites were heavy on text and low on interest. Advances in web design tools, accessible design and assistivetechnology mean that there are now many interesting ways that the Webcan be designed to be interesting, engaging and accessible.  See for example the JK Rowlings website which melds graphically rich design, interactivity and accessibility.

Alternative "text only" sites are now less common as adherence to the W3C guidelines can ensure your regular website will meet the needs of all users.

The W3C guidelines explain how to make web content accessible to people with disabilities and to maximise the use of assistance technologies such as screen readers and wireless pointing devices.  The Web Accessibility Initiative   suggests the following tips as astrating point:

1. Images & animations - Use the alt attribute to describe the function of each visual.
2. Image maps - Use the client-side map and text for hotspots.
3. Multimedia - Provide captioning and transcripts of audio, and descriptions of video.
4. Hypertext links - Use text that makes sense when read out of context. For example, avoid "click here."
5. Page organization -  Use headings, lists, and consistent structure. Use CSS for layout and style where possible.
6. Graphs & charts - Summarize or use the longdesc attribute.
7. Scripts, applets, & plug-ins - Provide alternative content in case active features are inaccessible or unsupported.
8. Frames - Use the noframes element and meaningful titles.
9. Tables - Make line-by-line reading sensible. Summarize.
10. Check your work - Validate. Use tools, checklist, and guidelines at http://www.w3.org/TR/WCAG