Integrating digital accessibility into test planning from the very beginning is crucial for efficiency and effectiveness. Rather than treating digital accessibility as a final separate test level or phase, it should be a consideration throughout the SDLC. While Chapter 3 outlines the high-level testing strategy and techniques, this section focuses on creating the specific, actionable test plan for a given project or release.
A number of factors need to be considered when planning digital accessibility testing. These include the following:
- Identifying digital accessibility requirements
- Defining the test scope and the test objectives
- Determining the test approach
- Planning resources and test environments
- Defining roles and responsibilities
- Test scheduling and integration
Identifying digital accessibility requirements
A digital accessibility requirement is a requirement regarding the digital accessibility of a component or system. It provides the basis for evaluating whether a digital product meets the needs of users with disabilities. Digital accessibility requirements can originate from several sources:
- Project requirements. Requirements stated in product documentation, acceptance criteria, user stories, design-system rules, or organizational policy (e.g., “As a keyboard-only user, I must be able to navigate the checkout form without getting stuck”).
- External requirements. Requirements imposed or referenced by applicable legislation, regulation, standards, procurement rules, or contracts (e.g., “The application must conform to WCAG 2.2 Level AA”).
- Derived technical requirements. Requirements derived from an applicable standard, platform accessibility model, design system, or supported assistive-technology interaction even when the implementation detail is not repeated in a user story. Derived requirements should be traceable to their source rather than treated as undocumented assumptions.
Defining the test scope and the test objectives
- Conformance goals. Clearly state the target digital accessibility standard (e.g., WCAG) and the desired conformance level (A, AA, AAA).
- Jurisdictional requirements. Identify any specific legal or regulatory requirements (e.g., Section 508 in the U.S., EN 301 549 in Europe).
- In-scope/Out-of-scope. Define which parts of the application, platform, or user journeys will be tested. This may involve prioritizing critical user paths, such as registration and core functionality.
Determining the test approach
- Automated testing: Integrate appropriate test automation tools into development and CI/CD workflows to identify rule-checkable issues early, while recognizing that automated results do not cover all accessibility requirements or user barriers.
- Manual testing: Plan for test activities that require human judgment, such as keyboard navigation, and logical content flow.
- Testing using assistive technology: Planning for testing with specific screen readers that are integrated into operating systems or external ones, screen magnifiers, or voice control software
- End-user testing: Involve people with disabilities in test activities to gain real-world feedback on user experience and digital accessibility.
Planning resources and test environments
- Team skills: Assess the team's knowledge of digital accessibility and plan for training, if needed. Awareness of disabilities is important.
- Tools and software: Allocate budget and time for manual testing, test automation tools, assistive technologies, representative devices/environments, and any external accessibility expertise or participant involvement required by the test approach.
- Test environment: Verify the test environment is configured to support digital accessibility testing (e.g., it is accessible for assistive technologies, and test automation).
Defining roles and responsibilities
Identifying who will perform which parts of the testing and remediation process to facilitate comprehensive coverage. Examples include:
- Tester: To execute routine automated and manual digital accessibility tests, report defects, and verify fixes (i.e., this is the core role executing the test plan).
- Developer: To consult on technical feasibility and implement accessible code and structural fixes.
- UX/UI designer: To verify that visual and interactive elements (e.g., color contrast, focus states) meet digital accessibility standards prior to development.
- Digital accessibility expert/consultant: To act as a Subject Matter Expert (SME), resolve complex WCAG interpretations, guide the team, and conduct formal compliance audits.
- Product owner / business analyst: To define explicit digital accessibility requirements, user stories, and acceptance criteria.
- Participant with a disability / end user: To provide first-hand feedback on barriers encountered during representative tasks and, when applicable, the use of assistive technologies. This role is distinct from the accessibility specialist or consultant role.
Scheduling and integration
- Entry and exit criteria: Define what must be ready before planned test activities begin and what evidence is required for completion. Exit criteria can include required coverage completed, agreed high-risk findings addressed or formally accepted, retesting completed, and required reports produced. Avoid relying on a universal percentage of defects resolved.
- Milestones: Integrate digital accessibility testing activities into project sprints and project milestones, from early design reviews through pre-production phases and testing in production.