WCAG for Medical Websites: What Practices Need to Meet
WCAG for medical websites explained for practice owners: which version to target, how ADA and HHS rules apply, what to fix first and how to test.

WCAG for Medical Websites: What Practices Need to Meet

For a medical website, the working target is WCAG 2.1 Level AA, and it covers more than your homepage: your scheduling tool, intake forms, patient portal and bill pay count too. No federal rule hands private practices a WCAG checklist, but the ADA applies to your website anyway, and WCAG is the yardstick that lawyers, courts and regulators reach for. Get it right once, at the build stage, and it stays cheap. Bolt it on after a demand letter and it doesn’t.
That’s the case for building accessibility into the site from the start. At KLYR Media, our HIPAA web design service is built for pharmacies and clinics, with compliance in mind from day one. Below: what WCAG is, which rules reach your practice, what usually breaks, and how to test.
TL;DR
- WCAG (Web Content Accessibility Guidelines) is the technical standard for making web content usable by people with disabilities. For healthcare, the benchmark is WCAG 2.1 Level AA.
- Private practices fall under ADA Title III. Practices taking Medicare, Medicaid or CHIP also face the HHS rule, with deadlines of May 11, 2027 (15 or more employees) and May 10, 2028 (fewer than 15).
- The rules cover portals, forms, scheduling and payment tools, including ones run by vendors. You can’t hand off the responsibility.
- The most common fixes are contrast, alt text, keyboard access, captions and labeled forms.
- Automated scanners catch only part of the problem. Pair them with a manual check.
Table of Contents
- What WCAG actually is
- Does the ADA apply to your practice’s website?
- The deadlines that matter
- WCAG 2.1 or 2.2?
- Where medical websites usually break
- A practical order of work
- How to test your site
- Accessibility and HIPAA: two jobs, one build
- Perspective
- Making it a build requirement, not a repair job
- FAQ
- Sources
What WCAG actually is
WCAG stands for Web Content Accessibility Guidelines. The W3C, the body that sets web standards, says WCAG 2 explains how to make web content more accessible to people with disabilities, and that it covers dynamic content, multimedia and mobile web. Versions 2.0, 2.1 and 2.2 all sit under the WCAG 2 banner. WCAG 2.2 is also an international standard, ISO/IEC 40500.
The guidelines rest on four principles: content must be Perceivable, Operable, Understandable and Robust, as MDN’s documentation lays out. In plain terms:
- Perceivable: a patient can see, hear or otherwise take in the content. Think alt text and captions.
- Operable: they can use it without a mouse, and without a steady hand.
- Understandable: forms and error messages make sense.
- Robust: screen readers and other assistive tools can read the page.
Each guideline has conformance levels: A, AA and AAA. Level AA is the one regulators and courts keep pointing to.
W3C’s accessibility team also notes that accessibility helps people without disabilities too: someone on a phone in bright sunlight, an older patient whose eyesight is changing, a person with a broken arm. For a practice, that’s a lot of your real patients.
Does the ADA apply to your practice’s website?
Short answer: yes. ADA.gov states that hospitals and medical offices are public accommodations under Title III, and that the Department of Justice has long held that the ADA’s nondiscrimination and effective-communication requirements apply to what you offer on the web. What DOJ hasn’t done is write a detailed technical web regulation for private businesses.
That gap is where the confusion comes from. No rulebook says “use WCAG 2.1 AA” for a private practice, but courts and settlements frequently reference WCAG as the benchmark. The Medical Society of the State of New York adds that federal courts have repeatedly held that Title III extends to private healthcare offices’ websites and digital tools.
If your site also needs to meet imaging or records obligations, the same nondiscrimination thinking applies to those channels. For example, a practice that shares imaging results online should understand the compliance rules for radiology practices alongside its accessibility duties, so patients can reach their results in a form they can actually use.
Three rule sets, one benchmark
| Rule | Who it reaches | What it asks |
|---|---|---|
| ADA Title III | Private practices, clinics, pharmacies open to the public | General nondiscrimination and effective communication, including online |
| DOJ Title II rule (2024) | State and local government entities, such as public hospitals | WCAG 2.1 Level AA for websites and mobile apps |
| HHS Section 504 rule (2024) | Practices receiving HHS funding (Medicaid, CHIP, Medicare) | WCAG 2.1 Level AA, with deadlines by size |
Section 1557 of the Affordable Care Act separately prohibits disability discrimination and may carry its own digital requirements for physicians who accept Medicare or Medicaid.
So for most of our readers, the practical answer is the same whichever rule applies: build to WCAG 2.1 AA.
The deadlines that matter
In 2024, DOJ and HHS finalized rules on web and mobile accessibility. According to the American Academy of Pediatrics, HHS-funded practices must meet WCAG 2.1 Level AA by May 11, 2027 if they have 15 or more employees, and by May 10, 2028 if they have fewer than 15.
Two details worth knowing. First, there’s no general exemption for smaller practices or individual clinicians who receive federal funding. Second, the rules reach beyond the website: mobile apps, kiosks, appointment scheduling, bill payment, patient portals and online forms, including tools run by third-party vendors.

A 15-person practice has until spring 2027. That sounds far off until you list how many patient-facing tools you run.
WCAG 2.1 or 2.2?
WCAG 2.2 is the newest version. MDN notes that newer versions don’t replace older ones, and WAI recommends the most recent. But the benchmark in the healthcare rules and guidance is 2.1 AA. The AAP says web content must conform to WCAG 2.1 Level AA.
Our take: aim for 2.1 AA as the floor, and build new pages with 2.2 in mind. Version 2.2 adds to 2.1 rather than contradicting it, so you won’t redo work.
Where medical websites usually break
Pharmacy and clinic sites tend to fail in the same places. Patients hit these walls at the exact moment they’re trying to book, refill or pay. Based on the ADA’s own guidance, these are the barriers to look for:
- Low color contrast. Light gray text on white, or pale buttons. The ADA says text needs sufficient contrast with its background.
- Color as the only signal. A red border on a form field means nothing to a colorblind patient. Add the word “required” next to the field.
- Images without alt text. Screen readers skip them or read out a file name. Short, descriptive alt text fixes it.
- Videos without captions. Captions need to be synchronized, accurate and identify speakers.
- Unlabeled forms. Intake, refill and contact forms with no proper labels, no keyboard access, or vague error messages.
- No keyboard navigation. Patients who can’t use a mouse get stuck in menus, pop-ups and date pickers.
- Messy headings. Semantic headings are how screen reader users jump around a page. Styled text that only looks like a heading doesn’t count.
- No way to report problems. The ADA suggests giving people a public way to tell you about accessibility issues.
- Zoom that breaks the layout. Patients should be able to enlarge text in the browser without losing content.
The pattern: the third-party widgets cause the most damage. Booking calendars, portal logins and payment screens are often embedded from vendors, and they’re the screens patients actually use.
A practical order of work
Good news first. MSSNY’s guidance for small practices says you don’t need to rebuild your website from scratch, and that a handful of targeted changes (alt text, contrast, keyboard access, captions, labeled forms) goes a long way.
Here’s a sequence that holds up, drawing on the American Dental Association’s digital accessibility guide, which is written for dental practices but lays out steps any covered practice can follow:
- Inventory every patient-facing tool. Website, mobile app, portal, intake and consent forms, online payment, scheduling, chat. If a patient touches it, list it.
- Audit against WCAG 2.1 A and AA. Check captions, alt text, keyboard navigation, labeled forms, color-independent information, clear error messages and contrast.
- Fix by risk and impact. Start with the tools patients must use: booking, forms, payment, portal login.
- Put accessibility in vendor contracts. Ask for WCAG 2.1 AA compliance as a contract term, and for a VPAT or Accessibility Conformance Report (a vendor’s written statement of how its product measures up).
- Train staff and document your policy. Whoever posts a PDF or a video needs to know the basics.
- Monitor continuously. Every new page and plugin update is a chance to break something.
The AAP’s point is worth underlining: existing content needs to have its barriers found and fixed, while all new or updated content should be accessible from the start. That’s why a rebuild or redesign is the cheapest moment to get this right. W3C makes the same point: evaluate early and throughout a redesign, when problems are easier to address.
Why vendors don’t take the liability off you
The American Dental Association is blunt: covered entities remain fully responsible for third-party accessibility. If your booking vendor’s calendar fails a screen reader, it’s your patient who can’t book. Review existing contracts, and get written confirmation from developers and portal vendors that their products meet WCAG.
How to test your site
Start with an automated checker. It will flag missing alt text, low contrast and unlabeled fields fast. But don’t stop there. ADA.gov advises pairing an automated check with a manual one: a clean report doesn’t guarantee an accessible site, and a few flagged errors don’t always mean real barriers. W3C agrees that no tool alone can determine whether a site meets accessibility guidelines; a knowledgeable human has to evaluate it.
A manual pass you can do yourself in 20 minutes:
- Unplug the mouse. Can you get through the booking flow with Tab, Enter and arrow keys alone?
- Zoom the browser to 200%. Does anything overlap or vanish?
- Submit a form with an error. Does the message say what went wrong and where?
- Play a video with the sound off. Are captions there and accurate?
- Read a page by its headings only. Does the outline make sense?
Those checks find the obvious problems. A full WCAG audit of your site and its embedded tools takes someone who knows the standard line by line.
Accessibility and HIPAA: two jobs, one build
Practice owners often treat these as separate projects. They shouldn’t be. The same forms that need clear labels and keyboard access also collect protected health information, and the same portal login has to be both secure and usable with a screen reader. Fixing one while ignoring the other leaves you exposed either way.
That’s the reason a healthcare-only build matters. When the person designing your intake form knows both rule sets, you don’t end up with a form that’s secure but unusable, or usable but leaking data. Our guide to healthcare website accessibility goes deeper on the compliance side, and top healthcare website features shows where accessibility sits among the other things a practice site has to do.
Perspective
We talk to independent pharmacy and clinic owners every week who think of accessibility as a legal chore for someone else’s website. It isn’t. It’s the same problem as a missed call: a patient tried to reach you and couldn’t. Revenue that never walked in.
Here’s how we see it. The patient who can’t read your pale-gray hours, can’t tab through your refill form, or can’t hear your video isn’t going to file a complaint. They’re going to call the chain down the street. Accessibility work is patient acquisition and retention work that happens to be backed by law.
That’s why we build for healthcare only. HIPAA-compliant design, local SEO and automated patient follow-up all depend on a site that every patient can actually use. Our approach is to build compliance in from day one, so you aren’t paying to retrofit it after the fact.
Independent practices can compete with the big chains and online pharmacies. But only if the front door works for everybody.
Opinly
Making it a build requirement, not a repair job
If you’re redesigning, or your current site was built by a generalist who never mentioned WCAG, the cleanest route is a build that treats accessibility and HIPAA as requirements from the first wireframe. Our HIPAA web design service is made for pharmacies, clinics and practices across the United States, and compliance is built in from day one.

Once the site is sound, the rest of your growth work (local search, paid ads, automated patient follow-up) lands on a page every patient can use. Our healthcare SEO service and patient retention automation are built for that second stage. For a wider look at how the pieces fit, see medical website design.
FAQ
Is WCAG legally required for a private medical practice?
Not by name. The ADA covers private medical offices as public accommodations, and DOJ says its requirements apply to what you offer online, but there’s no federal regulation spelling out web standards for them. In practice, courts and settlements frequently use WCAG as the benchmark. If you take Medicare, Medicaid or CHIP, the HHS rule sets WCAG 2.1 AA with firm deadlines.
Which WCAG level should my clinic aim for?
Level AA, on version 2.1 at minimum. That’s the standard named in the AAP’s guidance on the 2024 rules and in the DOJ Title II rule. Building new pages to WCAG 2.2 gives you room to spare.
Does my patient portal or booking tool count?
Yes. The rules reach portals, online forms, appointment scheduling and bill payment tools, including those run by third-party vendors. Ask vendors for written WCAG 2.1 AA commitments and a VPAT or Accessibility Conformance Report, and write it into the contract.
Can an accessibility overlay or scanner make my site compliant?
A scanner is a good first step, but it can’t finish the job. ADA.gov says a clean automated report doesn’t necessarily mean a site is accessible, and W3C says human evaluation is required. Plan for a manual audit and fixes in the site’s code and content.
Do small practices have to comply?
The AAP states there’s no general exemption for smaller practices receiving federal funding. The HHS deadline simply comes later for them: May 10, 2028 for fewer than 15 employees, against May 11, 2027 for 15 or more.
Sources
- WCAG 2 Overview, W3C Web Accessibility Initiative
- Introduction to Web Accessibility, W3C WAI
- Guidance on Web Accessibility and the ADA, ADA.gov
- Do Section 508 Accessibility Standards Apply to My Website?, Section508.gov
- Complying with 2024 ADA/HHS Requirements for Web and Mobile Content Accessibility, American Academy of Pediatrics
- Website and Digital Tool ADA Compliance, Medical Society of the State of New York
- Digital Accessibility Guide, American Dental Association
- Understanding the Web Content Accessibility Guidelines, MDN


