How to Build an ADA-Compliant Website for Your Healthcare Practice

Elena Marquez October 15, 2026 21 min read

Building an ADA compliant website for healthcare became personal for me a few years ago, when I tested a pediatric clinic’s website with a mother who is blind. She uses a screen reader every day and is faster on a keyboard than most of the developers I know. Her son needed a follow up appointment. At first, everything seemed fine, since the clinic’s homepage loaded without trouble. However, the “Book Now” button did not work for her. Her screen reader announced only the word “button,” with no label and no context. So she tabbed past it and landed in a chat widget she couldn’t close. Four minutes later, she gave up, picked up the phone, and sat on hold for twenty more. That afternoon showed me, more clearly than any audit report, that accessibility is a matter of patient access and not just a technical checkbox.

That clinic was not careless. In fact, its staff were kind people who would never turn a patient away at the front desk. Even so, their website was turning patients away every day, and nobody inside the building knew.

Who This Guide to an ADA Compliant Website for Healthcare Is For

I’ve spent my career auditing and rebuilding websites so people with disabilities can actually use them. Of all the sites I work on, healthcare sites are the ones I care about most, because the stakes are higher. For example, a broken checkout button on a clothing store costs a sale. By contrast, a broken appointment form at a cardiology practice can cost someone their care. For that reason, this guide walks you through how to build an ADA compliant website for healthcare. It follows the same process I use with practices, from solo therapists to multi location specialty groups.

Why an ADA Compliant Website for Healthcare Matters to Patient Care

Most practice owners first hear about web accessibility through a demand letter or a vendor’s sales pitch. Unfortunately, both framings put it in the wrong box. Accessibility is not mainly a legal problem or a marketing feature. Instead, it’s the same question as whether your exam rooms fit a wheelchair or whether you offer an interpreter.

The numbers make the point clearly. According to CDC data from the 2022 Behavioral Risk Factor Surveillance System, more than one in four American adults, over 70 million people, reported living with a disability. Among people aged 65 and older, the rate climbs even higher, to 43.9 percent. Now think about who books appointments at your practice. Older adults, people managing chronic conditions, and patients recovering from strokes or injuries make up much of that group. In other words, a large share of your patients are the people inaccessible websites fail first, and an ADA compliant website for healthcare is how you stop failing them.

Disability is also wider than most people picture. For instance, it includes low vision, color blindness, hearing loss, tremors, arthritis that makes a mouse painful, and cognitive conditions that make a cluttered page overwhelming. In addition, it covers temporary situations. Think of the patient with a broken wrist, or the parent squinting at a phone in a bright parking lot.

What the Law Requires From an ADA Compliant Healthcare Website

Let me lay out the legal picture plainly, because a lot of advice online is outdated or exaggerated. To be clear, I’m not an attorney, so your practice should run specific questions past legal counsel. Still, here’s the landscape as it stands in October 2026, and it shapes what an ADA compliant website for healthcare needs to deliver.

ADA Title III

Private healthcare providers are “places of public accommodation” under the Americans with Disabilities Act. Over the years, courts have repeatedly applied that duty to websites, especially websites connected to a physical location. Title III has no official technical standard for websites. In practice, though, courts, plaintiffs, and settlements all point to the Web Content Accessibility Guidelines (WCAG) as the benchmark.

Section 504 of the Rehabilitation Act

This is the rule most healthcare organizations need to watch. If your practice takes Medicare or Medicaid, or receives other HHS funding, you are likely covered. Back in May 2024, HHS published a final rule requiring covered websites and mobile apps to conform to WCAG 2.1 Level AA. Originally, the deadlines fell in 2026 and 2027. Then, in May 2026, an interim final rule moved them. As a result, recipients with 15 or more employees now have until May 11, 2027, while recipients with fewer than 15 employees have until May 10, 2028.

Please don’t read that extension as a pass. HHS acted after hearing that some recipients faced heavy burdens meeting the original dates, not because the requirement went away. Moreover, Section 504 and Section 1557 of the Affordable Care Act still require covered entities to provide effective communication, auxiliary aids and services, and equal access for people with disabilities. Those duties apply today, deadline or no deadline.

The Scope Is Broader Than Your Homepage

Notably, the rule covers more than the website your marketing team manages. It also applies to web content and mobile apps that outside companies provide or develop for you under contract. Consequently, your online scheduling tool, your patient portal, your bill pay page, your telehealth platform, and any remote patient monitoring app all count, even when another company built them.

Lawsuits Are Not Slowing Down

Seyfarth Shaw, a law firm that tracks these filings closely, reports that plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025. That figure represents a 27 percent increase from 2024. Healthcare is not immune, either. In fact, one midyear tally of 2025 filings counted 144 healthcare cases, or 7.1 percent of the total.

WCAG 2.1 AA: The Standard Behind Every ADA Compliant Healthcare Website

WCAG is written for engineers, and it reads that way. Underneath the technical language, however, it rests on four simple ideas. Every page on an ADA compliant website for healthcare should be:

Perceivable. Patients can take in the content, whether they see it, hear it, or read it through a screen reader or braille display.
Operable. Patients can navigate and use everything, including with a keyboard alone or voice control.
Understandable. Content and forms behave predictably and use clear language.
Robust. The code is clean enough that assistive technologies can interpret it reliably.

Level AA is the middle tier of the three conformance levels, and it’s the target the law points to. That said, if you’re building something new, I recommend aiming for WCAG 2.2 AA. After all, it’s the newer version and includes everything in 2.1. Better still, the HHS rule allows it, as long as the result offers equal or greater accessibility than WCAG 2.1 AA.

Step 1: Inventory Your Healthcare Website Before Making It ADA Compliant

Every project I run starts with a spreadsheet, not a redesign. Before you can build an ADA compliant website for healthcare, you need to know everything a patient might touch. First, list every digital touchpoint:

Your main website and every page template it uses
Online scheduling and appointment requests
Patient intake and registration forms
The patient portal
Bill pay and insurance verification
Telehealth platforms
PDFs, such as new patient packets, consent forms, and care instructions
Videos, webinars, and audio content
Your mobile app, if you have one, including any companion apps for wearable health devices

Next, note who owns each item. Is it your team, your web agency, or an outside vendor? Ultimately, that ownership column will drive most of your decisions later.

Step 2: Audit What Stands Between You and an ADA Compliant Healthcare Website

Automated scanners are a fine starting point. For example, free tools like WAVE, axe DevTools, and Lighthouse will find a lot of problems in minutes. On the other hand, automated tools typically catch only a fraction of real accessibility barriers. A scanner can tell you an image has alt text. Yet it cannot tell you whether that alt text says “IMG_4471.jpg” or “Dr. Patel examining a patient’s knee.”

The Three Layers of a Proper Audit

For this reason, a proper audit has three layers:

Automated scanning across every template to catch the obvious, repeatable errors.
Manual expert testing, where someone trained in WCAG checks each success criterion by hand. That means keyboard navigation, screen reader testing with NVDA, JAWS, and VoiceOver, zoom testing, and form behavior.
Testing with disabled users. Nothing replaces watching a real patient try to book an appointment. Every single time I do this, I learn something the checklist missed.

Test the Patient Tasks That Matter Most

Above all, focus your manual testing on the tasks that matter most. To start, check whether a patient can find your phone number and address. After that, confirm they’re able to request an appointment. Then make sure intake forms work from start to finish. Similarly, test whether bill payment goes through without a mouse. Finally, verify that the portal login is reachable. If those five tasks work, you’ve removed most of the harm, even before you’re fully conformant.

Step 3: Fix the Six Errors That Keep a Healthcare Website From Being ADA Compliant

Here’s some encouraging news. The most common accessibility failures are the same on almost every website, and they’re often easy to fix.

The WebAIM Million is an annual study of the top one million home pages. Admittedly, its 2026 edition is a sobering read. It found an average of 56.1 accessibility errors per page, up from 51 the previous year, and 95.9 percent of home pages failed basic WCAG standards. Nevertheless, about 96 percent of all errors fall into just six categories. It can also be done well: the University of Utah’s homepage ranked in the top 5 percent of that same report, with no errors detected.

Visual and Image Errors

Therefore, if you want the fastest progress toward an ADA compliant website for healthcare, fix these six first. Start with the errors patients notice on sight:

Low contrast text. Body text needs a contrast ratio of at least 4.5 to 1 against its background. That light gray text on a white background may look elegant, but many of your older patients can’t read it. So check your brand colors with a contrast checker before anything else.
Missing alt text. Every meaningful image needs a short description of what it shows or does. Meanwhile, purely decorative images should have empty alt attributes, so screen readers skip them.

Code and Labeling Errors

Next, move to the errors hidden in your code, which screen reader users hit constantly:

Unlabeled form fields. Every input needs a visible, programmatically connected label. Keep in mind that placeholder text inside a field is not a label, because it disappears the moment someone starts typing.
Empty links. Icon links with no text are the usual culprits here, like social media icons or a magnifying glass for search. As a result, screen readers announce them as “link” and nothing else.
Empty buttons. This was the clinic’s “Book Now” problem from my opening story. Visually, the button looked fine, but there was no accessible name behind it.
Missing document language. One line of code tells assistive technology which language the page is in. Without it, a screen reader may pronounce English text with Spanish phonetics, or the reverse.

Step 4: Build Forms Patients Can Finish on Your ADA Compliant Healthcare Website

Forms are where healthcare websites fail hardest, and where failure hurts most. After all, a patient who can’t complete intake online ends up with a clipboard in your waiting room, or never shows up at all, and few things hurt patient satisfaction faster.

When I review medical forms, I check for these things:

Clear labels and instructions placed before the field, not after it.
Grouped questions. Related items like “Do you have any of the following conditions?” belong in a properly coded fieldset with a legend. That way, screen reader users hear the question along with each checkbox.
Helpful error messages. “Invalid input” helps no one, whereas “Date of birth must use the format MM/DD/YYYY” helps everyone. In addition, errors should be announced to screen readers and tied to the field that caused them.
No surprise timeouts. If your form logs patients out after ten minutes, someone using a switch device or typing with one hand may lose everything. Instead, warn users before a timeout and let them extend it.
Accessible CAPTCHAs, or none at all. Image puzzles lock out blind patients completely. So use invisible spam protection or an accessible alternative instead.
Autocomplete attributes on fields like name, address, and phone number. This helps patients with memory or motor disabilities, and it also speeds things up for everyone else.

Step 5: Hold Your Vendors Accountable

This is where most practices get stuck. Of course, you can’t directly fix your scheduling platform’s code. Even so, you are still responsible for what your patients experience, and an ADA compliant website for healthcare is only as strong as the weakest tool linked to it.

Here’s what I tell clients:

Ask every vendor for an Accessibility Conformance Report (ACR), usually built on a document called a VPAT. Then read it closely, since many vendors list “partially supports” next to critical criteria and hope nobody notices.
Test the vendor’s tool yourself. For example, try booking an appointment using only your keyboard. If you can’t, your patients can’t either.
Write accessibility into your contracts. New agreements should require WCAG 2.1 AA conformance at minimum. Likewise, they should require the vendor to fix reported barriers within a defined timeframe.
Have a backup plan. Until a vendor tool is fixed, put a clear, accessible link nearby with an alternative. For instance, offer a direct phone line with real humans answering, or an accessible email request option.

Step 6: Treat PDFs as Web Content

Healthcare runs on documents. Think of new patient packets, HIPAA notices, financial policies, and preparation instructions for colonoscopies. Sadly, most of those PDFs are scanned images or untagged files that screen readers can’t read at all.

My honest advice is to convert as many PDFs as you can into regular web pages. An HTML page is easier to make accessible, easier to update, easier to read on a phone, and better for search. However, documents that must stay as PDFs need proper tagging. That means a logical reading order, real headings, labeled form fields, and alt text for images.

Fortunately, the rule offers some breathing room for older material. Specifically, exceptions cover archived web content that isn’t updated after the compliance date, along with certain legacy documents that patients no longer use to access care. But if a patient needs a document to receive care today, it isn’t archived. Therefore, it has to be accessible.

Step 7: Caption Your Videos and Transcribe Your Audio

If your practice publishes videos, such as physician introductions, procedure explainers, or exercise demos for physical therapy, they need accurate captions. Automatic captions generated by AI are a starting point, not a finish line. Indeed, auto captioning loves to mangle medical terms. I once watched “metformin” come out as “met for men” in a diabetes education video.

Similarly, prerecorded video needs audio description when important visual information isn’t spoken aloud. Consider a physical therapist demonstrating a stretch without narrating it. In that case, a blind patient gets nothing from the clip. Often, the simplest fix is to film it better, with the therapist describing each movement as they do it.

Podcasts and audio content need transcripts as well. Furthermore, videos should never autoplay with sound, because unexpected audio talks right over a screen reader user’s software.

Step 8: Design Choices for an ADA Compliant Healthcare Website

Some of the most important accessibility decisions happen in design, long before any code is written.

Visual and Navigation Choices

Keyboard focus must be visible. When someone tabs through your page, they need a clear outline showing where they are. Designers often remove this outline because they think it looks messy. Please don’t.
Logical heading structure. Use one main heading per page, then nested subheadings in order. After all, screen reader users navigate by headings the way sighted users skim.
Text that resizes cleanly. Patients should be able to zoom to 200 percent without losing content. Likewise, at 400 percent, content should reflow into a single column without horizontal scrolling.
Never rely on color alone. “Fields in red are required” means nothing to someone who can’t see red. Instead, add a text marker or an icon with a label.

Interaction and Language Choices

Generous touch targets. Small buttons crammed together are hard to tap with tremors or limited dexterity. WCAG 2.2 sets a minimum target size, and bigger is better.
Plain language. Write for a patient who is tired, worried, and maybe reading in a second language. In short, use brief sentences and common words, and explain terms when you can’t avoid them. This is where health literacy and accessibility meet.
Respect motion settings. Big animations and parallax effects can trigger dizziness or nausea in patients with vestibular disorders. For that reason, honor the reduced motion setting in their operating system.

Accessible design is not ugly design. On the contrary, some of the most beautiful healthcare sites I’ve worked on also had the strongest accessibility, because the constraints forced clarity.

Step 9: Skip the Overlay Shortcut

You’ve likely seen ads for accessibility widgets. Typically, a little icon sits in the corner and promises instant compliance with a single line of code. I understand the appeal, since it sounds cheap and fast.

Unfortunately, it doesn’t work. Overlays can’t fix the underlying code problems that block screen readers. Worse, they often interfere with the assistive technology patients already use, and many blind users actively avoid sites that run them. They don’t protect you legally, either. In the first half of 2025 alone, 456 lawsuits, or 22.6 percent of the total, targeted websites that already had accessibility widgets installed.

So spend that budget on real remediation instead. Granted, it costs more upfront. Even so, it’s the only route to an ADA compliant website for healthcare that actually helps patients.

Step 10: Publish an Accessibility Statement and Listen

Every healthcare website should have an accessibility statement linked from the footer. A good one:

Names the standard you’re working toward, such as WCAG 2.1 AA.
Describes what you’ve done and admits known gaps honestly.
Gives patients a real way to report barriers, like a phone number, an email address, and a named role responsible for responding.
Offers alternatives, such as help booking appointments by phone or documents in large print.
Shows a recent “last reviewed” date.

Then actually answer the feedback. A patient who takes the time to tell you your form is broken is, in effect, doing you a favor. Respond quickly, thank them, and fix it, the same way you would act on any other patient feedback.

Step 11: Keep Your ADA Compliant Healthcare Website Accessible After Launch

Accessibility isn’t a project you finish. Rather, it’s a habit you build. I’ve seen beautifully remediated sites slide backward within six months because a new staff member uploaded a scanned flyer or a plugin update broke the menu. In other words, an ADA compliant website for healthcare stays compliant only when someone keeps watching it.

To stay on track, follow these practices:

Train everyone who publishes content. Whoever posts blog articles, uploads forms, or updates provider bios needs to know about alt text, heading order, and link text.
Build accessibility into your website workflow. Check every new page and feature before it goes live, not after a complaint.
Run automated scans monthly and a manual expert review at least once a year, or after any major redesign.
Assign an owner. Someone in your organization needs to be accountable for accessibility, with real authority to push back on vendors and designers.
Document everything. Keep your audit reports, remediation records, vendor ACRs, and patient feedback logs. Should a complaint ever reach HHS or a court, a documented, good faith effort matters.

A Realistic Timeline for an ADA Compliant Healthcare Website

Practice owners always ask me how long this takes. For a typical independent practice with a 30 page website, a scheduling tool, and a portal, here’s what I usually see:

Weeks 1 to 3: Inventory, automated scans, and a manual audit of key patient tasks.
Weeks 4 to 8: Fix the six common errors, rebuild forms, add captions, and start vendor conversations.
Weeks 9 to 14: Convert or remediate PDFs, address design issues, and retest with assistive technology.
Week 15 onward: Publish your accessibility statement, train staff, and set up ongoing monitoring.

Larger organizations with multiple locations and many vendors, by comparison, should plan for six months to a year. That’s exactly why waiting until spring 2027 to start an ADA compliant website for healthcare is a mistake.

The Bottom Line on Building an ADA Compliant Website for Healthcare

Building an ADA compliant website for healthcare isn’t about chasing a perfect score on a scanner. Rather, it’s about making sure a patient with a disability can find you, understand you, and get care from you as easily as anyone else. Laws and deadlines will keep shifting. Nonetheless, that basic obligation won’t.

So start with the tasks that matter most to patients. Next, fix the common errors. Then hold your vendors to the same standard you hold yourself. Finally, listen to the people who use your site every day, because they’ll tell you what’s broken if you give them a way to do it, and that kind of patient engagement is worth more than any audit.

And that mother I tested with? The clinic fixed the “Book Now” button within a week. Today, she books her son’s appointments online. It took one line of code, and yet it changed her experience of that practice completely. In my experience, most accessibility wins look exactly like that.

FAQs About Building an ADA Compliant Website for Healthcare

Does the ADA apply to my private practice’s website?

In most cases, yes. Private healthcare providers are public accommodations under ADA Title III, and courts have applied that duty to websites. The Department of Justice explains its position in its guidance on web accessibility and the ADA.

What is the current deadline under the HHS Section 504 rule?

Practices with 15 or more employees that receive HHS funding must conform by May 11, 2027. Meanwhile, practices with fewer than 15 employees have until May 10, 2028. You can read the details in the HHS announcement extending the compliance dates.

Which standard should an ADA compliant website for healthcare meet?

The HHS rule requires WCAG 2.1 Level AA. However, for new builds, WCAG 2.2 AA is a smart target because it includes every 2.1 requirement plus a few more. The W3C overview of WCAG standards explains the versions and levels.

Will an accessibility widget or overlay make my site compliant?

No. Overlays don’t fix underlying code problems, and many sites using them have still been sued. Instead, real remediation is the only reliable path, as this analysis of 2025 ADA website litigation shows.

Am I responsible for my scheduling tool or patient portal if a vendor built it?

Yes. The rule covers content you provide through contracts and outside arrangements. For more detail, this overview of Section 504 deadlines for HHS funded providers covers vendor responsibility and exceptions.

How common are accessibility errors on websites?

Very common. In fact, the 2026 WebAIM Million report found detectable WCAG failures on nearly every home page it tested, mostly from the same six fixable errors.

References

Tags:Healthcare Technology