ADA Title II Deadline Lint (WCAG 2.1 AA)

Flags the ADA Title II and HHS Section 504 deadlines that both agencies reset in 2026, and the WCAG 2.1 Level AA failures your source code can actually show.

Get the complete version $29

This page is the working piece. The full pack has everything below.

Flags the ADA Title II and HHS Section 504 deadlines that both agencies reset in 2026, and the WCAG 2.1 Level AA failures your source code can actually show.

A hybrid WCAG audit (automated plus manual sampling) is quoted at $1,500-$8,000, and a VPAT/ACR write-up at about $350.

Buy the full version — $29
Want the full version?
Enter your email and we send the download link.
ENDEJAESPT

Find a tool

· ReadyStack

Worked example

Real numbers from this tool, line by line.

Five lines that used to be compliant: what DOJ and HHS changed in 2026

Five lines in a US county accessibility statement now fail the ADA Title II rule, and every free linter in the editor passes all five.

Here is what changed while nobody was looking. On 2026-04-16 the Department of Justice signed an interim final rule, effective on publication on 2026-04-20, that rewrote the compliance dates in 28 CFR 35.200(b). Public entities with a population of 50,000 or more moved from April 24, 2026 to April 26, 2027. Smaller entities and special districts moved from April 26, 2027 to April 26, 2028. Three weeks later, on 2026-05-07, HHS did the same to the Section 504 web rule at 45 CFR 84.84: recipients with 15 or more employees moved from May 11, 2026 to May 11, 2027, and recipients under 15 employees moved from May 10, 2027 to May 10, 2028.

Only the timing changed. The technical standard for all four is still WCAG 2.1 Level AA - not 2.0, not Level A, and not Section 508, which governs federal agencies rather than a county.

That combination is the trap. Every accessibility statement, roadmap, procurement answer and README written in 2025 names dates that are now wrong. Every model trained before May 2026 will confidently repeat them. And the tools that check your code - eslint-plugin-jsx-a11y, Lighthouse, the a11y rules in your CI - read markup semantics. They do not read regulation. A statement that promises April 24, 2026, cites Section 508 as the governing standard, and calls the site fully ADA compliant passes all of them, and those are precisely the three sentences a demand letter quotes back.

So here are the five lines, and what each one should say instead.

...will conform by April 24, 2026. becomes ...will conform by April 26, 2027. conforms to WCAG 2.0 Level AA becomes conforms to WCAG 2.1 Level AA. fully ADA compliant becomes a dated statement naming the standard you tested against and the gaps you know about. <img src="seal.png"> becomes <img src="seal.png" alt="City seal"> - SC 1.1.1, Level A. And <div onclick="pay()"> becomes <button onclick="pay()"> - SC 2.1.1 Keyboard, Level A, because a div takes no focus and announces no role.

ADA Title II Deadline Lint is a VS Code extension that runs 26 rules of exactly that kind over the file you have open: the superseded dates, the mis-cited standards, the unverifiable conformance claims, the WCAG 2.1 Level AA failures a source line can actually prove, and the two scope questions in 28 CFR 35.201 that decide whether a linked PDF or a third-party embed is even in scope. Every finding comes back with its success criterion or its CFR section attached, so you can paste it into the remediation ticket unedited.

The whole rule set is free on the file you have open, with no watermark and no usage limit. Paste a statement into the free web version and you get the same 26 rules in the browser. What a licence key adds is a different job: the whole repository instead of one file, and a dated CSV, JSON or HTML evidence file you can hand to counsel or procurement.

You have 230 days until April 26, 2027 and 245 until May 11, 2027. The stale date is a one-line fix. Finding it is the part nobody has automated.

15 seconds — what it actually does

Questions people ask

What does ADA Title II Deadline Lint actually do?

It reads the file you have open and flags two things. First, superseded compliance dates: DOJ moved the ADA Title II web deadline to April 26, 2027 on 2026-04-20, and HHS moved the Section 504 deadline to May 11, 2027 on 2026-05-07, so any document still naming the old dates is wrong. Second, WCAG 2.1 Level AA failures a single source line can prove, each tagged with its success criterion.

Who is this for?

Developers and agencies shipping web code for US state and local government - cities, counties, school districts, transit authorities, public universities - and for health organizations that receive HHS funding. Those two groups are the ones covered by 28 CFR 35.200 and 45 CFR 84.84, which is where the dated deadlines and the WCAG 2.1 Level AA standard come from.

Why will a free accessibility linter not cover this?

Free linters check markup semantics. They do not track regulation. eslint-plugin-jsx-a11y and Lighthouse will happily pass an accessibility statement that still promises April 24, 2026, cites Section 508 as the governing standard for a county website, or claims the site is fully ADA compliant. Those three sentences are the ones that get quoted back in a demand letter, and no generic linter reads them.

What is free and what needs a licence key?

Every rule runs for free on the file you have open or on the lines you select, with nothing held back, no watermark and no usage limit. A licence key adds a different job rather than more of the same one: scanning the whole repository, exporting a dated CSV, JSON or HTML evidence file, rewriting the superseded dates in place, and writing JSON for a pipeline step.

How does the price compare with paying somebody?

A hybrid WCAG audit that mixes automated scanning with manual sampling is quoted at $1,500-$8,000, and adding a VPAT/ACR write-up runs about $350 on top. This is $29 once, with a 7-day full refund. It does not replace the audit you will still need before you certify - it removes the findings an auditor would have billed you to discover.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.