ADA Compliance and WCAG Updates: What Government Websites Need to Do Now

This April, new ADA compliance rules will require state and local governments to make their websites and mobile apps accessible. Large jurisdictions (populations of 50,000 or more) must comply by April 24, 2026, while smaller jurisdictions and special districts have until April 26, 2027.

For cities, counties, and agencies across the country, the focus is on aligning with the Web Content Accessibility Guidelines (WCAG). Understanding the differences between WCAG 2.0 and WCAG 2.2 is key to preparing effectively and ensuring compliance with the directive.

From WCAG 2.0 to WCAG 2.2: What Changed

The Web Content Accessibility Guidelines (WCAG) have evolved over time to reflect how people use the web and the barriers they face. For public sector organizations, understanding these changes is critical because they directly affect how residents interact with government services online.

WCAG 2.0 (2008)

• Established the foundation for accessible websites.
• Required text alternatives for images, logical page structures, and keyboard navigation.
• Focused primarily on desktop experiences and visual accessibility.

What this meant in practice: Cities needed to ensure that basic content — like images, headings, and links — could be understood by screen readers and that websites could be navigated without a mouse.

WCAG 2.1 (2018)

• Expanded requirements to cover mobile accessibility, recognizing the rise of smartphones.
• Added guidance for users with low vision, such as requirements for contrast ratios.
• Introduced criteria for cognitive accessibility, like avoiding time limits that could disadvantage users.

What this meant in practice: Cities had to test their websites on mobile devices, adjust color schemes for readability, and ensure interactive features (like online forms) didn’t lock users out if they needed more time.

WCAG 2.2 (2023)

The newest version adds refinements that matter directly for government websites:

• Stronger focus indicators: Interactive elements like links, buttons, and form fields must have clear visual cues when selected.
  
  • In practice: Cities should update their site styles so keyboard users can always see where they are. For example, a visible outline or highlight around the active button.
• Drag-and-drop alternatives: Users with limited dexterity must be able to complete tasks without complex movements.
  
  • In practice: If a city’s permit application system uses drag-and-drop uploads, it must also allow a simple “browse and upload” option.
• Error prevention and correction: Forms must provide clear instructions and error messages.
  
  • In practice: Utility bill payment forms should explain why an entry is invalid (“Please enter the date in MM/DD/YYYY format”) instead of just showing “Error.”
• Support for cognitive and learning disabilities: Content should be easier to understand and navigate.
  
  • In practice: City websites should avoid jargon, use plain language, and provide consistent navigation so residents don’t get lost moving between pages.

Practical Changes Cities Should Make

To meet WCAG 2.2 standards, public sector websites should prioritize:

Forms and Applications

• Every form should have clear labels, instructions, and error messages that guide users through the process. For example, if a resident enters an invalid date, the error message should explain the mistake and suggest the correct format.
• Forms must be usable without a mouse. This ensures residents who rely on keyboards or assistive technology can still apply for permits, pay bills, or request services.

Navigation and Focus

• Keyboard users should always know where they are on a page. Cities should implement visible focus indicators, such as a highlighted outline around the active link or button.
• Menus and navigation should remain accessible when zoomed in or viewed on smaller screens. Hidden or disappearing navigation creates barriers for residents with low vision.

Mobile Accessibility

• With more residents accessing city websites on smartphones, layouts must adapt seamlessly. Buttons and links should be large enough to tap without difficulty, and text should remain readable without horizontal scrolling.
• Testing across devices is essential. A site that works on desktop but fails on mobile excludes a significant portion of the community.

Document Accessibility

• PDFs, Word documents, and spreadsheets should be created with accessibility in mind. This means adding headings, alt text for images, and ensuring tables are properly structured.
• Staff should be trained to use accessibility checkers before publishing documents. This prevents inaccessible agendas, reports, or notices from being posted online.

Content Management Systems (CMS)

• Cities should confirm their CMS supports accessibility features like alt text fields, heading structures, and accessible templates.
• If the current CMS falls short, upgrading or adding accessibility plugins may be necessary. This investment pays off by reducing compliance risks and improving usability for all residents.

Options for Implementation

Cities vary in size and resources, so implementation should be flexible:

• Low-cost steps: Use free evaluation tools like the W3C Accessibility Evaluation Tools List  to identify issues. Train staff on accessible document creation.
• Vendor partnerships: Review contracts to ensure accessibility obligations are met. Technology vendors, including Switchboard Live, can help fill gaps without requiring a full rebuild.
• Consultants: For cities with complex sites, accessibility consultants can provide actionable guidance and training.
• Phased approach: Start with high-impact areas like forms, council agendas, and emergency alerts. Expand improvements over time.

Why Compliance Matters

Compliance with these rules ensures equal access to information and services for all residents. When websites are inaccessible, residents with disabilities may be unable to:

Read council agendas or participate in public meetings  

• If agendas, minutes, or livestreams are not accessible, residents with vision or hearing impairments may be excluded from civic decision-making. This reduces transparency and weakens democratic participation.

Access emergency alerts during severe weather or public safety incidents  

• Inaccessible alerts — such as images without text alternatives or videos without captions — can prevent residents from receiving life-saving information in real time.

Pay utility bills or apply for permits online  

• If forms are not navigable by keyboard or lack clear error messages, residents may be locked out of essential services. This forces them to rely on in-person visits, which can be burdensome or impossible for those with mobility challenges.

Understand documents and notices  

• PDFs or Word files that are not tagged for accessibility cannot be read by screen readers. This means residents may miss critical information about taxes, elections, or public health.

Engage with digital democracy tools  

• Online surveys, comment forms, or feedback portals that are not accessible prevent residents with disabilities from voicing their opinions. This skews public input and undermines equity in policymaking.

‍

The upcoming ADA compliance rules are a chance for cities to modernize their digital presence and make it more inclusive. By focusing on WCAG 2.2 updates, investing in staff training, and leveraging technology partners, public sector organizations can meet the standards in a practical and sustainable way. Accessibility is not a one-time project but an ongoing responsibility. Cities that act now will not only meet compliance requirements but also build stronger, more connected communities.

‍