Elementary Standards
HTMLCSSWeb StandardsSEOBlogStart reading
Home / Blog / WCAG 2.2 and Healthcare Web Apps: What Patient Portals Actually Need to Comply
Accessibility

WCAG 2.2 and Healthcare Web Apps: What Patient Portals Actually Need to Comply

A developer's walkthrough of the legal requirements and the actual markup patterns behind accessible patient portals, lab-result pages, and intake forms.

9 min read·2026-11-19·James Webb

TL;DR: WCAG 2.2 AA is the practical compliance floor for patient portals, layered under ADA Title III, Section 504, and Section 1557 of the ACA. The new 2.2 criteria that matter most for healthcare forms are focus visibility, dragging alternatives, minimum target size, and accessible authentication. HIPAA's access obligations quietly overlap with all of it, and PDFs of lab results carry the same requirements as the page that links to them.

Patient portals get built under more legal pressure than almost any other web app category, and most of that pressure is poorly understood by the engineers actually writing the markup. Compliance teams hand down "make it WCAG AA" without explaining which 2.2 criteria actually bite for a login screen and an intake form, and legal reads ADA Title III as the whole story when Section 504, Section 1557, and HIPAA's access language are all independently in play.

Teams doing healthcare web application development under HIPAA constraints end up treating accessibility and compliance as the same engineering problem, not two separate checklists, because the overlap between "a patient can't use this" and "a patient can't access their own health information" is almost total. This piece walks through what the law actually requires, then gets into the semantic HTML and ARIA patterns that make a patient-facing form, a results page, and a login flow hold up under both an audit and a real screen reader.

What WCAG 2.2 Actually Requires From a Patient Portal

Level AA is the floor almost every regulator, auditor, and procurement checklist actually references when they say "WCAG compliant," and that's true for healthcare just as much as for any other sector. Treat AA as the non-negotiable baseline; the earlier accessible forms checklist and touch target sizing piece both cover the general case. A patient portal, though, has a specific subset of 2.2's new success criteria that carry more weight than the rest of the spec.

Four of the new 2.2 criteria carry the most weight for a patient-facing form:

The Legal Landscape — ADA, Section 504/1557, and HIPAA's Quiet Overlap

ADA Title III covers places of public accommodation, and courts have consistently treated a healthcare provider's website and patient portal as falling under that umbrella, even though the statute predates the modern web by decades. Section 504 of the Rehabilitation Act reaches further for most hospitals and clinics specifically because it attaches to federal funding, and Medicare and Medicaid reimbursement means the great majority of U.S. healthcare providers receive some. Section 1557 of the Affordable Care Act layers a nondiscrimination requirement on top of that for health programs and activities specifically, and its implementing regulations explicitly name accessible web and mobile technology as part of compliance, not an afterthought bolted onto a general civil-rights statute.

The quieter piece is HIPAA. The Privacy Rule gives patients a right to reasonable access to their own health information, and the Office for Civil Rights has treated an inaccessible portal as a barrier to that right, not a separate accessibility issue to be handled by a different team. For an engineering group, this means the accessibility backlog and the HIPAA access backlog are functionally one backlog, even if legal and compliance keep them in separate spreadsheets.

Semantic HTML First — the Patient Intake Form

Before any ARIA, get the plain markup right. Every field needs a real <label> tied to its input by for/id, every piece of help or error text needs to be programmatically linked with aria-describedby, and medical/contact fields need correct autocomplete values so password managers and browser autofill don't fight the form:

<label for="dob">Date of birth</label>
<input
  type="date"
  id="dob"
  name="dob"
  autocomplete="bday"
  aria-describedby="dob-hint"
  required>
<p id="dob-hint" class="hint">Format: MM/DD/YYYY</p>

<label for="insurance-id">Insurance member ID</label>
<input
  type="text"
  id="insurance-id"
  name="insurance-id"
  autocomplete="off"
  aria-describedby="insurance-hint">
<p id="insurance-hint" class="hint">Found on the front of your insurance card</p>

None of this requires a single ARIA role. A screen reader announces the label, the input type, and the hint text automatically, because the relationships are expressed in plain HTML attributes the browser already understands.

Accessible Error Handling for Clinical Data Entry

Color-only error states are the most common failure on patient-facing forms, and they fail two different groups at once: screen reader users get no signal at all, and colorblind users may not perceive the color shift that sighted users rely on. The fix is to pair a visible, legible error message with aria-invalid and a live-region announcement so the failure is heard, not just seen:

<label for="email">Email</label>
<input
  type="email"
  id="email"
  aria-invalid="true"
  aria-describedby="email-error">
<p id="email-error" class="error" role="alert">
  Enter a valid email address, like [email protected]
</p>

role="alert" on the error text means it's announced as soon as it appears in the DOM, without requiring the user's focus to already be there. Keep the message specific: "Enter a valid email address" tells someone what to fix; a bare red border and the word "Error" does not.

Lab Results, Discharge Summaries, and the PDF Accessibility Gap

A portal can be fully keyboard-navigable and still fail a patient at the last step if the discharge summary or lab-result download is an untagged, scanned-image PDF. Section 508 and most state healthcare accessibility laws treat that document as part of the same service as the page linking to it, which means it needs the same structural tagging (headings, reading order, table markup for lab values, and alt text for any chart) that the HTML page around it already has. Remediation tools exist, but the cheapest fix is almost always upstream: generate the PDF from a tagged source document (a properly structured Word file or an accessible HTML-to-PDF pipeline) instead of trying to retrofit tags onto a flattened scan after the fact.

Testing a Patient Portal for Accessibility Without a Paid Scanner

Automated scanners catch missing alt text and malformed ARIA, but they catch almost none of what actually breaks a patient's ability to finish a task. The reliable test is the same one that works for any interface: unplug the mouse, turn on VoiceOver (Cmd+F5 on macOS) or NVDA (free on Windows), and walk through intake, login, and viewing a lab result using only Tab, arrow keys, and the screen reader's own navigation commands.

If a sighted developer doing this blind finds it confusing, a patient who actually relies on a screen reader is having a worse experience, not a better one.

A Short Note on Multi-Language Patient Populations

Accessibility and language access are frequently handled by separate teams, but for a patient population that isn't primarily English-speaking, they compound. A translated portal that drops ARIA labels, loses lang attribute changes on code-switched sections, or renders a right-to-left locale with left-to-right-only form logic reintroduces accessibility failures that the English version already solved. If the portal supports multiple languages, re-run the keyboard and screen-reader pass in each one. Don't assume a passing English audit transfers automatically.

FAQ

Does WCAG 2.2 AA satisfy ADA Title III for a healthcare website?

There's no statute that names WCAG 2.2 AA as the legal standard, but it's the benchmark courts and the Department of Justice consistently point to when settling ADA Title III web-accessibility cases. Meeting AA doesn't make a lawsuit impossible, but it is the closest thing to a safe-harbor argument a healthcare provider's legal team currently has.

What's the difference between Section 504 and Section 1557 compliance obligations?

Section 504 of the Rehabilitation Act applies to any entity receiving federal funding, which covers most hospitals and clinics through Medicare and Medicaid reimbursement. Section 1557 of the Affordable Care Act extends that same nondiscrimination requirement specifically to health programs and activities, and explicitly folds in accessible web and mobile technology as part of nondiscrimination, not as an afterthought.

Do PDF lab results need to be accessible, or just the web portal?

Both. A patient portal that's keyboard-navigable and screen-reader-friendly but hands a tagged-nothing PDF to the user at the final step has moved the accessibility failure one click deeper, not removed it. Section 508 and most state healthcare accessibility laws treat downloadable documents as part of the same service, with the same obligations as the page that links to them.

What's the single most common accessibility failure in patient portal forms?

Error messages that rely on color alone, paired with form fields that aren't programmatically associated with their error text. A red border with no visible text change is invisible to a screen reader and unreadable to a colorblind user; the field also needs aria-invalid and an aria-describedby pointing at text that actually explains what to fix.

Can a component library make a healthcare app WCAG-compliant out of the box?

Partially, and that's the dangerous part. Mainstream libraries like MUI and Chakra UI render reasonable base markup and handle common keyboard patterns, but redundant-entry flows, accessible authentication, and clinical-specific error announcements are domain decisions no generic library ships with. Treat the library as a floor, not a finish line, and test every patient-facing flow by hand.

How do I test a patient portal for accessibility without buying a scanning tool?

Unplug the mouse and use what's already on your machine: VoiceOver (Cmd+F5) on macOS or NVDA (free download) on Windows. Walk through intake, login, and viewing a lab result using only Tab, arrow keys, and the screen reader's reading commands. If a sighted, mouse-free pass through your own portal is confusing, a screen reader user is having a worse time than you are.

Does HIPAA require accessibility, or is that purely an ADA/Section 508 matter?

HIPAA itself doesn't cite WCAG, but its Privacy Rule requires covered entities to provide patients reasonable access to their own health information, and the Office for Civil Rights has treated an inaccessible patient portal as a barrier to that access. In practice, accessibility and HIPAA's access obligations overlap enough that an engineering team should treat them as one requirement, not two separate compliance tracks.

Further reading: the W3C's WCAG 2.2 specification for the full normative text, and ADA.gov's web accessibility guidance for how the Department of Justice currently frames Title III obligations online.

Back to the blog
More notes

Keep reading