Skip to secondary navigation Skip to main content

Play 7: Integrate Accessibility Needs into Requirements and Design Processes

As products are developed for the benefit and use of the American people, federal employees, and other groups that include people with disabilities, agencies should conduct user research with the people that will interact with the product or solution being developed or implemented. We must begin technology projects by identifying the needs of people with disabilities who use and support the technology, and account for the ways the technology will fit into their lives. We must understand their preferences and expectations for using government technology to ensure it works for all users, not just some users. Creating user personas, testing with people with disabilities, and incorporating user stories can be used to integrate user needs into the design process. Adopting universal design as a core development principle is another useful method for integrating accessibility needs. Universal design is a concept in which products and environments are designed to be usable by all people, to the greatest extent possible, without the need for adaptation or specialized design. These perspectives should not only inform technical and design decisions, but should be considered throughout the IT investment, acquisition, development, and deployment phases.

Key Questions

  • At project inception, what steps do you take to determine whether a planned digital service or technology solution will support inclusive access?
  • What steps do you take to validate the accessibility of design proposals with potential disabled users?
  • How do you incorporate accessibility requirements into acquisition and development activities?

Checklist

Prior to beginning a technology project, work with usability professionals and requirements analysts to:

Table 1: Play 7 Checklist
Item Actions
Ensure developers, designers, and business analysts understand their responsibilities under Section 508 and know how to incorporate accessibility as a core requirement for all IT projects, as laid out in the design and development roles and responsibilities.
Encourage collaboration between developers, usability professionals, and business analysts.
Use a range of research methods to determine the goals, needs, preferences, and expectations of potential users with disabilities.
  • Include accessibility conformance requirements in the planning of ICT prototypes and pilots.
  • Create example User Stories that are used throughout the design process.
  • Establish example personas as a method for identifying the varying needs and expectations of different user types.
Identify what types of interactions could be difficult for users with disabilities, including individuals who may have:
  • Low or no vision
  • Low or no hearing
  • Difficulties with speech
  • Physical limitations including a lack of dexterity
  • Cognitive disabilities such as dyslexia, processing difficulties, reading challenges, or other cognitive conditions affecting learning or comprehension
Identify approaches that could lower or remove barriers to access.
  • The device(s) used to access agency content
  • The operating system used to run the device
  • The electronic content provided through or produced by the solution
  • The software used to view, interact, and navigate the electronic content
  • The training and documentation provided on how to configure and use the product
Include Section 508 and any additional accessibility requirements into decisions regarding what technology approach will best meet agency needs.
Note—this is before the acquisition or development phase.
When possible, create a proof-of-concept or prototype to validate potential technology approaches with representative users with disabilities. Utilize test findings to refine approaches and design alternatives. Refine and retest with users with disabilities to verify improvements.
Finalize accessibility requirements for the chosen solution, including all applicable Section 508 requirements and additional requirements necessary to address the needs of users with disabilities.
Incorporate the accessibility requirements into market research and acquisition efforts—see Play 8.
Incorporate accessibility requirements into development efforts—see Play 9.

Key Performance Indicators (KPI)

This section outlines Key Performance Indicators (KPIs) to track and measure accessibility testing, remediation, and overall Section 508 conformance across web, intranet, and enterprise ICT solutions.

Generic KPI: In FY2X, conduct user testing with people with disabilities on XX% of new user content before publishing and create a method for tracking this involvement.

Generic KPI: By QX FY2X, finalize and distribute a formal organization-wide ICT accessibility policy that includes all relevant OMB memos and Section 508 statutory requirements.

Reviewed/Updated: September 2025

Section508.gov

An official website of the General Services Administration

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