Web Accessibility, WCAG, and the DOJ Deadlines: What Your Organization Needs to Know
Accessibility is getting worse, and the law is catching up
The web failed more people in 2026 than it did the year before. WebAIM's annual scan of the top one million home pages found detectable WCAG 2 failures on 95.9% of them, up from 94.8% in 2025, with an average of 56 errors per page (WebAIM Million 2026, summarized by JSTOR). The same six problems have topped the list for seven years running: low-contrast text, images without alt text, unlabeled form fields, empty links, empty buttons, and pages with no declared language (Priority Pixels).
Those errors land on real people. A screen reader cannot describe an image that has no text description, and a keyboard user cannot activate a button that has no name. For a county resident trying to renew a license, request a ballot, or look up clinic hours, an inaccessible page is a closed door.
For the organizations that run those pages, the risk has shifted from reputational to regulatory. The Department of Justice and the Department of Health and Human Services have both written WCAG into federal rules with hard compliance dates, and the first of those dates is now six months away.
The DOJ rule and its deadlines
On April 24, 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act that, for the first time, names a specific technical standard for state and local government websites and mobile apps: WCAG 2.1 Level AA (ADA.gov fact sheet). The rule covers every public entity, from state agencies and courts to public universities, libraries, transit systems, and school districts. It also reaches content that a vendor builds or hosts on a government's behalf. If a web design firm maintains a county's parks page, that page must still conform.
On April 20, 2026, four days before the first deadline, DOJ published an interim final rule pushing both dates back one year (Federal Register, 91 FR 20902). The current dates:
| Covered entity | Compliance date |
|---|---|
| State and local governments serving 50,000 or more people | April 26, 2027 |
| Governments serving fewer than 50,000 people, and all special district governments | April 26, 2028 |
The extension changed only the dates. The WCAG 2.1 AA standard, the exceptions, and the underlying Title II obligation to provide effective communication are all unchanged, and DOJ said as much in the rule (JD Supra). The exceptions are narrow: archived content kept in a designated archive and never updated, PDFs and office documents posted before the compliance date and not used to access a current service, individualized password-protected documents, content posted by uncontrolled third parties, and pre-deadline social media posts. A 2020 PDF license application that residents still use to apply does not qualify.
HHS followed the same pattern. Its May 2024 Section 504 rule holds recipients of HHS funding, including hospitals and clinics that accept Medicare or Medicaid, to the same WCAG 2.1 AA standard. On May 7, 2026, HHS extended those dates by a year as well: May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones (Federal Register).
How WCAG, Section 508, and the ADA fit together
WCAG is the measuring stick. Every U.S. law in this space points to it rather than writing its own technical rules. The Web Content Accessibility Guidelines are published by the W3C and organized into three conformance levels (A, AA, AAA) under four principles: content must be perceivable, operable, understandable, and robust. Level AA is the target that regulators and courts use. WCAG 2.1 came out in 2018 and WCAG 2.2 in October 2023; each version adds criteria on top of the last without removing any, so a site that meets 2.2 AA also meets 2.1 AA and 2.0 AA.
The laws differ in who they cover and which WCAG version they name.
| Law or rule | Who it covers | Technical standard | Status |
|---|---|---|---|
| Section 508 of the Rehabilitation Act (Access Board) | Federal agencies and the ICT they buy, build, or use; contractors must show conformance | WCAG 2.0 AA, incorporated by reference in the 2017 refresh | In force since January 2018 |
| ADA Title II, 2024 DOJ rule (ADA.gov) | State and local governments, public schools and universities, and vendors acting for them | WCAG 2.1 AA | April 26, 2027 and April 26, 2028 |
| Section 504, 2024 HHS rule (Federal Register) | Recipients of HHS funding, including hospitals, clinics, and many nonprofits | WCAG 2.1 AA | May 11, 2027 and May 10, 2028 |
| ADA Title III | Private businesses and nonprofits open to the public | No regulation names a standard; courts and settlements use WCAG 2.1 or 2.2 AA | Enforced through private lawsuits now |
Title III has no deadline and the most litigation. Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, up 27% from 2024 (Level Access). Abroad, the European Accessibility Act took effect in June 2025 on the EN 301 549 standard, which also incorporates WCAG. An organization that builds to WCAG 2.2 AA covers all of these obligations at once.
Who is on the hook
Most organizations fall under more than one of these laws, and the overlap is where surprises happen.
Federal agencies and their contractors. Section 508 applies to any ICT an agency develops, procures, maintains, or uses, and the standards sit inside the Federal Acquisition Regulation (Access Board). A contractor delivering a website or a PDF to a federal client is delivering something the agency must certify as conformant, and solicitations routinely ask for an Accessibility Conformance Report (ACR) up front.
State and local governments. The DOJ rule reaches every public entity and every vendor acting on its behalf. A city that pays a private company to run its parking app is responsible for that app's conformance (ADA.gov). Procurement language and vendor contracts need to say WCAG 2.1 AA explicitly, with a testing obligation attached.
Nonprofits. A nonprofit open to the public is a Title III "public accommodation" and faces the same private-lawsuit exposure as a retailer. A nonprofit that receives HHS funding, or that delivers services under contract to a state agency, picks up the HHS Section 504 rule or the Title II rule as well, with the deadlines above. Grant agreements from other federal agencies often carry their own accessibility clauses.
Member associations. The public site is a Title III accommodation. The member portal, event registration, and continuing-education platform are usually third-party products, and courts have not treated "our vendor built it" as a defense.
Drupal sites. Drupal has treated accessibility as a release-blocking requirement since Drupal 7, and core now develops to WCAG 2.2 AA for both the public site and the editorial interface (Drupal.org). That is a strong starting point and only a starting point. Contributed modules skip the core accessibility gate, a custom theme can undo core's work in one stylesheet, and editors add images without alt text every day. A Drupal site stays accessible because the team running it keeps it that way.
How to find out where you stand
Start with an automated scan, and treat the result as a floor rather than a verdict. Free tools such as WebAIM's WAVE browser extension, Deque's axe DevTools, and the Lighthouse audit built into Chrome will flag the six most common failures in minutes. They cannot tell you whether a link's text makes sense, whether a form's error message is understandable, or whether a custom menu works with a screen reader, and those judgment calls are a large share of WCAG. The federal government's own guidance says to combine automated tools with manual testing rather than rely on either alone (Digital.gov).
The manual pass does not need a specialist. Put the mouse away and move through your top pages with Tab, Shift+Tab, Enter, and the arrow keys; every control should be reachable and the focused element always visible. Zoom to 200% and check that nothing disappears. Turn on the screen reader that ships with your operating system and listen to your home page and a form. Open your most-downloaded PDFs and check whether they are tagged documents or scanned pictures of text.
For anything that has to stand up to a federal buyer or an auditor, use the process the government uses. The DHS Trusted Tester conformance test process is a code-inspection method aligned to the Access Board's ICT Testing Baseline, and agencies that adopt it accept results only from certified testers (Section508.gov). A Trusted Tester report, or an audit from a firm that follows the same baseline, is what turns "we think we're compliant" into evidence.
Then look at the processes around the site: who writes alt text, who checks PDFs before posting, what accessibility language is in vendor contracts, and whether anyone has tested with assistive technology in the past year. A site that scans clean today with none of those answers will not scan clean next quarter.
What to do if the answer is "not yet"
Six months is enough time to make real progress if the work is sequenced by impact instead of by page.
- Fix the templates first. Contrast, focus indicators, skip links, heading structure, and form labels live in the theme, so one fix there repairs every page. On a Drupal site this usually means auditing the custom theme against Olivero's patterns and reviewing contributed modules that render markup.
- Fix the content people actually use. DOJ's exceptions are built around current use, so the license application, the benefits form, and the event registration page come before the 2015 newsletter archive. Pull analytics for your top 50 URLs and work down the list.
- Deal with documents. Untagged PDFs are the most common failure on government and association sites. Decide which become HTML pages, which get remediated as tagged PDFs, and which move to a designated archive.
- Put accessibility in the contract. Every vendor agreement should require WCAG 2.1 AA at minimum, an ACR on request, and a fix timeline for reported defects. Under the DOJ rule the vendor's shortfall is your shortfall.
- Train the editors. Alt text, descriptive link text, heading order, and accessible document export are habits. Drupal can enforce some of them (required alt text, CKEditor 5 accessibility checks); habits do the rest.
- Publish an accessibility statement with a working contact, and keep records. If a complaint arrives on April 27, 2027, a dated audit, a remediation log, and a vendor paper trail are the difference between a conversation and a consent decree.
One caution. Overlay widgets that add an "accessibility menu" through a single script do not make a site conform to WCAG, and plaintiffs' firms have learned to name them in complaints (Vardot). Spend the money on the template and content work instead.
Where Agileana fits
Agileana has built and maintained Drupal sites for federal agencies for more than a decade, where Section 508 conformance is a contract term rather than an aspiration. That work includes accessibility audits against the ICT Testing Baseline, theme and module remediation, PDF-to-HTML conversion, editor training, and the ACR documentation federal buyers ask for. If you run a government, nonprofit, or association site and want to know where you stand before April 2027, get in touch and we will scope an audit.
Sources
- U.S. Department of Justice, Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments, ADA.gov
- U.S. Department of Justice, Extension of Compliance Dates; Accessibility of Web Information and Services of State and Local Government Entities, 91 FR 20902, April 20, 2026
- U.S. Department of Health and Human Services, Extension of Compliance Dates; Accessibility of Web Content and Mobile Applications of Recipients of Departmental Financial Assistance, Federal Register, May 11, 2026
- Jackson Lewis / JD Supra, DOJ Delays ADA Web Accessibility Compliance Deadlines for Public Employers and Entities, April 2026
- U.S. Access Board, Revised 508 Standards and 255 Guidelines
- GSA, DHS Trusted Tester Process and Certification Program, Section508.gov
- Digital.gov, How to Test Websites for Accessibility
- W3C Web Accessibility Initiative, WCAG 2 Overview
- WebAIM, The WebAIM Million 2026; figures as reported by JSTOR and Priority Pixels
- Level Access, Title III Lawsuits: 10 Big Companies Sued Over Website Accessibility, citing Seyfarth Shaw's 2025 figures
- Drupal Association, Accessibility in Drupal, Drupal.org
- Vardot, How to Meet WCAG 2.2 AA on Drupal: A University Checklist