For years, public agencies knew their websites needed to be accessible to people with disabilities, but the exact standard wasn’t spelled out in regulation. That changed when the U.S. Department of Justice issued its final rule under Title II of the Americans with Disabilities Act, which adopts a specific technical standard for state and local government websites and mobile apps.
This article is a practical overview, not legal advice. Every agency should confirm its obligations and deadlines with its own legal counsel and current DOJ guidance.
What the rule requires
The DOJ’s Title II rule, published in April 2024, sets WCAG 2.1 Level AA as the technical standard for web content and mobile apps provided by state and local governments. That includes cities, counties, special districts, public transit agencies, public colleges, libraries and other public entities.
The rule gave public entities time to comply based on size: larger entities (populations of 50,000 or more) had an earlier compliance date than smaller entities and special districts. Check the DOJ’s ADA.gov resources for the dates and any updates that apply to your organization.
What WCAG 2.1 AA means in plain language
WCAG (Web Content Accessibility Guidelines) is organized around four principles. Content should be:
- Perceivable: people can see or hear it, or access it another way. Images need text alternatives, videos need captions, and text needs enough color contrast.
- Operable: people can use it with a keyboard, screen reader or other assistive technology, without time limits or flashing content getting in the way.
- Understandable: pages are predictable, forms have clear labels and errors are explained.
- Robust: content works reliably with current and future assistive technologies.
The most common problems we find
- Missing or meaningless image alt text (“image001.jpg”)
- Low color contrast between text and background
- Forms without proper labels or with unclear error messages
- Keyboard traps and menus that only work with a mouse
- Scanned PDFs that screen readers can’t read
- Videos without captions and meetings posted without transcripts
- Headings used for styling instead of structure, which confuses screen readers
- Links that say “click here” with no context
A practical path to compliance
1. Audit what you have
Run automated scans to catch obvious issues, then do manual testing with a keyboard and screen reader. Automated tools typically catch only a portion of accessibility problems, so manual review matters.
2. Prioritize by impact
Start with the pages and services residents rely on most: paying bills, applying for permits, finding meeting agendas, reporting issues, and emergency information.
3. Fix the templates first
Many issues live in your site’s theme, menus and forms. Fixing a template fixes every page that uses it.
4. Tackle documents
Convert important PDFs to accessible web pages or properly tagged accessible PDFs. Establish a process so new documents are accessible before they’re posted.
5. Train your content editors
Accessibility isn’t a one-time project. Staff who post news, agendas and documents need simple guidelines for alt text, headings, links and captions.
6. Publish an accessibility statement
Explain your commitment, the standard you follow, and how residents can report barriers and request content in an alternative format.
Beyond compliance
Accessible websites are easier for everyone to use, including older residents, people on mobile devices and people with temporary injuries. They also tend to perform better in search, because the structure that helps screen readers also helps search engines understand your content.
Frequently asked questions
Do third-party tools and vendor platforms count?
Content and services provided through contractors and vendors on your behalf are generally part of your obligations. Ask vendors for their accessibility documentation and include accessibility requirements in contracts.
Is an accessibility overlay widget enough?
Overlay widgets don’t fix underlying code and content issues, and many accessibility experts and users with disabilities report problems with them. They’re not a substitute for an accessible site.
How long does remediation take?
It depends on the size of your site and number of documents. Template fixes can happen quickly; large document libraries take longer.
Get an accessibility review
A Treehouse Group designs, audits and remediates websites for public agencies, special districts and chambers of commerce. Learn more about our government and public sector services or request a review.
