Website accessibility for healthcare organizations: legal requirements and patient impact

Key takeaways

• Healthcare organizations answer to several accessibility laws at once: the ADA, Section 504 of the Rehabilitation Act for recipients of federal funding and Section 1557 of the Affordable Care Act.
• The HHS Section 504 rule requires WCAG 2.1 Level AA for websites and mobile apps. In May 2026, HHS extended the compliance dates by one year to May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones.
• The extension changed timing only. The standard and the duty to make reasonable modifications for patients with disabilities still apply today.
• The patient impact is large: the CDC reports more than one in four US adults has some type of disability.
• Portals, scheduling tools, intake forms, telehealth platforms and PDFs all count, including tools supplied by vendors.

Healthcare organizations face accessibility requirements from multiple directions, and their websites carry higher stakes than most. Patients use them to find a provider, book an appointment, fill out intake forms, pay a bill and read test results. When those tasks fail for someone using a screen reader or a keyboard, the barrier is to care itself. This Emulent guide explains the legal requirements, how to assess your site, what to do next and how accessibility supports patient acquisition. It is general guidance, not legal advice; confirm your obligations with counsel.

What accessibility laws apply to healthcare websites?

Most healthcare organizations fall under at least two overlapping laws, and the technical standard behind all of them is WCAG 2.1 Level AA.

The Section 504 rule covers content you provide directly and content provided through contracts or licenses, so third-party patient portals, scheduling widgets and telehealth platforms are in scope. Duane Morris notes that the 2026 interim rule left the substantive scope unchanged and kept the duty to make reasonable modifications in force during the extension.

How do you assess a healthcare website for accessibility?

Start with the tasks patients need to complete, then test those paths with automated tools and by hand.

• Map the core tasks: find a provider or location, book or request an appointment, complete intake forms, log in to the portal, pay a bill and start a telehealth visit.
• Run automated scans with WAVE, axe DevTools or Google Lighthouse on each template and task page.
• Test by keyboard alone, using Tab, Shift+Tab, Enter, Space and the arrow keys, and confirm a visible focus indicator.
• Test with NVDA on Windows, VoiceOver on Mac and iPhone and TalkBack on Android, listening for unlabeled buttons, unannounced form errors and session timeouts with no warning.
• Review PDFs: patient forms, financial assistance policies and price transparency files are often scanned images with no readable text.
• Inventory vendors and request an Accessibility Conformance Report (ACR) for each patient-facing tool.

Expect findings. The 2026 WebAIM Million report detected WCAG 2 failures on 95.9% of the top one million home pages, averaging 56.1 errors per page, with low contrast, missing alt text and missing form labels most common.

What should healthcare organizations do after the assessment?

Turn the findings into a documented remediation plan with owners and dates. A clear record of progress helps if a regulator or patient raises a complaint.

• Fix task-blocking issues first: an intake form screen readers cannot complete or a scheduling button keyboard users cannot reach.
• Repair shared components such as headers, menus, form fields and buttons, so one fix carries across every page.
• Replace inaccessible PDFs with HTML pages or properly tagged documents.
• Add WCAG 2.1 AA conformance language to every new vendor contract and renewal.
• Publish an accessibility statement with a phone number and email for patients to request help or report barriers.
• Train content editors on alt text, headings, link text and captions, and retest after every major release.

Do not rely on an overlay widget. UsableNet’s 2025 report counted more than 1,400 lawsuits against companies that had accessibility widgets installed. Fixing the underlying code is the reliable path.

How does accessibility affect patient acquisition and SEO?

An accessible site reaches more patients and performs better in search. Many of the same fixes help screen readers and search engines read your content.

• Alt text on provider photos and facility images supports image search.
• Logical headings on service and condition pages help search engines and AI answer engines understand what you treat.
• Descriptive link text such as “Book with a cardiologist” tells users and crawlers where a link leads.
• Readable text and large tap targets help older patients, who are more likely to have vision or dexterity limitations, complete tasks on a phone.

Pair accessibility work with healthcare SEO and the same improvements support rankings and appointment requests. For practices on WordPress, most fixes can be made at the template and element level. Results vary by organization and market.

How the Emulent team can help

Emulent audits healthcare websites against WCAG 2.1 AA with automated scans and manual keyboard and screen reader testing, focused on the tasks patients rely on most. Our website design team fixes the issues in your templates, forms and content, and helps you document progress and vendor conformance. To see where your website stands before the Section 504 deadline, contact the Emulent team.