The gap between "compliant" and accessible is where lawsuits live
Two hours, live online, with a short break. An untangling of WCAG, the EAA, the ADA, and the gap between passing an audit and actually being usable by real people.
- WCAG vs the law — what's a technical standard, what's legally binding, and where the lines cross.
- Levels A, AA, AAA — what they actually require, and why almost everyone targets AA.
- Twelve hard questions about real-world accessibility exposure, raised and answered live.
Compliance theatre vs the real exposure.
Everyone says they're "compliant." Almost nobody can tell you with what. Accessibility stopped being a nice-to-have and quietly became a legal obligation — and most companies are aiming at a target they can't name, hitting a level they can't define, and signing off on statements they can't back up. This free, two-hour webinar clears up the confusion that's putting organisations at risk.
We untangle the three things everyone mixes up: the standard (WCAG), the law (the EAA, the ADA, and friends), and the gap between passing an audit and actually being usable by real people. You'll find out what Level A, AA, and AAA actually require, why AA is the line almost everyone is legally expected to hit, and what "we're WCAG 2.2 AA compliant" really commits a company to.
No checkbox theatre, no legalese for its own sake — just a clear-eyed look at where the real exposure is, who in your organisation is supposed to own this (spoiler: usually nobody), and what it means for the people in the room. Because the distance between "compliant" and accessible is exactly where the lawsuits live.
Twelve questions, posed from the stage.
These are the questions the session is built around — posed and answered live, with room for your own at the end.
- 01
Is WCAG actually a law — and if not, why does everyone talk about it like one?
- 02
If WCAG isn't the law, then what exactly is the legally binding thing?
- 03
What does a law mean when it says a product must be "accessible" — accessible by whose definition?
- 04
A, AA, AAA — what do these levels actually require, and why does almost everyone target AA?
- 05
Why is AAA almost never a realistic company-wide goal?
- 06
When a company says "we're WCAG 2.2 AA compliant," what has it actually committed to?
- 07
Is compliance a one-time audit, or something you're on the hook for forever?
- 08
What's the real difference between a company that treats accessibility as a checkbox and one that builds it in — and what does that difference cost?
- 09
Who in an organisation actually owns accessibility — and what happens when the answer is "nobody"?
- 10
What's the actual exposure if a company just ignores this — fines, lawsuits, reputation, or nothing in practice?
- 11
Does the European Accessibility Act change who has to care, and by when?
- 12
If accessibility lands in your testing scope tomorrow, where do you even start?
Save your seat — before someone else does.
You'll get the Zoom link the day before the session, and a calendar invite straight away.
The person who'll also answer the email.
Imola
Software-testing practitioner and quality advocate with fifteen years in the field — across product teams, agencies and in-house QA orgs. Has hired testers, been hired as one, and watched the job market change shape three or four times already.
Today Imola runs Pearly Quality from Hungary: the workshops, the monthly letter, the podcast, and the occasional honest conversation about where this profession is actually going.