Deadline Approaches to Address the Digital Services Gap

In our ever-growing digital world, most residents, if given the choice, prefer to communicate with the government online through websites and apps. But for millions of people, the government's vast number of digital storefronts is not easily accessible. Worse, they have little choice but to conduct business online or physically visit a government facility.

When we talk about building inclusive communities, the conversation has long focused on physical access: ramps, lifts, accessible parking and tactile paths. These are important. But in a world where citizens increasingly interact with government through websites, online portals and digital services, there is a parallel obligation that many leaders have been slower to address: digital accessibility.

WHY NOW?

The Web Content Accessibility Guidelines, known as WCAG 2.1, are the internationally recognized standard for making digital content accessible to people with disabilities. These guidelines, in turn, have been adopted and are enforceable under Section 508 of the Americans with Disabilities Act. For senior government leaders, understanding and acting on these guidelines is no longer a matter of best practice — it is now a legal obligation, a civic duty and a genuine public trust issue. This made explicit what many agencies had treated as advisory: Accessibility is now an enforceable digital service standard. At this moment, public managers in jurisdictions with over 50,000 residents have until April 24, 2026, to comply; those in smaller jurisdictions have another year. This is no small task.

Public managers must direct their attention toward understanding the common failure points that directly affect residents:

1. Keyboard inaccessibility: Some users cannot use a mouse. If a form, menu or calendar picker only works with a mouse/touch gesture, it fails.
2. Poor contrast and text scaling issues: Low-contrast text, tiny fonts and rigid layouts make content difficult to read for many residents, including older adults.
3. Missing text alternatives: Images, icons, charts and buttons need meaningful alternatives so screen reader users can understand the purpose and content.
4. Inaccessible forms: Forms often fail because fields are unlabeled, errors are vague, instructions are unclear or focus order is broken.
5. Uncaptioned media: Videos without captions (and in many cases transcripts) block access for people who are deaf or hard of hearing.
6. Dynamic content not announced to assistive technology: Modern portals often update content without a page reload; status changes (e.g., “submission successful”) must be conveyed programmatically.

These are not edge cases — they’re now considered mainstream barriers in government digital workflows. It also goes beyond the traditional government website and covers all citizen-facing government apps.

Many agencies assume they are “mostly compliant” because they ran an automated scan for accessibility. Automated tools are valuable, but they catch only part of the problem. Manual testing is still required for keyboard logic, reading order, screen reader behavior, form usability and user flow completion. WCAG conformance is criterion-based and rigorous; partial checks can create false confidence.

Public managers need to treat accessibility as enterprise-wide across digital service delivery, such as:

• Main website and department pages
• Resident portals (utilities, tax, permitting, case management)
• Mobile apps (parking, transit, alerts, inspections)
• PDFs, public notices, forms, agendas and reports
• Third-party and vendor-provided platforms operating on your behalf
  

In practice, legacy PDFs and vendor systems are often the highest risk areas.

WCAG 2.1 is built on four foundational principles, often referred to as the POUR principles. Content must be perceivable, meaning users can access information regardless of how they sense the world. It must be operable, meaning people can navigate and use the interface without relying on a mouse or specific physical abilities. It must be understandable, with clear language, predictable layouts and helpful guidance. And it must be robust, meaning content works reliably with assistive technologies such as screen readers and voice control software.

Within these principles sit dozens of specific technical criteria, each rated at one of three conformance levels: A, AA or AAA. For government organizations, Level AA is the target standard and the one referenced in most accessibility legislation. It is neither the bare minimum nor an aspirational ceiling — it is considered a practical, achievable benchmark that addresses the needs of the vast majority of users with disabilities.

WCAG 2.1 updated the earlier 2.0 standard by introducing 17 new criteria, with particular attention to groups that had been underserved: people with cognitive and learning disabilities, people with low vision and people accessing services on mobile devices. These additions are not minor technical details — they reflect a significant shift in how governments must think about who is trying to reach them and how.

THE COST OF NON-COMPLIANCE

Non-compliance carries real consequences. Government agencies have faced formal complaints, legal challenges and enforceable orders to remediate inaccessible services. Beyond litigation, there is significant reputational risk in being seen to exclude people with disabilities from essential public services — particularly in an era of heightened public scrutiny over government equity and inclusion commitments.

Non-compliance with WCAG 2.1 can trigger consequences in four buckets: legal, financial, operational and reputational. For public government entities, including public colleges and K-12, here’s the practical picture:

1. Legal and enforcement exposure

• For state and local governments (ADA Title II), the Department of Justice’s (DOJ) final rule adopts WCAG 2.1 Level AA as the technical standard for web content and mobile apps, with compliance deadlines tied to entity size (generally April 2026 or April 2027). Missing the deadline increases the risk of DOJ enforcement, complaints and court-ordered remediation.
• For federal agencies (Section 508), accessibility is a legal requirement, and the current 508 standards incorporate WCAG 2.0 AA criteria (not 2.1). Non-compliance can lead to administrative complaints, corrective action requirements and procurement/contract friction.

2. Direct and indirect cost increases

• Costs usually rise when remediation is done under deadline or legal pressure: emergency fixes, outside counsel, accelerated vendor work, re-audits and staff overtime.
• If litigation or settlement occurs, agencies may face mandated timelines, monitoring/reporting obligations and repeated testing — often more expensive than phased, proactive compliance.

3. Service delivery failures

• Inaccessible forms, payment portals, agenda packets, permit systems and emergency information can block residents from essential services.
• That creates higher call-center volume, manual workarounds and slower case processing — exactly the opposite of digital transformation goals.

4. Reputational and trust damage

• Accessibility gaps can undermine public trust, especially when agencies position themselves as “digital-first,” but some users are effectively locked out.
• Public scrutiny often intensifies around high-visibility services (elections info, public safety alerts, benefits and bill pay).

WCAG 2.1 is not an “IT technicality.” It has become a public service design in the digital era. When residents cannot access digital channels, government performance, trust and equity all suffer. When they can, service completion improves, call-center burden drops and confidence in government rises.

Digital storefronts for government services are changing, enabling millions more citizens to enjoy meaningful access. The leadership question is no longer whether to do this. The question is whether public organizations will do it proactively — with governance, funding and accountability — or reactively under pressure. 

Alan R. Shark, a senior fellow at the Center for Digital Government, is an associate professor at the Schar School for Policy and Government at George Mason University, where he also serves as a faculty member in the Center for Human AI Innovation in Society. He is also a senior fellow and former executive director of the Public Technology Institute, a fellow of the National Academy of Public Administration, and founder and co-chair of its Standing Panel on Technology Leadership. He is the host of the podcast series Sharkbytes.net. The Center for Digital Government and Government Technology are both divisions of e.Republic.