Skip to main content
Base22

Analytics cookies

We’d like to use Google Analytics cookies to learn how this site is used and improve it. Nothing is set unless you accept, and there are no advertising cookies. Change your mind anytime under “Cookie settings” in the footer. Privacy policy

Title II & Section 504 readiness

ADA Title II requires state and local governments to make their websites and documents, PDFs included, meet WCAG 2.1 AA. We run the program end to end: assess, remediate, certify, and keep it that way.

600+
PDFs remediated to WCAG 2.1 AA in one month

Schematic — client UI under NDA

  • Inventory
  • Remediation queue
  • Certified

Trusted by

  • New Mexico Department of Health
  • State of Ohio

In April 2026 the Department of Justice set the dates. Under ADA Title II, state and local governments must make their web content and electronic documents, PDFs included, conform to WCAG 2.1 AA:

  • April 26, 2027 — public entities serving 50,000 or more people.
  • April 26, 2028 — smaller entities and special districts.

Organizations that receive funding from the US Department of Health and Human Services have a parallel obligation under HHS’s Section 504 rule, with web and document requirements from May 2026.

The work is rarely the website alone. Agencies often hold years of forms, reports and notices as PDFs, and those count too. A readiness program treats the site and the documents as one inventory, with an owner and a date for every item, and ends with evidence you can show.

01Who is in scope

Three dates to plan around.

Title II applies to state and local governments; Section 504 to recipients of HHS funding.

  • Public entities serving 50,000+ people

    State agencies and larger counties and cities: websites and documents at WCAG 2.1 AA by April 26, 2027.

  • Smaller entities and special districts

    Public entities serving fewer than 50,000 people, and special districts: April 26, 2028.

  • Recipients of HHS funding

    Health and human services organizations funded by HHS: Section 504 web and document requirements from May 2026.

02What we deliver

A program, not a scan.

We run readiness as an engagement with a start, a finish and evidence at the end, sized to your inventory and your date.

  • An inventory you can plan with

    Every site, application and document, tested against WCAG 2.1 AA, with each issue ranked by who it blocks and how often people meet it.

  • Fixes where they multiply

    Templates and components fixed once, so the fix reaches every page built from them.

  • Documents at volume

    PDF remediation on the platform we built for it: 600+ PDFs to WCAG 2.1 AA in one month for the New Mexico Department of Health.

  • Certification and an audit trail

    For each page and document: what was checked, what was fixed and who signed off.

  • Compliance that holds

    Checks on every change and a path for new documents, so what you publish next year meets the standard too.

  • Authors who can own it

    Training for the people who publish pages and documents, so compliance does not depend on us.

03How an engagement runs

From inventory to certified, before your date.

  1. Assess

    Inventory and test your sites, applications and documents; agree the order of work with your team.

  2. Remediate

    Fix templates, components and content, and remediate documents, highest-traffic first.

    AI: self-hosted models draft alt text; a person approves every description.

  3. Certify

    Retest, and certify each page and document only when every check is resolved.

  4. Keep

    Automated checks on every change, and trained authors for what comes next.

04

Related work

Bring us the hard problem.

Book 30 minutes with the senior people who would do the work.

Or write to info@base22.com