Slide7-9 Testing Best Practice

Testing rules provide step by step instructions on how to test accessibility standards, and document issues in a common format.Accessibility is the goal – inclusion is the practice
Sharron Rush, award winning co-founder and Executive Director of Knowbility
Part 1: Test Plan
Assign specific roles to team members and detail their responsibilities. Include communication channels and protocols to ensure smooth collaboration.
Define the team testing goals (functionality, performance, usability, security, and compatibility).
Define the extent and boundaries of testing, specifying what will be tested (in scope) and what will not (out of scope).
Describe the hardware, software, and network configurations needed for testing. Specify if testing will be done in a local or remote environment.
Identify any dependencies in the testing process, such as required modules or services. Include plans for mock modules if development is not complete.
List the documentation and artifacts to be produced during the testing process (test cases, reports). Specify format, frequency, and distribution of deliverables.
Outline potential risks (missing deliverables, resource changes) and mitigation strategies. Use dependency mapping to anticipate adjustments.
Define the testing timeline, including milestones for manual and/or automated testing phases. Highlight deadlines for each testing activity.
Rules for accessibility conformance testing (ACT) describe how to test conformance of accessibility standards. ACT Rules inform accessibility testers on how to evaluate in a consistent method with other accessibility testers.
W3C/WAI: ACT Rules Implementation in Test Tools and Methodologies
W3C/WAI: ACT Rules Implementation in Test Tools and Methodologies
Part 2: Test Documentation
The date of producing the test results.
Name and contact of tester.
The web page name and URL.
The operating system (Windows version, iOS device/version).
Browsers and web applications used.
Screen reader, braille display, and other devices used.
Reviewer summary of accessibility issues and usability severity.
Document each issue according to the team accessibility template.
- Issue Id
- Issue severity
- WCAG Criteria Number
- WCAG Type (Perceivability, Operability, Understandability, Robust)
- Issue Description
- WCAG Remediation Technique
- Background Resources.
Consolidate reviewers test results.
Establish the reporting template that your team will be using. Examples:
Part 3: Test Exercises
Some tools for getting started with web usability testing.
Using assistive technology and only a keyboard, perform accessibility testing, for page content structure, on the following sample pages.
Using assistive technology and only a keyboard, book a domestic return flight trip with Air Canada and Porter Airline. Document each usability issue and the associated WCAG criteria failure.
Resources