240 likes | 482 Views
Accessibility Testing Tools. Testing goals. Compliance with accessibility standards? Conformity to coding standards or best practices? Functional Accessibility? Compatibility within a given environment?. Types of testing tools. Site-wide compliance scanning and validation tools
E N D
Testing goals • Compliance with accessibility standards? • Conformity to coding standards or best practices? • Functional Accessibility? • Compatibility within a given environment?
Types of testing tools • Site-wide compliance scanning and validation tools • Single page scanning and validation tools • Single test point testing tools • Assistive technologies
Site-wide tools • Automated testing of all static HTML pages. • Some support application testing • Limited support testing of content other than HTML. (PDF)
Examples • IBM/Watchfire (Used by Texas HHS) • DequeWorldspace • Web King • HiSoft
Benefits • Good monitoring capabilities • Rapid results • Excellent support for site-wide accessibility compliance management
Limitations • Complex to set up and maintain • Limited test coverage • Many checkpoints require human interpretation and judgment • Can give a false sense of security • Expensive
Single Page/Document Scanning Tools • Automated scan of web pages and documents. • Can flag both automatic check failures and highlight areas for manual inspection
Examples • Wave • Functional Accessibility Evaluator (FAE) • DequeFireEyes
Benefits • Immediate feedback to developers and accessibility testing staff • Full coverage of accessibility checkpoints • Easy to deploy and use • Free!
Limitations • Slow • Requires expertise to understand the manual checkpoints • Requires user to understand how a particular tool evaluates a testpoint
Single Test Point Testing Tools • Tests individual accessibility features on a page by page basis
Examples • Accessibility Toolbar (IE) • Juicy Studios Accessibility Toolbar (FF) • Wave toolbar (FF) • Jim Thatcher’s Favelets (Any Browser) • Complex Table Toolbar (FF)
Benefits • Good identification of features and problems • Excellent source of screen shots for developers/contractors • Some support editing of source code • Free
Limitations • Some do not work well on framed pages • CSS or Table layout methods may hide problems • Slow
Assistive Technology • Testing with screen readers, magnifiers, keyboard, or dictation software
Examples • JAWS, NVDA, Window Eyes, VoiceOver • ZoomText, Magic • Dragon Dictate • Unplug the mouse
Benefits • Tests functional accessibility with specific technology • Approximates user experience • Identifies compatibility issues
Limitations • Tests functionality with specific technology • Not a substitute for usability testing by disabled users • Does not identify compliance issues. • Requires considerable expertise • Expensive
Conclusion • Compliance testing does not equal accessibility testing • The best tool will depend on the tester, the environment, and what is being tested • Wide variety of tools out there, build a big toolbox