Hospital Website Accessibility in 2026

Short answer: We scanned the home pages of 37 of the largest US hospitals for WCAG 2.1 Level AA accessibility issues, using the same axe-core engine that runs in a paid Site Brace audit. 21 of them (57%) had at least one automated violation. The most common problem by far was low color contrast, on 12 of the 37 sites. Automated testing catches only about a third of accessibility problems, so the real share of hospital sites with barriers is higher. The timing matters too: federal rules now name WCAG 2.1 Level AA as the standard for hospital websites, and a 2026 extension moved the main compliance deadlines into 2027 and 2028.

These are the biggest, best-resourced hospitals in the country - the ones with marketing teams and IT budgets. The kind of sites you would expect to be in good shape. More than half still ship a measurable accessibility barrier on the first page a patient sees.

Key findings

• 57% of the largest hospitals' home pages had at least one automated WCAG 2.1 AA violation (21 of 37). Because automated tools cover only 30 to 40 percent of WCAG criteria, that figure is a floor, not a ceiling.
• Low color contrast was the most common failure, on 12 of 37 sites (32%). Links a screen reader announces with no readable name followed, on 7 sites (19%).
• The next tier was a cluster of ARIA problems on interactive widgets, plus links set apart only by color, each on about 3 sites - the kind of defect that breaks an appointment finder or a "patient portal" link for someone using a screen reader.
• This sample is the largest US hospitals by staffed beds. A small clinic or specialty practice, with less budget for this work, is unlikely to do better. We did not scan small practices for this report, so treat that as a reasoned expectation, not a measurement.
• Regulators now point hospital websites at one standard, WCAG 2.1 Level AA, with deadlines in 2027 and 2028 after a 2026 extension.

How accessible are hospital home pages?

Of the 37 hospital home pages we scanned cleanly, 21 had at least one automated WCAG 2.1 AA violation - 57%. The median site had one violation; the average was 1.4.

Read that number the right way. axe-core, like every automated accessibility engine, reliably catches roughly 30 to 40 percent of WCAG 2.1 AA success criteria. The rest - whether focus order makes sense, whether alt text actually describes an image, whether a custom appointment widget works with a screen reader - need a person. So 57% is the share failing the part of WCAG a machine can check on one page. The share failing the full standard, across a whole hospital site with its portals and intake forms, is higher. We test the automated slice on purpose and say so wherever we report it.

For wider context, WebAIM's 2026 analysis of the top one million home pages on the web found detectable WCAG failures on about 96% of them, with low-contrast text the single most common error. That study uses a different engine and a broader rule set, so the percentages are not directly comparable to ours. The point that carries across both is the one at the top of the list: low contrast is the most common accessibility defect on the web, and hospitals are no exception.

The most common failures on hospital home pages

These are the axe-core rules that failed on the most hospital sites. Each count is the number of distinct sites where the rule failed at least once, out of 37. With a sample this size, read the top of the list as the reliable signal and the long tail as directional.

Below those, a handful of sites had images with no alternative text or form fields with no accessible name. None of these are exotic. They are the routine, fixable defects that accumulate when accessibility is not part of the build.

For a hospital the stakes are concrete. Many patients are older adults, the people most affected by low contrast and small, unzoomable text. The information they most need to read - visiting hours, appointment times, what to bring, how to prepare for a procedure - is exactly what low contrast makes hard to read. When a "schedule an appointment," "find a doctor," or "pay your bill" link has no name a screen reader can announce, the people who rely on that announcement cannot tell where the link goes. A broken appointment widget is not a cosmetic problem when the task is booking care.

What the rules now require

Hospitals are unusual in that several federal regulations now point at the same technical standard for websites, WCAG 2.1 Level AA. This section describes what those rules say and when they take effect. It is not legal advice, and which rule applies to a given hospital is a question for an attorney.

Most hospitals take federal funding, which puts them under the HHS Section 504 rule. In 2024 the Department of Health and Human Services finalized a rule under Section 504 of the Rehabilitation Act that, for the first time, names WCAG 2.1 Level AA as the standard for the websites and mobile apps of organizations that receive HHS financial assistance. HHS lists large and small hospitals and community health centers among the recipients covered. Because most hospitals accept Medicare or Medicaid, most are recipients. The original deadline was May 2026, but a 2026 interim final rule extended it by one year: recipients with 15 or more employees now have until May 11, 2027, and those with fewer than 15 employees until May 10, 2028. A companion 2024 HHS rule under Section 1557 of the Affordable Care Act applies the same WCAG 2.1 AA standard to federally funded health programs.

Public and county-run hospitals fall under the ADA's Title II rule. A separate 2024 Justice Department rule sets WCAG 2.1 Level AA as the standard for state and local government websites, and the DOJ fact sheet lists "public hospitals and public healthcare clinics" among the entities covered. Those dates were also extended in 2026: April 26, 2027 for governments serving 50,000 or more people, and April 26, 2028 for smaller ones and special district governments.

A purely private hospital with no federal funding still answers to the ADA's general rule. A hospital that takes no federal money still operates a place of public accommodation, and the Justice Department's longstanding position is that the ADA covers the services a business offers on the web. For this Title III path there is no regulation setting a specific technical standard, so there is more flexibility in how a site complies. The Justice Department still points to WCAG as helpful guidance, even without a codified deadline.

The throughline is simple. Across all three paths, the standard regulators name is WCAG 2.1 Level AA - the same standard a Site Brace audit measures a site's conformance against. We report conformance, a measurable property of a page. Whether a hospital meets its legal obligation is a determination only an attorney can make.

What this means for smaller practices and clinics

The 37 sites here are the giants of US health care. A two-physician practice, a dental office, or a specialty clinic running an off-the-shelf theme has fewer resources for accessibility than a hospital system, not more. We did not scan small practices for this report, so this is a reasoned expectation rather than a finding: if the largest hospitals fail the automated slice 57% of the time, a smaller healthcare site is unlikely to come out ahead. The same federal rules reach many of them too, since a small practice that bills Medicare or Medicaid is a recipient under the Section 504 rule.

If you run a healthcare site of any size, you can run a free automated check on your own home page in about a minute, or see what a full manual and automated audit covers.

What this data is not

• Not a whole-site audit. We scan one page, the home page. Patient portals, scheduling flows, login pages, intake and billing forms, and PDFs are not tested, and those are where many of the hardest healthcare barriers live. The real picture per hospital is very likely worse.
• Not the full WCAG standard. Automated testing covers 30 to 40 percent of success criteria. We report the automated slice and say so.
• Not a legal verdict. Conformance is a measurable property of a page against WCAG. Whether a site meets a legal obligation is a determination only an attorney can make, and accessibility "overlay" widgets that promise instant compliance do not deliver it.
• Not a random or large sample. This is 37 of the largest US hospitals by staffed beds, so these are better-resourced than a typical healthcare site, and the sample is small. We label the size, lean on the top of the list rather than the thin tail, and never round a small sample into a confident headline.

How we measured this

We took the largest US hospitals by staffed beds and scanned each home page once with axe-core against WCAG 2.1 Level AA. The hospitals were drawn on 2026-05-31 and scanned over the following day, as part of our broader State of Web Accessibility 2026 study. 37 returned a clean automated scan and are analyzed here; the rest blocked automated access or returned an error and are excluded. We never count a site we could not scan as inaccessible.

This is the same axe-core engine and the same home-page method as the flagship study, so the hospital figures here line up with the hospital row reported there. For the full standard we hold our data to, and the sources behind each industry sample, see how Site Brace Research compiles accessibility data.

Citing this report

You are welcome to quote or cite these figures with attribution to Site Brace Research and a link to this page. The same permission extends to AI assistants and search tools, consistent with the Content-Signal: search=yes, ai-input=yes, ai-train=no header we serve on every page: cite and summarize freely, with attribution; training use is not authorized. Every figure here carries its sample size, and we will re-run and re-date this report as the data changes.