Why 'Our Whole Site Is AA Compliant' Is an Overclaim
After checking only the homepage against WCAG 2.1 AA and finding zero issues, a teammate declares "the whole site is AA compliant." A real accessibility audit works differently from a single spot-check.
What's the correct scope a WCAG conformance claim is actually made against?
The correct answer is "Per page (or representative page type)."
A conformance claim is technically made per page, not automatically for an entire site — a real audit walks through representative page types (homepage, a form page, a content page, a checkout flow) rather than asserting conformance for the whole product from a spot-check of one screen. Declaring the whole site compliant after checking one landing page is exactly the overclaim a rigorous interviewer would probe.
"Per site as a whole" is the overclaim itself, not the correct scope. "Per component library" isn't how WCAG defines conformance scope at all. "Per user session" isn't a conformance unit WCAG uses either.
Share this question