Skip to main content

Verify overview

The Verify phase gives testers a faster way to confirm the accessibility of products.

With more accessibility built into design and development, a tester’s role matures from discovering missing accessibility to confirming its successful incorporation. Effort is reduced and specific requirements are more quickly verified.

Testers run tools to validate that all issues discoverable by automated testing have been resolved. They then complete a manual inspection and keyboard check of the product, before confirming everything is usable with a screen reader. As explained in the Launch Readiness phase, testers gather the testing results and prepare to record and report the results in industry standard formats.

Three verify steps

Note: These tests focus on version 2.1 of the Web Content Accessibility Guidelines (WCAG). Non-WCAG items on the IBM Accessibility Checklist will require additional verification beyond what is outlined in this section.

Need help?

Submit a github issue and we’ll help you find what you need.

Submit an issue