Accessibility
The web accessibility deadline for public entities in plain English, what WCAG AA asks for, how LSCalado audits and fixes a site, and the standard this site is built to.
In 2024 the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act. The websites and mobile apps of state and local governments must meet WCAG 2.1 Level AA, a specific technical standard. This page says who it covers, when it applies, what the standard asks for, and how we handle it. It is general information, not legal advice. The rule itself is on ada.gov.
Two deadlines, both pushed back a year
An interim final rule published April 20, 2026 extended both compliance dates by one year. The standard stayed the same.
- April 26, 2027 for public entities with a population of 50,000 or more. The date was originally April 2026. If your site needs work, this budget cycle is the one to plan it in.
- April 26, 2028 for public entities under 50,000 and all special district governments. The date was originally April 2027.
Does this apply to us?
If your entity is covered by Title II of the ADA, almost certainly yes. That includes cities, towns, and counties; special districts such as water, parks, transit, and housing authorities; public schools, school districts, and community colleges; courts and other state and local public entities. It covers web content and mobile apps, including services a vendor runs on your behalf. Whether the rule, or another law, applies to your organization is a question for your counsel. Private associations, nonprofits, and businesses are not covered by Title II. Their members and donors may still need the same standard.
What WCAG 2.1 AA asks for
The standard has fifty success criteria. In practice they come down to six things.
- Every menu, form, and button can be reached and operated from the keyboard alone.
- Text is dark enough against its background to read in sunlight, on a cheap screen, and with low vision. The standard sets a measured ratio: 4.5 to 1 for normal text.
- Headings, labels, and landmarks are structured so a screen reader can announce what each thing is.
- Required fields, error messages, and instructions are announced to every user. Someone who cannot see the red outline still finds out what went wrong.
- Videos have captions, images have descriptions, and nothing important lives only inside a photo of a flyer.
- Documents count too. A PDF agenda packet is web content. The rule lists five exceptions: archived web content, preexisting conventional electronic documents, content posted by a third party, individualized documents that are password-protected, and preexisting social media posts. Each is narrow, and documents people currently need must be accessible.
Sites we build aim at WCAG 2.2 Level AA. The W3C page What's New in WCAG 2.2 says the 2.1 success criteria are essentially the same in 2.2, except 4.1.1 Parsing, which was removed as obsolete, and that 2.2 adds nine criteria. Building to 2.2 AA therefore works toward 2.1 AA as well.
Audit, prioritize, fix, keep
An automated scan is a starting point. Keyboard and screen reader checks find what the scan misses. Then comes a plan, the fixes, and the upkeep.
- We audit the site: automated scanning plus the part tools cannot do, which is manual keyboard passes, screen reader testing, and a review of your highest-traffic tasks and documents.
- We write a remediation plan ordered by impact on the people who use the site and by legal exposure. You see what to fix first, what can wait, and what falls under an exception.
- We fix or rebuild. Some sites retrofit cleanly. Some are faster and cheaper to rebuild accessible from the ground up. We tell you which yours is and put a fixed price on each path.
- We keep it that way, with notes for editors on headings, link text, and image descriptions, plus automated checks, so next month's news post does not bring the problems back.
On a site we build, the check is part of the build, and we test by hand before launch. We do not certify sites, and we do not treat an automated score as the result. A review of a site we did not build is scoped on its own; it is not part of a care month unless the plan says so. The security, accessibility, and performance page describes the service.
Want to know where your site stands?
Send us the address through the contact form. You get back a short written note: where the site stands against WCAG 2.1 AA, what we would fix first, and roughly what the path to your deadline looks like. No charge, no meeting, no obligation. The note is a first look, not the full audit described above.
This website
This site aims at the same standard. If something on it blocks you, write to contact@lscalado.com and name the page and the problem.