Provision Resources for Accessibility

Provisioning resources for accessibility means making the time, budget, expertise, tooling, and organizational capacity available to do accessibility work. Anyone who controls a resource can make this commitment -- an executive setting a budget, a manager scoping a project, a developer estimating a task, or a solo practitioner deciding how to spend an afternoon. Builders are themselves a resource -- they can direct their own time, skill, and attention toward accessibility whether or not an organization has required it.

Role in the ENABLE Model

The ENABLE Model places resource provisioning second. Setting requirements defines the obligation. Resource provisioning determines whether accessibility work has what it needs. Without it, subsequent stages -- content, design, development, testing -- operate without the capacity to deliver on accessibility.

Disambiguation with later stages

Resource provisioning is the act of securing capacity, not exercising it. Allocating a budget for accessibility audits, appointing a Chief Accessibility Officer, funding a grant program, or writing accessibility requirements into a vendor contract are provisioning acts. They make later work possible without constituting it. When the defining act is creating content, designing, developing, testing, or iterating on a product, the act is downstream of provisioning. As an example, providers of accessibility services -- testing firms, consultancies, tool vendors -- are located where their work operates. The client organization's decision to engage and fund them is the provisioning act.

Why It Matters

Organizations regularly cite lack of time, budget, or expertise as reasons they cannot deliver on accessibility requirements. Those are provisioning failures. But the failure rarely belongs to a single decision-maker. Time estimates that exclude accessibility work, hiring pipelines that do not screen for accessibility skills, training budgets that do not cover accessibility tools -- each withholds part of what accessibility needs from whoever controlled that resource.

Builders apply the same distributed logic to care. A developer who writes semantic HTML without being asked, a designer who chooses inclusive patterns before anyone reviews their work, a content creator who adds alt text to every image -- each is directing the resource they control toward accessibility. A mandate from leadership enables this work. It does not create it.

Grounding

The U.N. Committee on the Rights of Persons with Disabilities says that states should "provide both the human and material resources necessary to remove the barriers."¹ Ontario gives organizations similar planning guidance: when they build multi-year accessibility plans, they should estimate the human, financial, and technical resources needed and available.²

Standards bodies also separate resourcing from downstream implementation work. ISO/IEC 30071-1 says ICT accessibility has to be implemented at organizational and system-development levels.³ W3C's Accessibility Maturity Model treats knowledge and skills, personnel, support, and procurement as separate dimensions from the ICT development lifecycle.⁴

Employers withhold accessibility when they refuse to fund it. Deloitte's Disability Inclusion at Work 2024 survey covered 10,000 respondents across 20 countries and found that nearly three-quarters of respondents who requested accommodations had at least one request rejected. Among those rejections, 41% were described as too costly or expensive.⁵

Governments also fund accessibility as its own workstream. Canada's Enabling Accessibility Fund offers grants up to $200,000 and contributions up to $3 million per project.⁶ Singapore's Enabling Masterplan 2030 coordinates 29 recommendations across disability policy through 2030, with yearly updates tracking delivery.⁷

Organizations create dedicated accessibility authority when they decide resourcing cannot stay informal. Microsoft was publicly using the Chief Accessibility Officer title by March 2011.⁸ IBM appointed Frances West as its first Chief Accessibility Officer in July 2014.⁹ Canada's Accessible Canada Act created the Chief Accessibility Officer role in 2019.¹⁰

Kate Knibbs reported that Twitter's accessibility layoffs showed how quickly accessibility capacity can disappear when staffing decisions treat it as expendable.¹¹

In the news

Microsoft's AI for Accessibility program awards grants to organizations building accessible AI tools
-- Microsoft

• Microsoft funds an ongoing grant program providing up to $75,000 per organization, plus Azure credits and technical support, to develop AI-powered accessibility tools. The program treats resource provisioning as a structural commitment, funding the means to build accessible technology rather than expecting it to happen without investment.

OMB M-24-08 requires federal agencies to designate Section 508 program managers (December 21, 2023)
-- Office of Management and Budget

• OMB M-24-08 requires all federal agencies to name a Section 508 program manager and publish agency-level accessibility statements. The directive converts an unfunded mandate into a staffed role -- a named person with designated authority and responsibility for resource provisioning toward accessibility.

Canada's Enabling Accessibility Fund
-- Government of Canada

• The Enabling Accessibility Fund provides up to $200,000 for small projects and up to $3 million for larger initiatives, treating resource provisioning for accessibility as a distinct government function -- separate from setting accessibility requirements or enforcing compliance.

South Korea allocates 9.2 billion won for kiosk accessibility (2025)
-- TPGi

• South Korea announced a dedicated funding initiative of 9.2 billion won (approximately USD 6.66 million) for kiosk accessibility, including technical consulting subsidies and priority hardware distribution -- a named budget for accessibility provisioning at national scale.

Examples

Time

• Including accessibility work in project and sprint estimates
• Blocking time for accessibility review before launch
• Directing personal work time toward accessibility without waiting for a formal requirement

Money

• Budgeting for audits, user research with disabled participants, and remediation
• Purchasing screen readers, testing tools, and assistive devices for QA
• Paying out of pocket for accessibility tools or training when an organization hasn't provided them

People

• Designating a named owner for accessibility, even if part-time or a single person at a small organization
• Building accessibility expertise into hiring criteria and job descriptions
• Treating oneself as the responsible party when no one else has been assigned

Knowledge

• Funding training so developers, designers, and content creators can do accessibility work competently
• Sourcing external accessibility consultants when in-house expertise is limited
• Self-directing toward accessibility education when formal training hasn't been provided

Procurement

• Building accessibility requirements into vendor contracts so that suppliers arrive with the required capability

Care sounds like

"Who owns accessibility on this project? Let's put a name to it."
"I'm including accessibility work in my estimate -- it's part of doing this right."
"We need a line item for an audit before launch."
"Nobody asked me to, but I'm building this accessibly -- it's within my control."
"I taught myself screen reader testing because we had no budget for training."

Neglect sounds like

"We don't have the budget for that."
"Nobody has time to deal with accessibility right now."
"We'll fix it when someone complains."
"We care about accessibility but it's not in scope for this cycle."
"Nobody required it, so I didn't think about it."

Real-world Scenario

A government agency updates its procurement policy to require WCAG 2.1 AA compliance from all vendors. No one inside the agency is assigned to verify compliance, no budget covers independent audits, and the procurement team has no training in reading accessibility documentation. Vendors submit VPATs; nobody reviews them. Adding a part-time accessibility reviewer and an annual audit budget would have provisioned what the policy needed to produce delivery.

A developer on the same agency's internal tools team writes semantic HTML, labels all form inputs, and tests keyboard navigation on every component they ship -- without being asked. No policy required it. When an external audit eventually runs, their work passes. The rest of the codebase does not.

---

Footnotes

1. U.N. Committee on the Rights of Persons with Disabilities, General comment No. 2 (2014), Article 9: Accessibility ↩

2. Ontario: How to create an accessibility plan and policy ↩

3. ISO/IEC 30071-1:2019 ↩

4. W3C Accessibility Maturity Model ↩

5. Deloitte: Disability Inclusion at Work 2024, A Global Outlook ↩

6. Canada: About Enabling Accessibility Fund ↩

7. Singapore Ministry of Social and Family Development: Enabling Masterplan 2030 ↩

8. Microsoft Announces New Accessibility Offerings ↩

9. IBM Names Chief Accessibility Officer ↩

10. Summary of the Accessible Canada Act ↩

11. Kate Knibbs, WIRED, Twitter's Layoffs Are a Blow to Accessibility ↩