SEO and content marketing specialist who started working in the field in 2011. I love all things content, search engines, web accessibility, design, tech, and AI.
On April 20, 2026, four days before public universities were due to comply, the Department of Justice pushed the ADA Title II web accessibility deadline back by one year.
Campus-scale WCAG monitoring scans every college subdomain, PDF, and form against WCAG 2.1 AA. It runs on the academic calendar, weekly in the weeks when once-a-term editors publish syllabi and readings. It reports open failures college by college, each with a named owner, against the new compliance date.
Larger public entities now have until April 26, 2027, and smaller jurisdictions and special districts until April 26, 2028. If you run the web or accessibility office for a public college, that leaves this fall term and next spring to get every college there.
Summary
- The DOJ pushed public colleges’ ADA Title II web accessibility deadline to April 26, 2027 for larger jurisdictions and April 26, 2028 for smaller ones, while the WCAG 2.1 AA standard itself remains unchanged.
- Title II coverage extends beyond HTML pages to PDFs, slide decks, and online forms, so scans that stop at HTML pages understate a campus’s real accessibility gaps.
- Monitoring should run on the academic calendar, with weekly scans during the first month of each term when editors upload syllabi, slides, and reading materials.
- Content posted after the compliance date counts as new content and must meet WCAG 2.1 AA regardless of any extension.
One campus runs many websites
A public college website is a cluster of sites. Each college and department often runs its own subdomain, its own CMS instance, and its own editors. Campus monitoring starts with a map that ties every subdomain and URL path to a college and a named owner.
The map comes before any purchase. For a working example from a public university, read how the University of Texas at Dallas manages accessibility.
List every subdomain and path, assign each to a college or administrative unit, and put one owner’s name beside it. The subdomain-to-college map also routes each fix to its owner, and it becomes the grouping key for every report you send this year.
PDFs and forms count as much as pages
The Title II rule reaches past HTML pages to the documents and forms students use. Course PDFs, slide decks, and online applications all sit within the content a public college must make accessible, so a campus monitor has to open documents and test form fields.
UIC’s IT guidance lists syllabi, lecture slides, PDFs, and readings among the course materials public universities must make accessible. The rule carves out some archived content and preexisting documents; check ADA.gov’s fact sheet for the exact conditions before you exclude a folder from scans.
Documents often fail on structure: missing tags, a broken reading order, images with no text alternative. Our guide to tagging and reading order in accessible PDFs covers the fixes. Forms fall under WCAG Guideline 3.3, which sets rules for labels and input assistance on forms.
During any accessibility tool trial, feed the tool a real reading PDF and a live registration form. A tool worth keeping flags the untagged document and the unlabeled field.
Run scans on the academic calendar
The start of each term, when syllabi, slides, and reading PDFs land on department sites, is when campus monitoring has to catch errors and hand each editor their fixes.
All of those uploads count as new content. ADA.gov’s guide to the Title II rule says a presentation posted after the compliance date would not fall under the exception and would probably have to meet WCAG 2.1, Level AA.
Schedule scans weekly through the first month of each term, and at publish time where your CMS allows it. Send each alert to the page’s owner with a one-page fix guide built from the most common accessibility failures:
- Alt text on images
- Heading order
- Descriptive link text
- Tagged PDFs with a logical reading order
- Labels on form fields
For a one-page check before anything goes live, give editors a free accessibility checker. Editors get the guide in the alert, the week they publish.
Each college gets its own readiness trend
Report open WCAG 2.1 AA failures per college, with a named owner, the change since last month, and the monthly reduction needed to reach zero by the compliance date. A snapshot shows where a college stands today, while a trend shows whether it will reach the standard by the deadline.
From the date of this blog’s publishing, that leaves about six monthly reports, and each one adds a point to a line that has to reach zero open AA failures by late April 2027.
Set each monthly report to show three numbers per college: open issues, the change since last month, and the required pace. Divide a college’s open failures by the months left before the compliance date, and that figure becomes the reduction its owner has to beat in every report that follows.
Title II’s extra year is for monitoring
Section 504 now carries its own date. On May 7, 2026, HHS extended its Section 504 rule’s WCAG 2.1 AA deadline for funding recipients with 15 or more employees to May 11, 2027, according to the HHS press release. Public and private colleges with HHS grants answer to both laws, which name the same standard on dates about two weeks apart.
| Instrument | Who it covers | Compliance date |
| ADA Title II (DOJ rule) | Public colleges that are part of a state government, or of a local jurisdiction of 50,000 or more | April 26, 2027 |
| ADA Title II (DOJ rule) | Public colleges in smaller jurisdictions and special districts | April 26, 2028 |
| Section 504 (HHS rule) | Recipients of HHS funding with 15 or more employees, public or private | May 11, 2027 |
The University of Maryland’s guidance specifies WCAG 2.1 Level A and Level AA success criteria. Tag each finding with the compliance date in the table above that applies to your institution.
Four tests for any campus monitor
Test every monitor against four campus requirements:
- subdomain crawling,
- PDF and form checks,
- reporting by college, and
- a WCAG 2.1 AA view.
The first three follow from how a college publishes. The fourth decides whether each college’s count matches Title II requirements.
W3C’s directory of web accessibility evaluation tools gives you names. Only a trial on your own subdomains shows how a tool behaves.
During a trial, ask each tool four questions:
- Crawling: Does it follow links onto department subdomains and separate CMS instances?
- Documents and forms: Does it flag the untagged PDF and the unlabeled field you fed it?
- Reporting: Can it group findings by your subdomain-to-college map?
- Standard: Does it report the Title II standard on its own?
Then trial each tool on two colleges, one strong and one struggling, with their PDFs included. Run the trial in January, when the spring syllabi land. It’s the last term start before the compliance date, and the last rehearsal against the standard.
Frequently asked questions
When is the new ADA Title II web accessibility deadline?
The DOJ pushed the deadline back one year on April 20, 2026. Larger public entities, including most public universities, now have until April 26, 2027. Smaller jurisdictions and special districts have until April 26, 2028. The WCAG 2.1 Level AA standard itself did not change.
Why do subdomain crawls matter for college accessibility scans?
A public college website is actually a cluster of sites, with each college and department often running its own subdomain and CMS instance. A crawl seeded only at the main domain misses most of them, so campus monitoring must start with a map tying every subdomain and URL path to a named owner.
Do course PDFs and syllabi fall under Title II rules?
Yes. Course PDFs, slide decks, and online applications sit within content public colleges must make accessible. UIC’s IT guidance lists syllabi, lecture slides, PDFs, and readings among required materials. Most live on department subdomains, so scans scoped only to the main domain miss them entirely.
How does Section 504 differ from Title II for colleges?
Section 504 covers HHS funding recipients with 15 or more employees, public or private, with a WCAG 2.1 AA deadline of May 11, 2027. Title II covers public colleges with deadlines of April 26, 2027 or 2028. Both name the same standard roughly two weeks apart.
What questions should a campus test before choosing a monitoring tool?
Ask whether it crawls onto department subdomains and separate CMS instances, flags untagged PDFs and unlabeled form fields, groups findings by the subdomain-to-college map, and reports against WCAG 2.1 AA specifically rather than blending in WCAG 2.2 criteria that inflate or miss required failures.
