Compliance and accessibility Nonprofit By Shashank Ayyar and Partha Biswas Last updated on October 13, 2026 6 min read

WCAG conformance: four ways it quietly lapses after an audit

Timeline showing an accessibility audit date followed by four kinds of change that affect WCAG conformance.

For a nonprofit that receives HHS funding, the Section 504 rule sets WCAG 2.1 Level AA from May 11, 2027 at 15 or more employees, and from May 10, 2028 below that. If the plan is to meet it with an audit, the audit describes the site on the day it was tested. WCAG conformance after that day depends on what changes next. What happens to it as the site keeps changing?

TL;DR

WCAG conformance is a property of specific pages on a specific date, and it lapses in four ordinary ways: content edits, plugin and theme updates, new embeds and widgets, and new pages, forms or processes. A site that rarely changes keeps it longer, but W3C sets no re-check interval and no study we found measures the decay. W3C’s guidance requires conformance on full pages and complete processes, so one new image without alt text or one untested donation step is enough to break it. Someone has to operate the site after the audit, and updates are one of the four routes: see what NoDrama’s WordPress maintenance covers.

In this guide

  1. 01
    Know what conformance means
    The short answerThe requirements
  2. 02
    See how it lapses
    The audit snapshotThe four ways
  3. 03
    Keep it from lapsing
    HHS datesActionsMisreadingsLimitsConclusion

Does WCAG conformance last after an audit?

No, not by itself. WCAG conformance holds while the pages stay as tested. When a page changes, the audit result no longer describes it, and a site with few edits lapses slowly.

What WCAG conformance requires, level by level

W3C’s guidance on conformance says “three levels of conformance are defined: A (lowest), AA, and AAA (highest).” One of these WCAG conformance levels must be “met in full.”

ALowest
AAAll A and AA criteria
AAAHighest

For the AA conformance rating set out in WCAG, “the web page satisfies all the Level A and Level AA success criteria” or “a Level AA conforming alternate version is provided.” Four further requirements apply:

Full pagesConformance “is for full web page(s) only, and cannot be achieved if part of a web page is excluded.”
Complete processesFor a series of pages presenting a process, “all web pages in the process conform at the specified level or better.”
Accessibility-supported uses“Only accessibility-supported ways of using technologies are relied upon to satisfy the success criteria.”
Non-interferenceTechnologies used in a way that is not accessibility supported must not “block the ability of users to access the rest of the page.”

This is guidance for WCAG 2.2, not the normative text, and the HHS rule names 2.1. For the standards themselves, read WCAG standards and conformance levels explained.

Why an accessibility audit is a dated snapshot

WCAG-EM, W3C’s evaluation method, requires an evaluation statement to carry the “Date of when the evaluation statement was issued.” For a public statement, “the product owner commits to ensuring the validity and maintaining the accuracy of the evaluation statement made.” The owner carries the statement after the audit, not the auditor.

Audits are often sampled

“WCAG 2 conformance claims cannot be made for entire websites based upon the evaluation of a selected sub-set.”

The method also expects repeat evaluation

“Evaluation, according to this methodology, may be re-run after a short period.”

WCAG-EM, W3C

The four ways WCAG conformance lapses

Each route changes something the audit tested.

01

Content edits

A new image without alt text, a PDF link, a low-contrast banner or an unlabeled form field can each break a criterion that passed at audit. W3C’s guidance says “Be sure to monitor any content that can change without approval from the web page author,” because “a page which once conformed may suddenly fail to conform.”

The WebAIM Million, an automated test of home pages only from February 2026, lists the most common detected failures:

Detected failure Home pages
Low contrast 83.9 percent of home pages
Missing alt text 53.1 percent
Missing form labels 51 percent
Empty links 46.3 percent
Empty buttons 30.6 percent

An editor can introduce each of these in a normal edit. That link is our observation, not WebAIM’s, and the figures are a snapshot, not a measure of decay.

02

Plugin and theme updates

A change to a theme template, form plugin or menu plugin changes the whole rendered page, and one update can reach every page. Nothing in WordPress compares the result to the audit. No source we found quantifies updates as a cause, so this is mechanism, not a rate.

03

New embeds and third-party widgets

A video player, chat widget, map, booking tool or donation iframe added later becomes part of the page being judged. Third-party content can also change without anyone at the organization touching it.

04

New pages, forms and processes

A volunteer form or donation flow added after the audit was never tested. Under W3C’s guidance, “all web pages in the process conform at the specified level or better,” so one failing step fails the process.

What this means for an HHS-funded nonprofit

45 CFR 84.84 sets the dates and the standard. A recipient with 15 or more employees must comply from May 11, 2027, and one with fewer than 15 from May 10, 2028.

15 or more employeesMay 11, 2027
Fewer than 15 employeesMay 10, 2028

The standard is to “comply with Level A and Level AA success criteria and conformance requirements specified in WCAG 2.1.” That is 2.1, not 2.2.

Section 84.84(a) covers content provided directly or through contractual, licensing, or other arrangements. We have not read that clause in full, so check with counsel how it applies to an embed such as a donation form you do not host.

The date sets when the standard applies. Whether pages still conform then depends on what changed after the audit.

How to keep WCAG conformance from lapsing

  1. 01

    Name an owner for each of the four routes: content edits, updates, embeds, and new pages and forms.

  2. 02

    Re-check affected pages after a template or plugin change.

  3. 03

    Test a new form or process end to end before it goes live.

  4. 04

    Keep a list of embedded third-party tools.

  5. 05

    Date your evidence: record when pages were last checked and what changed.

Scanners catch part. WebAIM says “Absence of detected errors does not indicate that a page is accessible or conformant.”

Verify it

After the next update or new page, compare it against the audited version of the same page. Any change since the audit date is outside what the audit covered.

Updates are one of the four routes, and someone has to run them. NoDrama’s plans include “WordPress, plugins and themes kept current” and visual regression testing, which compares how pages look. It does not test WCAG criteria. NoDrama does no accessibility work, so audits, remediation and WCAG re-checks stay with you and whoever you hire.

See what NoDrama’s plans include.

The pricing page lists what each plan covers.

See the Three Plans

Common misreadings of WCAG conformance

A passed audit is a permanent certificate.

It is dated and sampled.

A clean scan means conformance.

WebAIM says an absence of detected errors does not make a page conformant.

WCAG 2.2 is what the HHS rule requires.

The rule names WCAG 2.1.

What this does not solve

This guide is not an accessibility audit or remediation, and NoDrama’s plans include no accessibility, WCAG, ADA or Section 508 work. It is not legal advice, and applicability depends on funding and headcount. No source we found measures a decay rate.

A conformance claim describes pages as tested, on a date

WCAG conformance is a dated claim about specific full pages and complete processes. Edits, updates, embeds and new pages each change what was tested, so an owner for each route keeps the claim true after the audit.

Frequently asked questions

Level AA conformance means a page meets all the Level A and Level AA success criteria, or a Level AA conforming alternate version is provided, according to W3C's guidance.
No. An audit produces a dated evaluation statement, and for a public statement WCAG-EM says the product owner commits to maintaining its accuracy.
Conformance is for full web pages, and WCAG-EM says claims for an entire website cannot rest on a selected sub-set. Pages outside the sample are outside what the audit covered.
Under 45 CFR 84.84, a recipient with 15 or more employees must comply from May 11, 2027, and a recipient with fewer than 15 employees from May 10, 2028. Applicability depends on funding and headcount, so confirm it with counsel.
W3C sets no fixed interval, and we found no source that does. WCAG-EM says an evaluation may be re-run after a short period, so re-checking after a change in any of the four routes is a reasonable trigger.
Written byShashank AyyarCo-Founder

Shashank co-founded NoDrama and is co-founder of Pangolin Marketing. He has spent eighteen years as a consultant and head of marketing to startups and growth-stage companies, work that centred on positioning and demand generation. He writes about positioning, buyer trust, and how businesses should evaluate whoever maintains their site.

Written byPartha Biswas

Someone Has to Run the Updates

Get Started
Cancel anytime
Yearly runs to the end of the paid year
Real team behind every plan