WCAG 2.1 Compliance: What Local Governments and Healthcare Providers Need to Know

Most websites were built for people who can see perfectly, hear without aids, and use a mouse without difficulty. A significant portion of the population cannot do one or all of those things. WCAG 2.1 is the standard that bridges that gap, and 2026 is the year the federal enforcement clock started ticking for local governments and healthcare providers.

If your municipality or practice has not looked at this yet, you are inside a 12-month implementation window. This is the moment to act.

What WCAG 2.1 Actually Is (The Plain English Version)

WCAG stands for Web Content Accessibility Guidelines. Version 2.1 was published by the World Wide Web Consortium and defines how websites should be built so they can be used by people with disabilities.

That includes people who:

Are blind or have low vision and use screen readers
Are deaf or hard of hearing and need captions or transcripts
Have motor impairments and navigate with a keyboard instead of a mouse
Have cognitive disabilities and need clear, simple language and layout

WCAG 2.1 groups its requirements into four principles. Content must be Perceivable, Operable, Understandable, and Robust. These are often called POUR.

There are three conformance levels:

Level A: Minimum accessibility
Level AA: The broadly required standard for most compliance obligations
Level AAA: The highest level, not required across the board

When regulations and legal rulings reference WCAG compliance, they almost always mean Level AA. That is the target this article focuses on.

Why 2026 Is the Year This Became Urgent

For years, WCAG compliance was a best practice with soft enforcement. That changed.

What Changed for Local Government

In April 2024, the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act requiring state and local governments to meet WCAG 2.1 Level AA for their websites and mobile apps.

Then, on April 20, 2026, the DOJ published an Interim Final Rule extending the original compliance dates by one year after determining that many covered entities needed more time to assess and remediate their websites. The updated deadlines are:

Jurisdictions serving populations of 50,000 or more: April 26, 2027
Jurisdictions under 50,000 population: April 26, 2028

That extension is not a reprieve. It is a final runway. The DOJ issued it specifically because of “the technical and staffing realities of covered entities,” which means the expectation is that organizations use this time to actually do the work. Private rights of action under the ADA remain active during the extension period, meaning residents can still bring accessibility claims independently of federal enforcement timelines.

For any jurisdiction that has not yet audited its site, the window from now to spring 2027 is not as long as it looks once you account for procurement, vendor timelines, and the remediation work itself.

What Changed for Healthcare

Healthcare providers face obligations under multiple overlapping frameworks.

The Americans with Disabilities Act applies to healthcare facilities that serve the public. Under existing ADA guidance and case law, providers are already expected to ensure their websites are accessible to patients with disabilities. This is not new, but enforcement through civil complaints and litigation has increased significantly over the past several years.

Section 504 of the Rehabilitation Act is the more specific mechanism here. Section 504 prohibits disability discrimination by entities that receive federal financial assistance - which includes any practice or health system that accepts Medicare or Medicaid. On May 7, 2026, the HHS Office for Civil Rights issued its own Interim Final Rule establishing specific web accessibility compliance deadlines under Section 504:

Healthcare recipients of federal funding with 15 or more employees: May 11, 2027
Smaller practices with fewer than 15 employees: May 10, 2028

Section 1557 of the Affordable Care Act adds a parallel layer prohibiting discrimination on the basis of disability for covered healthcare entities. Numerous organizations have already faced complaints and settlements tied to inaccessible patient portals, appointment booking tools, and informational content.

State-level requirements vary and in some states add additional layers. Healthcare organizations operating across state lines may face multiple sets of expectations.

As with the government extension, private ADA claims remain available to patients regardless of the HHS enforcement timeline. The deadline extension does not reduce existing legal exposure - it provides a defined window for organizations to get into compliance before federal enforcement begins.

What Non-Compliance Actually Looks Like

WCAG 2.1 failures are often invisible from looking at a site. They show up in audit tools and through the experience of affected users.

Common failures across government and healthcare sites include:

Images without descriptive alt text, leaving blind users with no information
Videos without captions, excluding deaf and hard-of-hearing users
Forms that cannot be completed with a keyboard alone
Color contrast ratios that make text hard to read for low-vision users
PDFs that are not tagged for screen reader navigation
Session timeouts that do not give users enough time to complete tasks
No way to skip repetitive navigation when moving between pages

Any of these can form the basis of a complaint or lawsuit. Many fail silently for years before a user files a formal grievance.

Local Government: What Needs to Be Accessible

The DOJ rule covers more than just the homepage. Government entities need to assess:

All official government websites and web applications
Online forms for permits, licenses, registrations, and applications
Meeting agendas, minutes, and public records posted online
Emergency information and public notifications
Online payments for utilities, fees, and fines
Recruitment and employment pages

Archived content published well before the compliance deadline may have limited exceptions, but anything actively linked to as a current resource is generally expected to meet the standard.

For smaller municipalities running legacy content management systems or sites built a decade ago, the gap can be significant. The website that looked fine in 2018 may have structural issues that no amount of quick fixes will resolve.

Healthcare: What Needs to Be Accessible

For medical practices, clinics, hospitals, and health systems, accessibility obligations extend to:

Patient portal login and navigation
Appointment scheduling tools
Contact and location information
Insurance and billing pages
Medical records access
Telehealth and video visit platforms
Patient education materials
Prescription refill and communication tools

When a patient cannot book an appointment, access their test results, or reach billing support because the website fails them, that is the kind of situation that generates complaints, negative reviews, and regulatory attention. The patient experience extends to the digital front door.

How to Assess Where You Stand

Neither governments nor healthcare providers should assume their site is compliant because it was built by a reputable vendor or because it has never generated a complaint. Compliance requires verification.

A basic accessibility assessment includes:

Automated scanning: Tools like WAVE, Axe, or Lighthouse can identify a portion of WCAG failures automatically. These are a starting point, not a complete audit.

Manual review: Automated tools catch roughly 30 to 40 percent of real accessibility issues. The rest require a human tester navigating the site as someone with a disability would.

Screen reader testing: The experience of a keyboard-only user or someone using a screen reader like NVDA or VoiceOver often reveals failures no automated tool would catch.

Document review: PDFs and downloadable materials are frequently forgotten and often fail accessibility standards entirely.

For most organizations that have not done this work, the audit will find issues. The question is whether they are minor and fixable quickly or structural and requiring a rebuild.

What a Remediation Plan Looks Like

Once issues are identified, the path forward depends on severity and the underlying technology.

Fixes that can often be addressed without rebuilding:

Adding alt text to images
Improving color contrast on text and buttons
Adding captions to embedded videos
Replacing inaccessible PDFs with accessible HTML pages

Structural problems that may require more significant work:

Replacing forms built on frameworks that cannot produce accessible output
Rebuilding navigation to be fully keyboard-operable
Migrating away from a content management system that generates inaccessible markup
Redesigning layouts that rely on visual positioning without semantic structure

Many organizations find that full remediation and a new site build cost similar amounts when the old site has deep structural problems. If the technology cannot be made compliant, the technology needs to change.

The Case Beyond Compliance

Accessible websites are better websites for everyone.

Captions help people watching in a noisy environment. Clear navigation helps users under stress. High contrast helps people viewing a screen in bright sunlight. Keyboard operability helps power users who work faster without a mouse.

For local government, an accessible site means more residents can actually use the services they pay for. For healthcare, it means more patients can navigate their own care without calling the front desk. The legal requirement and the practical benefit point in the same direction.

How to Capitalize on the Federal Extensions

The DOJ and HHS extensions pushed deadlines out by one year. That is not a signal to wait. It is a defined window to complete work that should have started already.

Organizations that treat this extension as a grace period rather than an implementation timeline are the ones that will find themselves scrambling again in 2027. Regulators and courts look favorably on documented good-faith efforts. An audit, a plan, and visible progress carry weight. No action does not.

A practical use of this window:

Conduct an accessibility audit to establish a baseline and identify specific failures
Build a remediation plan with a timeline tied to your enforcement deadline
Address the highest-severity failures first, particularly anything in forms, navigation, or patient-facing tools
Post an accessibility statement on your site with a contact method for users who encounter barriers
Work through full remediation rather than stopping at partial fixes

Remember that private ADA claims remain active during this window regardless of where federal enforcement stands. An audit and a visible remediation effort reduce that exposure even before the official deadline arrives.

If you are a municipality, county, clinic, or practice that needs a site built to WCAG 2.1 AA from the ground up, that is one of the things we do. A compliant site does not need to be retrofitted later. We build websites that are accessible by design, so the work you do now is the work you keep. If you want a second set of eyes on where your current site stands - or want to talk about what a compliant rebuild would look like - start with a conversation here.

Frequently Asked Questions

What is WCAG 2.1 and why does it matter now?

WCAG 2.1 is the Web Content Accessibility Guidelines version 2.1, published by the World Wide Web Consortium. It defines how websites should be built to work for people with visual, auditory, motor, and cognitive disabilities. It matters now because federal rules under the ADA have established hard compliance deadlines for local governments, and healthcare providers face escalating enforcement under existing federal law.

Does my small town or county have to comply with WCAG 2.1?

Yes. All state and local governments in the United States are covered by the DOJ’s Title II ADA rule. Following a DOJ Interim Final Rule issued April 20, 2026, jurisdictions serving populations of 50,000 or more have until April 26, 2027 to comply. Smaller jurisdictions under 50,000 have until April 26, 2028.

Are healthcare websites required to be accessible?

Yes. Healthcare providers are covered by the Americans with Disabilities Act and by Section 504 of the Rehabilitation Act if they receive federal funding such as Medicare or Medicaid reimbursements. Under an HHS Office for Civil Rights Interim Final Rule issued May 7, 2026, practices with 15 or more employees must comply by May 11, 2027. Smaller practices with fewer than 15 employees have until May 10, 2028. Accessible patient portals, appointment tools, and informational content are not optional for covered entities.

What level of WCAG compliance is required?

Most legal requirements reference WCAG 2.1 Level AA. Level A is the minimum standard and Level AAA is the most stringent, but Level AA is the compliance target under both the DOJ ADA rule and healthcare accessibility frameworks.

How do I know if my website passes WCAG 2.1?

Automated tools like WAVE, Axe, or Google Lighthouse can identify some issues at no cost. A complete assessment requires manual testing, including keyboard navigation and screen reader testing. Automated tools alone miss a significant portion of real accessibility failures.

What happens if a local government or healthcare provider does not comply?

Organizations can face formal complaints to the Department of Justice or the Office for Civil Rights, private ADA lawsuits, and significant settlement or remediation costs. Beyond legal exposure, the reputational risk of community members and patients being unable to access digital services is real and growing.

How long does a WCAG 2.1 remediation take?

It depends on the severity of issues and the underlying technology. Minor fixes to an existing site may take a few weeks. A site with structural accessibility problems may require months or a full rebuild. Given that the extended deadlines are April 2027 for larger governments and May 2027 for larger healthcare providers, organizations should begin their audit now to have enough time for either path.

Does WCAG 2.1 apply to PDFs and downloadable documents?

Yes. Documents posted on a public-facing website and used as part of delivering services are expected to be accessible. This includes PDFs, Word documents, and other downloadable content made available to the public through the site.

What is the difference between ADA compliance and WCAG compliance?

The ADA prohibits discrimination against people with disabilities and applies broadly to public entities and many businesses. WCAG 2.1 is the technical standard that tells you specifically how to build a website so it does not discriminate. ADA compliance for websites is now largely defined by meeting WCAG 2.1 Level AA.

Sources

World Wide Web Consortium (W3C). Web Content Accessibility Guidelines (WCAG) 2.1. w3.org/TR/WCAG21
U.S. Department of Justice. Accessibility of Web Information and Services of State and Local Government Entities. Final Rule under Title II of the ADA. Federal Register, April 2024.
U.S. Department of Justice, Civil Rights Division. Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities. Interim Final Rule. Federal Register Vol. 91, April 20, 2026. ada.gov
U.S. Department of Health and Human Services, Office for Civil Rights. Nondiscrimination on the Basis of Disability in Programs or Activities Receiving Federal Financial Assistance. Interim Final Rule. May 7, 2026. hhs.gov/civil-rights