Skip to secondary navigation Skip to main content

Integrating Section 508 Requirements into Each Agile Sprint

For federal agencies using Agile development methods, Section 508 standards must be integrated continuously across the product backlog, sprint cycles, and releases—not treated as a separate or final step. Proactive integration of information and communication technology (ICT) accessibility in the product lifecycle helps manage costs, improves usability, ensures compliance, and strengthens team accountability. Conversely, addressing ICT accessibility issues late in the development process can be more disruptive and cause expensive rework.

To ensure each Agile sprint integrates ICT accessibility:

  • Use Personas of People with Disabilities (PWD) in Backlog Refinement and User Story Development: When writing or refining user stories, include personas of users with various disabilities such as screen-reader users, low-vision users, users without hearing, keyboard-only users, and users with cognitive disabilities. These personas help the team anticipate specific accessibility needs, design considerations, and test points. Personas should also inform backlog prioritization and acceptance criteria, not just story creation.
  • Include Section 508 Conformance in both the Definition of Ready (DoR) and the Definition of Done (DoD): The Definition of Ready is the team-defined list of criteria that a product backlog item or user story must meet before it is accepted into a sprint. Accessibility requirements should be explicit in acceptance criteria and validated before a story is considered ready for development. The team defines the Definition of Done as their collective understanding of what constitutes a completed user story. For user interface and feature-focused stories, the DoD should encompass both functional requirements and Section 508 accessibility standards. This includes ensuring keyboard-only functionality, adherence to sufficient color contrast ratios, and a valid and appropriate name, role, state, and value for all user controls.
  • Integrate accessibility testing continuously through test-driven or behavior-driven approaches: As part of development, break down ICT accessibility requirements into testable units. Developers and testers collaboratively implement automated tests and conduct manual testing as part of the development workflow, ideally before or alongside feature implementation. If issues are found, a remediation loop ensures fixes are incorporated before the sprint ends.
  • Embed accessibility expertise within the team and involve Subject Matter Experts (SMEs): Ensure that team members have or acquire accessibility expertise and use accessibility SMEs to provide guidance, pairing, and coaching rather than acting solely as reviewers. Include ICT accessibility SMEs, designers, testers, and PWDs—through usability or assistive technology testing—in design and review cycles, especially at sprint reviews and demonstrations.

Integrating ICT Accessibility in Agile Sprints

Below is a workflow to help ensure that the team iteratively integrates accessibility and Section 508 conformance validation across Agile events.

  • Backlog Refinement
  • Sprint Planning
    • Select stories that meet the Definition of Ready, including accessibility criteria.
    • Confirm the accessibility testing approach.
  • During Sprint (Development and Testing)
    • Implement features incrementally.
    • Perform continuous accessibility testing (automated and manual).
    • Address defects as they are identified.
    • Verify that acceptance criteria, including accessibility requirements, are met and that no critical accessibility defects remain.
  • Sprint Review
    • Demonstrate working, accessible functionality.
    • Validate accessibility as part of acceptance.
  • Retrospective
    • Identify accessibility gaps and process improvements.

Include Section 508 Conformance in Definition of Done

Below are example clauses you may include in your Definition of Done for user stories involving user interface or feature changes. Adapt this list depending on your agency's standards, technology stack, and type of ICT product.

Table 1. Examples of Definition of Done (DoD) ICT Accessibility Clauses
DoD ICT Accessibility Clause Description
Section 508 criteria met All user interface features comply with applicable Section 508 standards.
Color contrast verified Text and images of text meet minimum contrast ratios.
Keyboard navigation and focus order tested All interactive elements can be accessed and activated using only a keyboard; tab order is logical and focus is visible.
Screen reader and assistive technology compatibility tested The user interface is tested using the screen reader(s) and assistive technologies used by target users or required by agency standards.
Alternative text sufficient Images have sufficient alternative text.
Form fields are appropriately labeled Forms have appropriate visible labels and programmatic accessible names and descriptions.
Error messages are accessible When validation errors occur, the feature provides Section 508-conformant messaging, moves focus to the error, and includes instructions to fix it.
Content is responsive User interface remains usable at up to 200% zoom; no loss of functionality or content.
Section 508 testing completed Passes automated Section 508 conformance tests, manual checks are complete, and Section 508 defects are documented.
Accessibility requirements validated The feature or design meets all applicable Section 508 standards.
Accessibility acceptance criteria met All accessibility-related acceptance criteria defined in the user story have been fully implemented and verified through testing.
Automated accessibility tests included in CI/CD pipeline Automated accessibility tests are integrated into the CI/CD pipeline and run with each build to detect regressions and ensure ongoing conformance.
No critical accessibility defects No open defects remain that would prevent users with disabilities from accessing or using core functionality; any remaining issues are documented and do not block release.

Testing and Remediation Loop Within Sprint Cycles

To embed unit testing and remediation into each sprint, complete the following steps:

  1. Sprint Planning and Story Creation

    • Write user stories that include acceptance criteria incorporating personas of people with disabilities (PWDs) and ICT accessibility requirements.
    • Define the Definition of Done (DoD) for each story, including applicable Section 508 standards.

  2. Development Phase

    • Build features incrementally while incorporating accessibility requirements throughout development.
    • Develop unit, component, and integration tests—automated where possible—to validate accessibility requirements such as sufficient color contrast, semantic structure, correct ARIA usage, and keyboard operability.
    • Use code linters, accessibility checkers, and other appropriate tools to support accessible development.
    • Integrate automated accessibility testing into the CI/CD pipeline to run with each build and detect regressions.
    • Perform manual accessibility testing for requirements not fully covered by automation, including keyboard navigation, focus order, meaningful alternative text, accurate labeling, heading structure, and use of color.
    • Remediate accessibility defects as they are identified and retest fixes within the same sprint.

  3. Remediation Loop

    • Treat accessibility defects with the same priority as functional defects.
    • Remediate identified accessibility issues within the sprint.
    • Retest to validate that fixes are effective and do not introduce new defects.

  4. Review and Demonstration

    • Demonstrate completed features, including functionality that supports Section 508 conformance.
    • Include a Section 508 subject matter expert (SME) in the review process to provide feedback and identify potential issues.

  5. Sprint Close and Retrospective

    • Document Section 508 and ICT accessibility challenges, lessons learned, and successful practices.
    • Update the Definition of Done, accessibility tools, testing approaches, and personas as needed to improve future sprints.
Reviewed/Updated: June 2026

Section508.gov

An official website of the General Services Administration

Looking for U.S. government information and services?
Visit USA.gov