You will not get a second hour of an executive's calendar to make this case again. If the first meeting goes long, gets vague, or turns into a WCAG history lesson, you don't get a do-over next quarter. You get a polite "let's revisit this later," which means never.
So the meeting has to work the first time. Lead with the real market size. Back it with a real deadline that is already sitting on the calendar whether anyone in the room acts on it or not. Close with one specific, real finding from your own site. That's the whole meeting. Everything else is padding that costs you the attention you came in with.
The Stat: An estimated 1.3 billion people, about 16% of the global population, experience significant disability. (Source: WHO)
Why the order matters more than the content
Most people who walk into this meeting start with the wrong thing. They open with WCAG itself: the four principles, the conformance levels, the difference between AA and AAA. That's real information, and it's exactly the wrong opener, because it asks the executive to learn a framework before they've been given a reason to care about it.
Reverse the order. Give the reason first. The framework can come later, in a follow-up document nobody has to sit through live.
Step one: open with the market, not the framework
Start the meeting with a single sentence: an estimated 1.3 billion people, about 16% of the global population, experience significant disability, according to the World Health Organization. Say it plainly and let it sit for a second. You are not describing an edge case or a compliance footnote. You are describing a population roughly the size of the world's largest country, distributed across every market the business operates in.
This is the moment to point them to WHO's official fact sheet on disability rather than a vendor's slide deck. A neutral, globally recognized health body citing this number carries more weight in a budget conversation than any internal estimate you could produce, and it removes the "where did this number come from" objection before it's asked.
Step two: show the deadline that's already on the calendar
Market size motivates. Deadlines move budgets. This is the step people skip, and it's the one that actually gets a line item approved.
Two real dates matter here, and neither is a suggestion:
- The EAA, formally Directive (EU) 2019/882, has been in application since 28 June 2025. If the business sells into the EU, this is not a future consideration. It is already active.
- The US DOJ's 2024 Title II rule sets ADA deadlines of April 24, 2026 and April 24, 2027 for state and local government websites and apps to meet defined accessibility standards.
Say it directly: these are fixed dates, not open-ended advice. That distinction is what makes this section land differently than a general appeal to doing the right thing. Executives are used to hearing that accessibility is "important." They are less used to hearing that a specific regulation with a specific date is already running, whether or not it's on their roadmap.
If someone in the room pushes back on interpretation or scope, don't argue from memory. Point them to the W3C's own Business Case for Digital Accessibility, a resource built specifically to make this argument without leaning on any single vendor's framing. It exists precisely so you don't have to be the only voice making the claim.
Step three: close with one real finding from your own site
This is the step that turns an abstract argument into a decision. Market size and deadlines establish that the topic deserves attention. A single, specific, verifiable finding from your own product is what gets someone to say "fix that" before the meeting ends.
Don't bring a list of forty issues. A long list reads as an overwhelming project with no clear owner or starting point, and it invites the meeting to end in "let's form a working group," which is where these conversations go to die. Bring one. A checkout button with no accessible label. A form error that only shows as a red border with no text description. A modal that traps keyboard focus and never lets go. Pick the one that's easiest to demonstrate live, on screen, in under sixty seconds.
Concrete beats comprehensive in this specific meeting. You can hand over the fuller list afterward, once you have a decision-maker who's already agreed the topic is worth fixing.
What to leave out of this meeting entirely
- WCAG's success criterion numbering system, unless someone asks
- Internal audit history or blame for how things got this way
- Any invented cost-savings figure or ROI multiplier you can't source
- A request for a large, undefined budget with no first deliverable attached
- Comparisons to what a specific competitor is or isn't doing
Every one of these either slows the meeting down or opens a debate you don't need to have in order to get a yes. Save them for the follow-up document, if anyone asks for one.
It helps to think of this meeting as a pitch for a single decision, not a briefing on the whole subject. An executive does not need to leave understanding WCAG. They need to leave having said yes to one specific, small, dated next step. Every extra fact you include past that goal is a chance for the conversation to drift into a debate you did not come prepared to win, and a debate is exactly what turns a fifteen-minute yes into a three-month "let's circle back."
A simple structure to bring into the room
| Meeting segment | What you say | What you show |
|---|---|---|
| Open (1-2 min) | The market is 1.3 billion people, 16% of the global population | WHO fact sheet citation |
| Deadline (2-3 min) | EAA is already in application; ADA Title II has fixed 2026/2027 dates | The two dates, written plainly |
| Proof (2-3 min) | Here is one real issue on our own site | Live demonstration or screenshot |
| Ask (1 min) | One clear, small next step | A specific owner and a specific date |
The checklist for the day before the meeting
- Confirm the one finding you'll demonstrate actually reproduces live
- Have the WHO figure and the two regulatory dates written down, not recalled from memory
- Cut any slide that explains WCAG conformance levels before the ask is made
- Prepare a single, specific next step to request, not a general budget
- Know who in the room can actually approve that next step, and address the ask to them directly
- Have a link ready to send afterward for anyone who wants the deeper background
We've written before about why this is a leadership problem in the first place, and it's worth reading if this meeting is happening because the topic has been quietly stuck at the individual-contributor level for too long. Getting one executive to say yes in one meeting is the fastest way to unstick it.
If you want your specific finding ready before you walk in, get a free audit finding to bring into the room rather than relying on a guess about what's broken. A real, reproducible issue from your own product is worth more in that meeting than any general statistic, and it takes the guesswork out of step three. If you'd rather talk through how to frame the meeting itself, our team is reachable directly at experts@wcag.world, no pitch attached, just a conversation about what's actually going to move your specific room.