Play 9: Integrate Accessibility Needs into Development Processes

Regardless of whether you use contractors or agency staff to develop digital services and technology, agencies must satisfy Section 508 requirements. Whether using waterfall, agile, or another development approach, achievement of Section 508 conformance is dependent upon your ability to incorporate accessibility needs from the very beginning of the development effort (conceptualization and planning) and through design, development, testing, deployment, continuous enhancements, and maintenance activities. Failure to consider Section 508 compliance throughout the development lifecycle will likely relegate Section 508 conformance considerations to the end of the project, when it is most costly to fix accessibility problems.

Key Questions

How does your agency incorporate Section 508 requirements into your development processes (lifecycles) used to design, develop, deploy, and maintain digital services and technology solutions?
When using agile processes, how do you ensure Section 508 conformance is addressed in each development iteration?
How do you train and equip developers to ensure Section 508 conformance?

Checklists

Table 1: Play 9 Basic Checklist—General Preparation
Item	Actions
	Ensure developers and designers understand their responsibilities under Section 508, and know how to incorporate accessibility as a core requirement for all ICT projects.
	Provide developers with the training and guidance needed to produce accessible websites and software.
	Encourage collaboration between developers, usability professionals, and business analysts.
	Address accessibility needs in project planning: Consider accessibility needs when making investment and enterprise architecture decisions Determine if development platforms, tools, hosting environments, and electronic content viewers could potentially create accessibility barriers for disabled users Allocate funding to perform accessibility assurance activities Allocate time in your project schedule to allow for accessibility and usability planning, design, testing, and remediation
	Address accessibility needs during requirements gathering and design (see Play 8 for more information): Conduct user-centered design activities to identify the needs of users with disabilities (see Play 7) Identify applicable Section 508 standards for solution features and electronic content Factor accessibility needs into solution design and alternatives analyses Address the needs of users with disabilities and applicable Section 508 standards in initial design, pilot, and proof of concept efforts Address pre-existing accessibility issues when prioritizing technology enhancements Validate solution designs and prototypes with the assistance of users with disabilities When using agile methods, ensure Section 508 conformance requirements are included in the "definition of done" for user stories that support development of a user interface/feature. If you do not factor a Section 508 conformance assessment into the determination of when each development iteration is complete, accessibility barriers may accumulate over time. Address accessibility needs during development: Train developers to understand the rationale and importance of Section 508 standards conformance Provide Section 508 conformance testing tools to assist developers with performing unit testing, and provide training on how to use these tools to generate accessible solutions Encourage the use of accessible code libraries and design patterns, such as the US Web Design System When using open source development platforms ensure responsibility for fixing accessibility issues is clearly determined
	Address accessibility needs during testing (see Play 10 for more information): Determine what accessibility testing methods you will use. Agencies are encouraged to use a test method aligned to the ICT Testing Baseline. When using agile methods, ensure accessibility requirements are validated in unit tests throughout iterative development Identify where accessibility issues are located, and troubleshoot potential root causes Implement processes and tools to track accessibility bug fixes and their resolution status Follow a test plan that includes: Conducting testing with assistive technology Conducting usability testing
	During deployment and maintenance: Ensure configuration and integration activities do not introduce new accessibility barriers Monitor and validate updates to the technology solution to ensure they will not negatively affect accessibility Monitor and validate changes to the technology environment to ensure that they will not negatively affect accessibility (operating system, browser, hosting platform, etc.)
	Include IT accessibility subject matter experts as authoritative decision makers at critical development checkpoints.

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: By QX FY2X ensure that content created using the enterprise-wide chat or internal real-time messaging system conforms to at least XX% of applicable Section 508 requirements.

Generic KPI: By EOFY FY2X remove all multi-function printers from agency offices that do not conform to Section 508 hardware and software requirements.

Generic KPI: By QX FY2X ensure XX% of all agency developed desktop software and native mobile applications adhere to all relevant Section 508 standards.

Generic KPI: By EOFY FY2X ensure all agency developed desktop software and native mobile applications adhere to all relevant Section 508 standards.

Generic KPI: By EOFY FY2X remediate the current tool, create accessible templates or invest in an enterprise-wide survey authoring tool that can be accessed and used by all users.

Generic KPI: By QX FY2X ensure that the organization's enterprise-wide video player conforms to XX% of applicable Section 508 requirements.

Generic KPI: By QX FY2X ensure that the organization's most widely-used, public facing fillable form conforms to XX% of applicable Section 508 requirements.

Generic KPI: By QX FY2X, determine what percentage of intranet web pages currently live on agency websites fully conform to Section 508 standards.

Generic KPI: By QX FY2X, test and remediate agency public internet web pages to ensure that at least XX% of web pages fully conform to Section 508 standards.

Generic KPI: By QX FY2X ensure that XX% of external and internal surveys conform to applicable section 508 requirements.

Generic KPI: By QX FY2X ensure that surveys created using the primary survey authoring tool conform to at least XX% of applicable Section 508 requirements.