In This Guide:
- Which accessibility rules change in 2026 and who they apply to
- Where WCAG 2.1 AA and WCAG 2.2 AA actually matter
- What to prioritize now to avoid compliance and usability problems later
The Simple Truth Most Organizations Miss
Accessibility is no longer something you “add later” if someone complains.
In Washington, multiple rules converge in 2026, and they apply to different types of organizations in different ways. The confusion usually stems from assuming there is a single universal law. There isn’t. There are overlapping requirements with very real deadlines.
If you manage a public-facing website and fall into one of the covered groups, waiting puts you behind schedule before you realize it.
What Changes in 2026 for Washington Public Entities
The biggest shift comes from the U.S. Department of Justice’s ADA Title II web rule.
This rule requires state and local governments to ensure their websites and mobile apps conform to WCAG 2.1 Level AA. The compliance deadline depends on the size of the entity, with many larger public entities required to comply by April 2026.
This affects more organizations than people expect. City websites, counties, public libraries, school districts, public utilities, and special districts are all commonly covered.
The practical tradeoff is straightforward. Public entities that delay remediation often face rushed fixes, incomplete compliance, or emergency budget requests as the deadline approaches.
Washington State’s Own Standard Moves the Bar
In addition to the federal ADA rule, Washington State has its own digital accessibility policy and standard.
As of July 1, 2026, Washington State agencies are expected to meet WCAG 2.2 Level AA. This applies not only to internal teams but also to vendors who build or maintain sites on the state’s behalf.
The difference between WCAG 2.1 and 2.2 is not cosmetic. WCAG 2.2 adds success criteria focused on focus visibility, target size, and user interaction reliability. These are common problem areas on modern websites.
For agencies and vendors, the tradeoff is clear. Sites built to 2.1 may still require rework. Sites built to 2.2 now are less likely to need remediation later.
Healthcare and Federally Funded Organizations Face a Separate Deadline
Organizations that receive federal financial assistance from the U.S. Department of Health and Human Services face another requirement.
If the organization has 15 or more employees, its web content and mobile apps must conform to WCAG 2.1 Level AA by May 11, 2026. Smaller organizations have an additional year.
This often affects healthcare providers, clinics, and related service organizations in Washington that do not consider themselves “government,” but still fall under federal accessibility rules.
The risk here is operational. Websites that block access to forms, scheduling, or patient information create both compliance issues and real service failures.
What Accessibility Compliance Is Actually About
Most rules do not require a visible accessibility settings panel.
They require the site itself to be usable by people navigating with keyboards, screen readers, assistive technology, and alternative input methods. This is about structure and behavior, not overlays.
In practice, accessible websites share common traits. When those traits are missing, users get stuck.
What accessibility work usually focuses on:
- Keyboard navigation and visible focus states
- Proper form labels, errors, and validation feedback
- Clear heading structure and landmarks
- Sufficient color contrast and readable links
- Meaningful alt text and accessible documents
An accessibility widget can help some users, but it does not replace these fundamentals.
Who Should Be Treating This as Urgent
Some organizations can afford to move deliberately. Others cannot.
This is the highest priority for:
- State and local government websites and apps
- Washington State agencies and their vendors
- Healthcare and HHS-funded organizations
Private businesses without direct coverage are not exempt from accessibility risk, but they typically have more flexibility in timing and scope.
The practical decision point is not fear. It is alignment. Sites built to recognized standards are easier to maintain, defend, and use.
What to Do Now if You Manage a Website
The smartest move is not to chase every rule. It is to choose the correct target standard and fix the real blockers first.
What we recommend starting with:
- Identify which rule applies to your organization
- Choose the appropriate WCAG level as your baseline
- Audit for task-stopping issues, not cosmetic ones
- Include documents and PDFs in your scope
- Publish a clear accessibility statement and contact path
This avoids rushed fixes and lets accessibility become part of regular site maintenance rather than a one-time scramble.
Common Questions, Answered Clearly
Do we need an accessibility widget on our site?
No. Widgets can help some users, but they do not, on their own, satisfy WCAG requirements. Accessibility is primarily about how the site is built.
Is WCAG 2.2 required everywhere in Washington?
No. WCAG 2.2 AA is required for Washington State agencies as of July 1, 2026. Other organizations may still be required to comply with WCAG 2.1 AA.
Does this apply to small local governments?
Yes, but timelines vary. Smaller public entities often have later deadlines, not exemptions.
What if our site had been compliant a few years ago?
Older compliance does not guarantee current compliance. New content, new templates, and new tools often introduce issues over time.
Is this mostly a legal concern?
It is a usability concern first. Legal risk typically arises when usability problems prevent access to essential services.
