Set Requirements that Include Accessibility

Role in the ENABLE Model

Setting requirements is the first and most fundamental act of care. It defines accessibility as a core obligation -- not a discretionary add-on. The absence of early mandates is often the root cause of systemic inaccessibility.

Without this stage, all subsequent acts -- design, development, testing -- lack structure. Early neglect here multiplies downstream burdens.

Why it matters

Requirements set the foundation. Without codified expectations around accessibility, every subsequent action (design, development, testing) operates in ambiguity or neglect. Mandating inclusion from the outset prevents exclusion from being baked into infrastructure.

Examples

In the news

Justice Department Finalizes Rule Requiring State and Local Governments to Make their Websites Accessible (April 24, 2024)
-- U.S. Department of Justice

• The DOJ finalized a historic rule under ADA Title II requiring all state and local government websites and mobile apps to meet WCAG 2.1 Level AA by 2026-2027. This rule transforms accessibility requirements from informal guidance into enforceable mandates, setting a precedent for legal protections that could extend to private sector websites.

The EAA comes into effect in June 2025. Are you ready? (June 28, 2025)
-- European Commission

• The European Accessibility Act became law across all EU member states, requiring e-commerce services, banking, transportation, and digital products to meet accessibility standards. The EAA applies to any company selling to EU consumers, regardless of location, making accessibility requirements a baseline for global market access.

OMB M-24-08: Strengthening Digital Accessibility and the Management of Section 508 (December 21, 2023)
-- Office of Management and Budget

• The OMB issued guidance requiring all federal agencies to designate Section 508 program managers, publish accessibility statements on all websites, and incorporate accessibility into agency policies. This directive treats accessibility requirements as a core obligation, not a discretionary add-on.

• Use institutional policies such as Section 508 in U.S. federal procurement to require accessibility.
• Apply ADA standards in state services
• Adopt UN Convention on the Rights of Persons with Disabilities (CRPD) globally
• Incorporate WCAG 2.2 compliance in design contracts
• Bake accessibility into definition of done for all features
• Use procurement language that mandates WCAG compliance
• Use compliance frameworks like VPATs in vendor review

Care sounds like

"Our speech recognition AI must be usable by people who stutter."
"We must write procurement language that makes accessibility non-negotiable."
"Let's align this project's definition of done with accessibility standards."

Neglect Sounds Like

"Accessibility is not a deliverable."
"It's not legally required for our sector."
"We'll add it later if we have time."
"It's not in the spec."

Real-world Scenario

A municipal procurement office updates its RFP templates to require vendors to submit a Voluntary Product Accessibility Template (VPAT). This shifts accessibility from an optional concern to a required deliverable -- forcing every bidder to articulate their plan.