WCAG 2.1 level AA is a technical bar, not a law

The workload

Building to the Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA means meeting a defined set of success criteria organised under four principles: perceivable, operable, understandable and robust. The 2018 W3C Recommendation states that Level AA conformance requires satisfying all Level A criteria plus the additional AA criteria, which include a minimum contrast ratio of 4.5:1 for standard text, captions for prerecorded audio, a consistent heading structure, and keyboard operability without traps. For a one-person team this is design and front-end work distributed across a product rather than a single feature: labelling, contrast, focus order and alternative text have to be correct throughout, not added once at the end.

What the documents show

Verified: WCAG 2.1 reached formal Recommendation status on 5 June 2018, per the dated version of the specification. Verified: it did not deprecate WCAG 2.0, which remains a separate Recommendation in its own right. Verified: the W3C's own guidance page states that WCAG 2.0, 2.1 and 2.2 are all still standing standards, and that the harmonised standard referenced by the European Accessibility Act, EN 301 549, currently points to WCAG 2.1. Verified: WCAG is, in the W3C's own description, a technical specification, not a statute; it becomes a legal bar only where a specific law or regulation names it. The current, non-dated WCAG 2.1 page, as retrieved on 16 September 2026, now serves a version carrying incorporated errata rather than the original 2018 text verbatim, which matters if a compliance record cites the current page rather than the dated 2018 Recommendation.

The operating cost

The specification itself carries no fee; it is a free, publicly published document. The cost is the engineering and design time to meet the criteria and, separately, to document that a specific version was met on a specific date, since the living page's content can be corrected without changing its version number. Neither document attempts to price that engineering time, and none is estimated here.

The stop condition

Editorially: there is no single point at which meeting WCAG 2.1 AA becomes unnecessary while a product remains in an EU or US consumer market, since the standard is referenced by ongoing law rather than a one-time filing. A workable stop condition is version-based: treat a specific WCAG version and level, checked against an automated and a manual review, as the target for a release, and re-check it against whatever version the applicable law or contract names, rather than chase every future WCAG revision indefinitely.

• Does the product need to satisfy WCAG 2.1 specifically, or does the applicable law or contract point to a later version such as 2.2?
• Is the compliance record dated against the 2018 Recommendation text or the current, periodically corrected page?
• Which Level AA criteria are hardest to verify without a screen-reader or keyboard-only test pass, and has that pass actually happened?

WCAG 2.1 AA is a specific, checkable bar, not a certificate. Meeting it is evidence a founder can point to; it is not, by itself, proof of compliance with any particular country's law.