Testing Accessibility

Judy Brewer
jbrewer@w3.org

Web Accessibility Initiative Domain Lead
World Wide Web Consortium

Overview

Accessibility-supporting functionality
- is integrated in most Open Web Platform (OWP) specifications
Testing accessibility often means
- different approaches or additional types of tests
- the need to bring additional expertise to the table
Accessibility testing requirements
- may get overlooked
In some settings, it's a requirement to get accessibility right

Accessibility may be required
- laws, regulations, policy directives
- business priorities
Gaps in accessibility support may shut out a market

For instance...
- (on images) alt; (for tables) summary; (for forms) required
- (example of an off-site assessment of html5 accessibility feature support; not up-to-date)
Also embedded in HTML5: WAI-ARIA features
- ~60 roles, ~35 states and properties that variously apply to roles
- ~700 tests done, another ~300 more tests expected
- some additional features needing testing: ARIA UI Implementation such as keyboard focus management; ARIA property change events
Extensions
- (expected) longdesc, others

Testing requirements, that now include initial & updated inputs on accessibility requirements
- includes need for platform-specific AAPI testing, for instance
  - Microsoft Active Accessibility and/with/or iAccessible2
  - Microsoft UI Automation
  - Linux Accessibility Toolkit
  - Assistive Technology Service Provider Interface
  - Mac OS X Accessibility Protocol
Benefit of AAPIs is that mainstream user agent doesn't require knowledge of specific assistive technology
- only to allow for programmatic knowledge of the general use case
AAPI inspection tool could be used manually
Automated AAPI inspection tools (per AAPI) could help automate test runs

Protocols and Formats Working Group (PFWG) Test Harness
- was necessary to develop for WAI-ARIA Candidate Recommendation
- feature set is usable and adaptable for other groups
Test cases
- may need to align terminology with Philippe's assertions
Test runs
- data currently visible only to testers
Test reports
- sample results showing

Accessibility support database
- under development by WAI-ACT for WCAG 2; some relevant info
Authoring Tool Accessibility Guidelines (ATAG) testing
- may have relevant info
IndieUI necessary for accessible functionality for mobile
- developing testing strategy; majority automatable; most expressable through Web IDL
Integrated testing approach beneficial
- useful to confirm accessibility testing angle for each, and plan for resources
- consult with accessibility experts knowledgeable about AAPIs