Built for Virginia counties, cities, towns, and special districts
Meet your ADA Title II web accessibility deadline.
The Department of Justice requires state and local government websites, mobile apps, and online documents to meet WCAG 2.1 AA. Localities serving 50,000 or more people must comply by April 26, 2027. Smaller localities and special districts have until April 26, 2028.
The rule, in plain English
Title II of the Americans with Disabilities Act already required state and local governments to make their services accessible. In April 2024, the Department of Justice published a final rule that sets a specific technical standard, WCAG 2.1 Level AA, for websites, mobile apps, and web content, including PDFs and forms posted online.
The rule covers web content and mobile apps a public entity provides or makes available, directly or through contractual, licensing, or other arrangements. On April 20, 2026, DOJ published an Interim Final Rule extending the compliance dates. The current deadlines are in 28 CFR 35.200.
April 26, 2027
A public entity, other than a special district government, with a total population of 50,000 or more.
April 26, 2028
A public entity with a total population of less than 50,000, or any special district government.
Starting now still matters. Audits, PDF remediation, and staff training take time, and an early start lets your team do the work carefully.
Sources: ADA.gov fact sheet on the web rule and Federal Register, April 20, 2026 extension.
What we do
Accessibility audit
Review of your public website and online documents, including PDFs and forms, against WCAG 2.1 AA.
Prioritized fix plan
A clear, ordered plan so staff know what to tackle first.
Remediation help
Hands-on guidance for your web vendor or in-house team as issues are fixed.
Accessibility statement
A public accessibility statement and a feedback process residents can use.
Staff training
Practical training so new pages, PDFs, and forms stay accessible.
Ongoing monitoring
Regular checks after the initial work so problems are caught early.
How it works
Step 1: Request a website review
Tell us about your locality, website, and document library.
Step 2: Receive your findings
Get a plain-language findings report and a prioritized plan.
Step 3: Fix, train, and monitor
Work through fixes, train staff, and keep content accessible over time.
About Mike Arthur
Mike Arthur is the founder of 2080compliance. He is a former county government chief data officer, holds the CIPP/US credential, and has more than 10 years of experience in data privacy and data management.
He works with Virginia localities that need a practical path to Title II web accessibility.
Frequently asked questions
A public entity, other than a special district government, with a total population of 50,000 or more must comply by April 26, 2027. A public entity with a total population of less than 50,000, or any special district government, must comply by April 26, 2028. Special districts use the later date. Population is generally based on total population as described in the rule (Federal Register).
Yes. Web content the locality provides or makes available, including documents posted online such as PDFs and forms, is in scope.
The rule requires the web content and mobile apps themselves to meet WCAG 2.1 AA. A third-party overlay or toolbar, by itself, is generally not a substitute for fixing the underlying site and documents.
No. Finding issues, fixing templates, remediating PDFs, and training staff takes time. Starting with a review now leaves room to do the work carefully.
It depends on the size of your site and document library. Request a website review and we will discuss scope with you.
Request a website review
Clerks, IT staff, managers, and ADA coordinators are welcome to get in touch.