You Cannot Remediate What You Cannot See
The plan covers the sites you know about
Many public web teams have a Title II plan. It usually covers the main site, admissions or services pages, and a handful of high-traffic properties. That is sensible. It is also incomplete, because the list it starts from is incomplete.
Colleges, departments, labs, and agencies launch sites on their own. Some are a decade old. Nobody in web services provisioned them, and they show up when something breaks.
On April 20, 2026, the Department of Justice extended the Title II web and mobile app compliance dates. State and local government entities with a total population of 50,000 or more now have until April 26, 2027. Entities under 50,000, and every special district government, now have until April 26, 2028. The standard is unchanged: WCAG 2.1 Level AA. Source: the DOJ interim final rule extending the Title II compliance dates (91 FR 20902).
Why the unseen sites carry the risk
The main site gets budget, attention, and regular testing. The unseen sites get none of that. They tend to run older software, use untested themes, and have no current owner. For a public institution, they are very likely still its web content under Title II.
A remediation plan that never sees them cannot fix them. Worse, it can give leadership a false sense that the work is on track.
Inventory before remediation
The order matters:
- Find every site on the domains you own, with platform and owner.
- Score them so you can see where accessibility, security, and update problems cluster.
- Triage: retire, merge, fix, or rebuild each one.
- Remediate the sites that stay, starting with the ones people depend on most.
Skipping step one means every later step is guesswork.
What Accorbis does here
Accorbis is a standalone web governance platform. It gives one dashboard across the WordPress, Drupal, and custom sites an organization already runs. It is not a CMS and not a hosting company.
Accorbis discovers sites across the estate and puts each one in the dashboard with its owner, platform, and status. It runs automated WCAG 2.1 scanning across those sites so you can see where problems concentrate. No CMS migration and no agent installed on the sites. More detail is on the page about how Accorbis works.
What it does not do
An automated scan is not a remediation program. Many WCAG 2.1 success criteria need human judgment, which you can see by reading the WCAG 2.1 specification from the W3C. Accorbis shows you where to look and tracks progress. Fixing code, content, and documents is work your team or your implementation partner does.
A hypothetical: the audit that missed half the estate
Imagine a public university that commissions a thorough accessibility audit of its main site and the ten sites the web team manages. The audit is good. The fixes are made. Months later, a complaint arrives about a continuing education site that a college launched with an outside vendor. It was never in the audit because it was never on the list.
The university did the work it planned. The plan started from the wrong list.
An inventory-first checklist
- List every domain the institution owns, including legacy and vanity domains.
- Run discovery across those domains and record every site found.
- Record platform, owner, and last update for each site.
- Flag sites with no owner for a decision.
- Review accessibility scores across the estate to see where issues cluster.
- Rank sites by audience and risk before assigning remediation work.
- Recheck for new sites every month.
How to rank sites once you can see them
- Required services first: sites people must use to apply, pay, register, or get public information.
- High traffic next: sites with large audiences, even if they are not transactional.
- Low scores on shared themes: fixing a theme used by many sites fixes theme-level issues on every site that uses it.
- No owner and no audience: candidates to retire rather than fix.
What to report to leadership
Leadership needs a short, honest picture: how many sites you found, how many have owners, how many are being retired, and where the highest-priority issues are. Avoid presenting a scan score as proof of conformance. Present it as a signal of where work is needed and whether it is moving.
Frequently asked questions
Is a scan the same as remediation?
No. A scan finds issues a machine can detect and tracks them over time. Remediation fixes them, and manual testing finds what scanning misses.
Do we have to move to a new CMS?
No. Accorbis sits above WordPress, Drupal, and custom sites. They stay where they are.
Does this cover sites our team did not build?
Yes, if discovery finds them on your domains. That is the point of starting with inventory.
Which Title II date applies to us?
It depends on your entity’s total population and type. April 26, 2027 for 50,000 or more; April 26, 2028 for smaller entities and special districts. Confirm with counsel.
How long does discovery take?
It depends on the size of the estate and how many domains are involved. Ask in a working session what discovery looks like for your domains.
Can we start remediation before inventory is complete?
Yes, on the sites you already know are high priority. Just do not treat that list as the whole plan.
What does a working session cover?
We look at your domains and your questions in the Accorbis workspace. No slide deck.
See it against your estate
Schedule a 30-minute working session. We look at your domains, not a slide deck.
