Accessibility teams often face a translation problem: leadership may agree that access matters without connecting that commitment to a budget, owner, or roadmap decision. This five-step process closes that gap.
- 5 steps, from diagnosing the real objection to turning approval into governance
- Chosen around what actually moves: budget, capacity, or roadmap space
- Written for accessibility practitioners preparing an executive conversation
- Includes a one-page executive brief template and answers to common objections
An accessibility practitioner presenting a one-page brief to executives around a meeting table
What Leadership Buy-In Actually Requires
To get leadership buy-in for accessibility, connect an evidenced barrier to a priority an executive controls: risk, service access, quality, employee experience, equity, budget, or mission. Then make a scoped ask with an owner, timeline, and success measure.
Although the examples below focus on digital accessibility, the same process can support physical spaces, public services, procurement, employment, communications, and events. Define the scope before asking for resources.
What this guide gives you
- Verbal agreement is not buy-in. Treat movement in budget, capacity, or roadmap space as the real signal.
- The pitch fails more often on audience than on content: technical success criteria explain how, not what is affected or what decision is needed.
- Evidence you own, from your own flows and support data, is usually more actionable than an industry statistic.
- Small, time-bound asks attached to work that already has budget are easier to approve than standalone requests.
- Approval that is not documented as policy, funding, and named ownership tends not to survive a change in leadership.
Why Accessibility Buy-In Stalls
Verbal agreement alone does not allocate resources. A meaningful commitment usually requires budget, capacity, or roadmap space. You have stronger evidence of buy-in when at least one of those things moves.
The usual mistake is pitching the wrong thing to the wrong person: presenting guidelines, conformance levels, and audit scores to whoever will take the meeting. Technical success criteria explain how; start with what is affected, why it matters, and what decision is needed.
Reframe the first conversation. Its purpose is not to extract a yes; it is to create shared clarity about what is broken, who it excludes, and what decision is needed. Clarity gives the conversation a more useful starting point than argument alone.
Four practical signals show that support is becoming an organizational commitment:
- A line item in an actual budget, not a promise to "find something"
- Accessibility written into the definition of done for new work
- A named executive attached to the policy by title
- A reporting cadence that continues through changing priorities
Step 1: Diagnose the actual objection before you build a case
Best at preventing the most common waste: a case argued against an objection the executive never had.
Best for: Practitioners preparing their first leadership conversationFour blockers look identical from the outside and need completely different pitches:
- No budget. They believe in it, but they cannot fund it this cycle.
- No perceived users. They think disabled people are not in their audience.
- No capacity. The team is already underwater.
- No owner. Everyone agrees, nobody is accountable.
If feasible, speak with a small number of decision-makers individually before presenting to a group. One-to-one conversations can surface concerns that may not appear in a group discussion. Watch especially for the objection nobody states out loud: fear that a formal assessment will surface a problem that then has to be disclosed, budgeted, and fixed.
Write each objection down in the executive's own words, then answer that sentence directly in your materials. A case built against an assumed objection is unlikely to persuade.
Before finalizing the case, involve disabled people and representative organizations in defining the problem, testing the experience, and reviewing priorities. Provide compensation and access support for meaningful participation.
Step 2: Match the Case to Each Decision-Maker
Best at making one shared brief land with five different executives who each control something different.
Best for: Approvals that need finance, legal, marketing, engineering, and HR to agreeDifferent decision-makers need different evidence. Use one shared core brief, then adjust the emphasis for each stakeholder.
- CFO: show the cost, timing, and resource trade-offs of addressing barriers at different project stages.
- Legal and risk: For covered U.S. state and local governments, the Department of Justice's Title II fact sheet explains that web content and mobile apps generally need WCAG 2.1 Level AA, subject to the rule's scope and exceptions. Organizations offering products or services covered by the European Accessibility Act should confirm the applicable national requirements.
- CMO and development: Reach and trust. Donation forms, event registration, and email campaigns that create barriers for assistive-technology users may make measured journeys harder to complete; connect this point to your own user research, support data, or conversion data.
- CTO and engineering: Accessible and maintainable markup often overlap. Semantic structure, predictable focus management, and tested components can support maintainability and help prevent some errors when paired with testing.
- HR and people: Internal tools that exclude disabled employees can make hiring, retention, and workplace-inclusion commitments harder to deliver.
- Nonprofit context: connect accessibility to equitable program delivery and any applicable funder or grant requirements.
Step 3: Build a One-Page Accessibility Business Case
Best at putting the evidence and the decision requested on the same page, so leadership can see how one leads to the other.
Best for: Anyone who has evidence but no document an executive will readUse a one-page executive brief with three evidence blocks: your data, one external benchmark, and a named cost or consequence. Keep the decision requested on the same page so leadership can see how the evidence leads to action.
Your own data. Run an automated scan plus a short manual test with a screen reader or another relevant assistive technology on your highest-value flow, such as a donation form, application, intake process, or public-service journey. Findings from your own product or service are usually more actionable than an industry statistic.
One external benchmark. Use it for context, not as the argument. WebAIM's 2026 Million report found detected WCAG 2 failures on 95.9% of sampled home pages, up from 94.8% in 2025; because it measures automatically detectable issues, it is an industry signal rather than a full conformance verdict.
One named consequence. Record a short video of a real barrier in your own flow. Pull support tickets, abandoned-form analytics, and refund or re-submission requests that may signal access failures. Treat those signals carefully, then state one concrete consequence of inaction and one concrete resource or decision required, so the comparison is evidence-based rather than opinion.
One-Page Executive Brief Template
| Field | What to include | | — | — | | Current barrier | What prevents access | | People affected | Users, employees, residents, or customers affected | | Evidence | Audit findings, support data, research, or user testing | | Organizational consequence | Risk, service failure, rework, exclusion, or missed opportunity | | Proposed action | The first specific intervention | | Decision requested | Budget, capacity, owner, approval, or policy change | | Sponsor and owner | The executive sponsor and operational owner | | Timeline and measure | Pilot period, review date, and success measure |
For additional checklists and accessibility materials, explore the Foundation's accessibility resources.
Step 4: Make a Specific, Scoped Ask
Best at converting general support into a decision that has a scope, an owner, and a date.
Best for: Teams stuck at "leadership agrees" with nothing scheduledAsk for a defined decision rather than a general commitment to accessibility. State the scope, resource request, owner, and decision date.
One example is a 90-day pilot on the highest-traffic or highest-impact flow, one training session for the team that owns it, and one named owner with agreed capacity and authority to coordinate the work.
Offer two or three options with clearly different scope, resource needs, and timeframes so leadership can choose a feasible starting point. Agree on the success metric before the pilot starts, so the review can focus on the agreed evidence rather than restarting the case.
Step 5: Turn Approval Into Governance
Best at keeping the commitment alive after the executive who approved it moves on.
Best for: Programs that won approval once and do not want to win it againApproval can weaken when leadership changes, or priorities shift. Document the commitment so it can continue beyond the person who approved it. Four artifacts make the commitment easier to sustain:
- A published statement of commitment with clear scope and principles
- An organization-wide policy, not only a team-level practice
- A funded action plan with dates
- An executive sponsor and operational owner identified by role
Put accessibility requirements into procurement so new tools are evaluated against them, and add accessibility criteria to vendor contracts and your definition of done. Set a quarterly reporting cadence to leadership using the same metrics each time.
The executive sponsor should remove organizational barriers and protect the priority; the operational owner should coordinate delivery, evidence, and reporting.
Pair the policy with a resourced program so it does not become a document nobody reads. If you need help connecting assessment, policy, roadmaps, and implementation, review the Pineda Foundation's advisory approach.
Prepare for Common Accessibility Objections
"We do not have disabled users." Standard analytics may not reliably identify assistive-technology use. An inaccessible journey may also prevent people from completing it, so traffic data alone should not be used as proof that access is unnecessary.
"It only helps a small group." The World Health Organization estimates that 1.3 billion people experience significant disability, roughly 16% of the world's population, or one in six. Add aging users, temporary injuries, and situational limits such as bright sunlight or a noisy room.
"It would need a full rebuild." A full rebuild is not always necessary. Prioritize templates or journeys by importance, reach, and risk; fix the highest-value barriers first and place the remaining work on the roadmap.
"It is too expensive." The cost and effort can be easier to manage when accessibility is included in design review, procurement, and code review rather than left to post-launch remediation.
"We have bigger priorities." Accessibility can be built into existing priorities such as service quality, security, performance, employee experience, and equitable participation.
If Leadership Still Says No
Build a coalition. Legal, procurement, customer support, HR, and program teams may experience the same barrier from different angles. A cross-functional request can show that the issue affects more than one team.
Do the smallest unfunded action that can produce useful evidence, document the result, and return with findings instead of argument. Use real external triggers honestly: an upcoming procurement cycle, a funder requirement, or a redesign already scheduled. Attaching accessibility to a project that already has budget may be easier to fund than a standalone request.
Measure Buy-In and Program Progress
Leading indicators include the percentage of new work reviewed for accessibility, training completion, issues caught before launch, and the number of teams using accessibility requirements in delivery.
Lagging indicators include the selected conformance level, median time to fix, complaints received, and whether people can complete important journeys with fewer barriers.
Report the trend and, with consent, an anonymized example of a user barrier or improvement in each leadership update. Long-term success is a program that remains active through staffing and priority changes.
Accessibility Leadership Buy-In FAQs
How do I get leadership buy-in for accessibility?
Connect a documented barrier to a priority the decision-maker controls, such as service access, risk, quality, employee experience, equity, budget, or mission. Show who is affected, what decision you need, who owns delivery, and how success will be measured.
How do I build a business case for accessibility?
Use organization-owned evidence first. Explain the barrier, affected people, organizational consequence, proposed action, required resources, and success measure. The W3C business-case guidance notes that ROI can be useful, but it is not the only way to measure the value of an accessibility commitment.
What should an executive accessibility proposal include?
It should answer five questions: what barrier exists, who is affected, why does it matter now, what decision or resources are requested, and how will the organization know whether the action helped?
How can I get accessibility funding when there is no dedicated budget?
Attach the first action to an already-funded redesign, procurement cycle, training program, service improvement, or capital project. Make the request small and time-bound, document what the work shows, and use that evidence in the next budget discussion.
What does real leadership buy-in for accessibility look like?
It includes more than verbal support: budget or agreed capacity, an executive sponsor, an operational owner, accessibility requirements in procurement and delivery processes, and recurring reporting to leadership.
Make Accessibility Part of the Operating Model
Long-term leadership means accessibility is supported by policy, delivery practices, procurement, resourcing, and measurement, not only by a final audit.
This systems-oriented approach aligns with the Foundation's public focus on disability justice, inclusive policy, research, education, and systems change. Learn more about the Foundation's disability-justice work.
Start with one flow, one executive, and one review window. If your organization needs help assessing accessibility, building a roadmap, or connecting policy with implementation, contact the Foundation.
Start with one flow, one executive, and one review window
If your organization needs help assessing accessibility, building a roadmap, or connecting policy with implementation, the Pineda Foundation can help.