Accessibility
Sites we build aim at WCAG 2.2 Level AA. In practice that means text you can read against its background, every link and form usable from the keyboard, labels on form fields, error messages that say what went wrong, and a layout that still works on a phone at a large text size. We test those things by hand before launch. We do not stamp a certificate on a site, and an automated score is a starting point, not the result.
The legal standard for public entities
The Department of Justice rule under Title II of the Americans with Disabilities Act sets WCAG 2.1 Level AA as the technical standard for the web content and mobile apps of state and local governments. According to the rule page on ada.gov, an interim final rule published April 20, 2026 set the compliance dates at April 26, 2027 for entities with a population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments.
Whether that rule, or another law, applies to your organization is a legal question for your counsel. We do not give that advice. 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.
On your site
The check is part of the build, not a report at the end. Editors get a short note on headings, link text, and image descriptions, because the site keeps changing after launch. PDFs that people still need are part of the review. A one-time review of a site we did not build can be scoped on its own. It is not part of every care month unless the agreement says so.
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.