Testing Lifecycle Overview

Section 508 conformance testing is essential to ensure information and communication technology (ICT) is usable and accessible for people with disabilities and conforms to federal Section 508 Standards. Without testing, Section 508 defects may go unnoticed—leading to conformance issues, poor user experience, and potential legal risk. The testing lifecycle begins with planning and scoping, followed by testing using a test methodology and tools to identify defects. Following the review, remediation is performed and validated through retesting to ensure all issues have been adequately resolved. Ongoing monitoring and maintenance helps sustain Section 508 conformance as ICT evolves.

Testing should happen throughout the design and development process, not just before a product is released. For example, Section 508 testers or subject matter experts could provide feedback early on during design and prototyping. Development teams can also integrate accessibility testing into their regular build and deployment routines. In Agile or collaborative development environments, the roles of designer, developer, and tester are often shared across team members, or even performed by the same individual, making early and continuous accessibility testing an integral part of the development lifecycle. Regardless of how Section 508 is integrated, the testing process should always allow enough time to fix any issues before a product goes live. Below is a simple overview of the Section 508 testing lifecycle:

1. Plan and Scope Testing

   • Identify which ICT product(s) will be tested, such as a web page, web site, software, electronic document, or hardware.
   • Determine applicable Section 508 Standards, testing methodologies, and associated tools that will be used. Align with agency approved Section 508 conformance testing methodologies.
   • Scope which user paths, functions, or other product features will be included in the testing. At minimum, the testing scope should include public-facing, frequently used, or critical functions.
   • Select knowledgeable Section 508 testers—these may include federal employees, contractors, third-party accessibility testing experts, or users with disabilities.

2. Gather Testing Materials and Access

   • Identify all product components required for testing such as web pages, electronic documents, software applications, and hardware.
   • Ensure installation of or access to all product components including test environments.
   • Confirm testers have required login information, test data, or administrative credentials.
   • Gather any additional information needed from designers or developers to understand how to use the content within the scope of testing.

3. Conduct Section 508 Testing

   • Using the methodologies identified in Step 1, test the product.
   • Ensure comprehensive testing includes all applicable Section 508 Standards.
   • Ensure each defect is captured in an Accessibility Test Report.

4. Review Test Report

   • Prioritize defects for remediation based on severity, risk, or impact on users.
   • Assign who is responsible for remediation which may be a specific person, team, or vendor.
   • Set and document deadlines in a Remediation Plan. High priority defects should be remediated as soon as possible, but deadlines for remediation should preferably not exceed 1 year.
   • Use a mechanism to track defects, progress, expected remediation date, and actual remediation date.

5. Remediate Defects

   • Work with designers, developers, and content creators to remediate issues.
   • Continue to update the defect tracking mechanism to monitor remediation and outstanding defects.

6. Retest for Verification of Remediation

   • Knowledgeable Section 508 testers should:
   • Re-check fixes and confirm defects have been adequately addressed.
   • Ensure fixes did not introduce new issues.
   • Update the accessibility test report and tracking mechanisms with the new status for each Section 508 Standard, date of re-test, and any other product information that has changed.
   • Create an Accommodation or Alternate Means Plan for any defects that remain unresolved.
   
   Once all defects have been remediated, or remediated to the best of the team’s ability, there may be a need to develop an Accessibility Conformance Report (ACR) based on the test results. See the Accessibility Conformance Report (ACR) page for more information on how to create a machine readable ACR and when you may need one.

7. Ongoing Monitoring and Maintenance

   • Schedule periodic re-testing. At a minimum, Section 508 testing should be included in any updates or redesigns. Alternatively, Section 508 testing may be integrated into development processes.
   • Embed Section 508 conformance into future work and ensure it is included in design, procurement, development, and content processes.

Reviewed/Updated: July 2025