Accessibility Testing Requirements – Understandable – Readable
In the series of reviews I’m looking at WCAG level A / AA (Web Content Accessibility Guidelines) requirements from testing perspective.
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.
Understandable – Readable
Make text content readable and understandable.
Tools can be used for content parsing and checking language settings.
Language of Page
The language of the page is identified using the HTML lang attribute.
Human Testing – Brief
Tool-Assisted Checking – Full
Tool may check for a presence of lang attribute, but unable to judge whether the appropriate language is set.
Testers should also verify a corresponding link to the page – the link should have page language specifier as well.
Language of Parts
The language of page content that is in a different language is identified using the lang attribute.
Human Testing – Brief
Tool-Assisted Checking – Full
Tool may check for a presence of lang attribute, but unable to judge whether the appropriate language is set.