HHS Section 504 web accessibility is now a practical planning item for any healthcare organization that receives federal health funding. This guide explains who is covered, which technical standard applies, what the May 11, 2026 compliance date means, and how the rule differs from the ADA. It is general information, not legal advice, and it is published on Accessify’s own blog, so read the vendor section with that in mind.
HHS Section 504 web accessibility at a glance
Quick answer: The HHS Section 504 rule requires recipients of HHS financial assistance to make their websites and mobile apps accessible to people with disabilities. The standard is WCAG 2.1 Level AA, and the first compliance date is May 11, 2026. Covered organizations should audit, fix and document their digital services now.
- Who: recipients of HHS financial assistance, such as hospitals, clinics and health plans that take part in HHS-funded programs.
- What: accessible web content and mobile apps, including patient portals, forms and documents.
- Standard: WCAG 2.1 Level AA [INSERT: confirm citation to the final rule text on the HHS Office for Civil Rights site].
- When: first compliance date of May 11, 2026. Check the final rule for whether a later date applies to smaller recipients.
Who is covered by the HHS rule
The rule applies to recipients of HHS financial assistance. Receiving that funding is the trigger, not the size of the organization or whether it is public or private. If your clinic, hospital system or health plan receives HHS funds, your digital services are in scope.
Two examples show how this plays out. A small clinic with a brochure-style site, an online appointment form and a few PDF intake forms has a short list of assets, but every one of them must work for patients using screen readers or keyboards. A hospital system has a larger footprint: public websites, a patient portal, billing pages, a mobile app, video content and thousands of documents, often built by different vendors. Our healthcare website accessibility compliance guide covers the broader picture for providers.
Whether a specific funding stream counts as HHS financial assistance is a legal question. Confirm it with counsel before you decide a site is out of scope.
The technical standard: WCAG 2.1 Level AA
WCAG 2.1 Level AA means a page satisfies every Level A and Level AA success criterion. According to the W3C, Level A is the minimum, AA adds more, and AAA is the highest level. The W3C also notes that WCAG 2.1 addresses content on desktops, laptops, kiosks and mobile devices, which is why it fits both websites and apps. You can read the full text in the official WCAG 2.1 recommendation.
The W3C says WCAG 2.1 was started to improve guidance for people with cognitive or learning disabilities, people with low vision and people with disabilities using mobile devices. New criteria such as Orientation, Reflow, Non-text Contrast, Pointer Gestures and Status Messages matter for portals and apps. The W3C also encourages use of the most current WCAG version, so many teams plan ahead for 2.2. Our WCAG 2.2 updates for website owners explains what changes.
One caution from the W3C: even AAA content will not work for every user, so testing with real assistive technology still matters.
What the May 11, 2026 date means now
May 11, 2026 is the first compliance date under the rule. If it is near or has passed, the work is no longer a future project: covered recipients should be able to show a good-faith, documented path to conformance.
A sensible sequence looks like this:
- Inventory every public web page, portal, app, form and document.
- Test the highest-traffic and highest-risk journeys first: booking, login, bill pay, test results, forms.
- Fix issues, retest, and record what you changed and when.
- Set up a way for patients to report accessibility problems and a named owner to respond.
Do not assume a clean automated report means you are done. The ADA.gov web guidance warns that a clean report does not necessarily mean everything is accessible, and recommends pairing manual checks with automated checkers.
How Section 504 differs from ADA Title II and Title III
HHS Section 504 web accessibility is tied to receiving HHS funding, while the ADA is tied to the type of entity. According to ADA.gov, Title II covers state and local governments, and Title III covers businesses open to the public, a category that includes hospitals and medical offices. A provider can fall under more than one of these laws at once.
- Trigger: Section 504 applies to recipients of HHS financial assistance. Title II applies to public entities. Title III applies to public accommodations.
- Standard: the HHS rule names WCAG 2.1 AA. ADA.gov’s March 2022 guidance says the Department of Justice has no regulation setting detailed web standards for businesses, and points to WCAG and Section 508 as helpful references.
- Newer ADA rule: ADA.gov notes that requirements for state and local governments were published in the Federal Register on April 24, 2024, so that older guidance does not reflect them.
Read the Department of Justice web accessibility guidance for the ADA side. If you also work with federal agencies, our Section 508 compliance guide explains that separate standard.
Practical checklist for each digital asset
Websites and patient portals
Patient portal accessibility is where many providers struggle, because portals are often third-party products. Test keyboard access, visible focus, color contrast of at least 4.5:1 for normal text, text resizing to 200 percent, and clear headings. Ask your portal vendor for conformance details in writing.
Mobile apps
Check orientation, touch gestures with single-pointer alternatives, labels that match visible text, and status messages that screen readers announce. The WCAG 2.2 quick reference lets you filter criteria by level.
PDFs and forms
- Every field has a label and clear instructions, as ADA.gov recommends.
- Errors are identified in text and explain how to fix them.
- PDFs have real headings, reading order and text alternatives for images.
- Videos have accurate captions, and important visuals have text equivalents.
- Do not use color alone to show required fields; add the word “required”.
Comparing support options for healthcare sites
The sources used for this article do not cover vendor features, so this comparison is deliberately limited. Verify every point on each vendor’s own public pages, and check the vendor’s site for current pricing.
- Accessify: an AI-powered widget with automated remediation, a 2-minute install on Shopify, WordPress and other platforms, and plans from $19/month. Strength: fast, low-cost start for small clinics and practices. Limit: complex portals and apps also need manual testing and code fixes.
- UserWay, accessiBe and AudioEye: widget and automated-remediation tools in the same broad category. Strength: quick deployment for many sites. [INSERT: confirm each vendor’s healthcare-specific features and pricing from their public pages.]
- Level Access: an enterprise accessibility provider. Its staff are listed among WCAG 2.1 working group participants in the W3C acknowledgments. Strength: depth for large organizations. Better suited to hospital systems that want managed audits and platform tooling.
- Manual audit: the strongest evidence for portals and apps, and a good complement to any widget.
No widget alone guarantees legal compliance. Use automation for broad coverage and people for complex workflows.
HHS Section 504 web accessibility action checklist
- Confirm with counsel whether you receive HHS financial assistance.
- Inventory sites, portals, apps, forms, PDFs and video.
- Set WCAG 2.1 Level AA as your target.
- Run automated scans, then manual keyboard and screen reader tests.
- Ask third-party vendors, especially portal vendors, for conformance evidence.
- Fix priority journeys first and record every change.
- Publish a way to report accessibility problems and assign an owner.
- Retest after each release and schedule regular reviews.
Frequently Asked Questions
What is the HHS Section 504 web rule?
It is a rule under Section 504 of the Rehabilitation Act that requires recipients of HHS financial assistance to make their web content and mobile apps accessible to people with disabilities. It points to WCAG 2.1 Level AA as the technical standard. Confirm exact wording in the final rule text.
Who must comply with it?
Organizations that receive HHS financial assistance must comply, including many hospitals, clinics and health plans. Size does not decide coverage; funding does. Because funding streams vary, ask legal counsel to confirm whether your organization is a recipient before you decide the rule does not apply.
When is the first compliance date?
The first compliance date is May 11, 2026. If you are covered, treat it as the point by which your digital services should be tested, fixed and documented. Check the final rule to see whether a later date applies to smaller recipients.
Is this the same as the ADA?
No. The ADA applies by entity type: Title II to state and local governments and Title III to businesses open to the public, including hospitals and medical offices, according to ADA.gov. Section 504 applies because of HHS funding. A provider may be subject to both, so plan for the stricter requirement.
Can an accessibility widget make my site compliant?
A widget can fix many common issues quickly, but it cannot guarantee compliance. ADA.gov cautions that automated tools need careful use and that a clean report does not prove accessibility. Complex portals, apps and documents still need manual testing and, often, code-level fixes.
What should a small clinic do first?
Start with the patient journey: booking, forms and portal login. Test them with a keyboard and a screen reader, fix labels, contrast and error messages, then check PDFs. Write down what you tested and fixed. A small, documented, repeatable process is better than a one-time scan.
Want a quick starting point for your clinic or health system site? Explore how Accessify can help at accessify.app.
