Accessibility conversations usually start with risk — a lawsuit, an audit, a procurement requirement — but the stronger long-term argument is the one that rarely gets made: accessible products reach more people and cost less to maintain.
By VVnT SeQuor Team··2 min read
In this article
01
What changed in WCAG 2.2
WCAG 2.2 added nine new success criteria on top of 2.1, with a particular focus on cognitive…
02
The market you’re not reaching
Roughly one in six people globally live with some form of disability, and that doesn’t count…
03
The compliance landscape
Section 508 governs US federal procurement — if you sell to US government agencies,…
What changed in WCAG 2.2
WCAG 2.2 added nine new success criteria on top of 2.1, with a particular focus on cognitive accessibility, mobile interaction patterns, and authentication. Focus Not Obscured, Dragging Movements, Target Size (Minimum), and Accessible Authentication are the ones most product teams encounter first — they affect everyday UI decisions like modal placement, drag-and-drop interactions, and tap target sizing, not just screen-reader edge cases.
WCAG’s four POUR principles — every success criterion in the standard, including what changed in 2.2, maps back to one of these four.
The market you’re not reaching
Roughly one in six people globally live with some form of disability, and that doesn’t count the much larger group affected by situational or temporary limitations — a broken arm, bright sunlight on a phone screen, a noisy environment that makes audio content unusable. Accessible design decisions — sufficient contrast, resizable text, captions, logical keyboard navigation — make products easier to use for everyone in those conditions, not just permanent assistive-technology users.
The compliance landscape
Section 508 governs US federal procurement — if you sell to US government agencies, conformance isn’t optional.
The ADA has been applied to websites and apps through litigation even without a specific digital-accessibility statute, making WCAG conformance the de facto legal standard referenced in settlements.
A growing number of enterprise RFPs now require a current VPAT® / Accessibility Conformance Report before a vendor can even be evaluated.
India’s GIGW guidelines apply a similar WCAG-aligned bar for government and PSU-facing digital properties.
The remediation math: fixing a contrast ratio or a missing form label during design review costs a design tweak. Fixing it after launch, discovered through a complaint or an audit, costs an engineering sprint, a re-test cycle, and often a VPAT re-issue. Accessibility debt compounds exactly like technical debt.
Where to start if you’re at zero
An initial WCAG audit against a representative set of key user flows — not the whole site at once — gives you a prioritized, evidence-backed remediation list rather than a vague sense that “accessibility needs work.” From there, VPAT® / ACR preparation turns that audit into the document your enterprise customers and procurement teams are actually asking for.
Frequently asked questions
Is WCAG 2.2 AA the right conformance target for most organizations?
Yes, Level AA is the target referenced by most legal frameworks, government requirements and procurement standards, including Section 508 and most ADA settlements. Level AAA is rarely required in full and some AAA criteria aren’t achievable for all content types.
What’s the difference between a VPAT and an ACR?
VPAT® (Voluntary Product Accessibility Template) is the standardized template; ACR (Accessibility Conformance Report) is the completed document produced from it for a specific product. People often use the terms interchangeably, but the ACR is the deliverable procurement teams actually request.
Can automated scanning tools catch everything?
No. Automated tools reliably catch roughly a third of WCAG success criteria — contrast ratios, missing alt text, form labeling. Keyboard navigation logic, focus order, and meaningful screen-reader experience require manual testing by someone using assistive technology.
This is general guidance, not a scoped engagement plan. If you want one for your specific environment, talk to our Accessibility & Inclusive Product Engineering practice.