Sat 29 Sep 2007
There are at least two web accessibility guidelines: Section 508 from the federal government and WCAG from the W3C .
What’s an quick, simple, cheap method for testing or validating web accessibility?
Their are a number of tools available that attempt to provide automated accessible testing:
- Firefox Plugins
- Fangs – a screen reader emulator
- Firefox Accessibility Extension – from uiuc.edu
- Validation services:
- webxact
- Cynthia Says – can select section 508, or WCAG 1 through 3
- FAE – Functional Accessibility Evaluator
- Testing
- VisCheck – simulation of web page experience for the color blind
These tools are a great place to start and by passing these tests your website will be usable by screen-readers, braille printers and other accessibility tools. That said, making an excellent site really cannot be automated. Improving accessibility includes things such as descriptive links, content that doesn’t require a user to visually scan a page, using the <abbr> tag, useful description of images, labels, allowing text to be resized (use em not px), etc. The W3C provides an excellent article entitled: How People with Disabilities use the Web.
Accessibility software:
- Kurzweil 3000 – “the comprehensive reading, writing and learning software solution for any struggling reader, including individuals with learning difficulties, such as dyslexia, attention deficit disorder or those who are English Language Learners”
- JAWS – Windows screen reader
- Dolphin Hal – Windows screen reader
- Orca – gnome’s visual assistive technology
- Sun’s Solaris 10 includes much built-in accessibility functionality, including a screen reader for gnome
- Apple’s Mac OS X contains tightly integrated accessibility features
Isaac Vetter – Webmaster