Meeting these rules is about ensuring everyone has access and opportunity — and it’s also about avoiding fines and legal exposure that can blow up a technology budget.
This post clarifies what changed, what’s due when, what’s at stake, and the practical steps to get compliant in time.
“Accessibility rules and their requirements are becoming front of mind … and we want to be on that journey with you,” said Granicus’ Katie Jones during a recent webinar titled, “Web and mobile accessibility laws are changing — is your government ready?”
The accessibility law landscape: What’s changed
The U.S. Department of Justice (DOJ) finalized a Title II rule that requires state and local governments’ web content and mobile apps to conform to WCAG 2.1 Level AA. That standard now anchors federal compliance expectations across digital properties.
States are also moving, often layering additional obligations or faster timelines. Colorado’s law, for example, required conformance to state rules by July 1, 2025 (following a grace period), and it applies to state and local governments and their vendors.
Bottom line: Whether you’re looking at federal Title II or state requirements, WCAG 2.1 AA is the common baseline agencies should plan to meet.
Critical compliance deadlines you must know
Federal ADA (Title II) compliance dates:
- April 24, 2026: Jurisdictions serving more than 50,000 residents.
- April 26, 2027: Jurisdictions serving fewer than 50,000 residents and most special districts.
Practical steps to avoid financial penalties that could devastate your budget
Financial penalties can escalate quickly. Under the ADA, DOJ raised the maximum civil penalty for a first violation to $75,000, with $150,000 for subsequent violations.
States add their own exposure: California’s Unruh Civil Rights Act allows at least $4,000 per violation in statutory damages in private suits, plus attorney’s fees. On top of fines and damages, agencies should anticipate legal fees and remediation costs that often exceed the initial penalty. As Jones cautioned during the webinar, penalties can be assessed per violation, and actions can stack: “It’s quite expensive to have this type of error come up.”
Getting ready means treating accessibility as an ongoing operational discipline. Start by naming an accessibility coordinator who can align leadership, IT, content owners, and vendors, then run a baseline audit of your websites and mobile experiences against WCAG 2.1 AA.
Once aligned, formalize an accessibility review policy and build it into content and product workflows. Then, train every staffer who creates, approves, or publishes content on the process, including how to handle PDFs and when to provide accessible HTML alternatives.
Ensure continuity with recurring audits, resident feedback channels, and VPAT reviews for third-party tools, an expectation some states make explicit.
As Jones put it, there’s no such thing as being “100% accessible” forever, as browsers, operating systems, and rules change. So, treat this as a continuous assessment.
Deadlines are set, and the stakes are high. Meeting WCAG 2.1 AA protects residents’ rights and safeguards taxpayer resources by avoiding fines, lawsuits, and emergency rework. Prepare now, document progress, and build accessibility into daily operations so you’re ready well before the clock runs out.
“We’re here to help modernize government and empower you all,” Jones said. “Let’s build a cross-functional plan that sticks.”
To learn more about the tactics and strategies that can help your agency stay compliant ahead of upcoming deadlines, watch the full online session here.
