Accessibility Testing Requirements – Review
In the series of reviews I’m looking at WCAG level A / AA (Web Content Accessibility Guidelines) requirements from testing perspective.
Scope
(The following table of contents is taken from WCAG site and redirects to its contents)
- 1 Perceivable
- 1.1 Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
- 1.2 Provide alternatives for time-based media.
- 1.3 Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- 1.4 Make it easier for users to see and hear content including separating foreground from background.
- 2 Operable
- 3 Understandable
- 4 Robust
Approach
- Review testability of the requirements
- Review applicability of checking tools
- Assess tool / skill balance
- Define special testing knowledge or skill requirements
- Review some of tools per class
- Develop testing heuristics
- Mindmap the knowledge
Common Definitions
Human Testing
- Brief – “You know as you see it” – quick scanning is sufficient to check and make a judgment. This does not include effort of logging defects.
- Detailed – Either interaction (execution of tests) with the functionality is necessary or detailed review/analysis must be done in order to verify a requirement.
Tool-Assisted Checking
- Not Available – Tools cannot help in checking for the specified requirement or they help very insignificantly.
- Partial – Tools provide significant help in checking for the specified requirement, either by saving time in parsing content source or through visualization. Human does the verification and judgment.
- Full – Tools capable of locating and verifying the specified requirement. Brief review of checking results is sufficient to make a judgment.