ADA Ally - Health

Accessibility Services for Hospitals, clinics, and private practices

No overlays, no shortcuts. Just real, lasting accessibility verified by people with experience using adaptive technology.

WCAG 2.1 AA

The standard in the HHS rule

Manual

Testing, no overlays

Web + docs

Portals, telehealth and PDFs

Credentials held by our testers

IAAP CPACC Certification
IAAP CPWA Certification
IAAP WAS Certification
IAAP CERTIFIED ADS Certification
DHS Trusted Tester Certification
Why now

A federal rule names the standard and the date

HHS’s Section 504 rule (45 CFR Part 84, Subpart I) requires recipients of HHS federal financial assistance, such as Medicaid or Medicare payments, to make their web content and mobile apps meet WCAG 2.1 AA.

HHS Section 504 web & mobile deadline
May 11, 2027 for organizations with 15+ employees

May 10, 2028 for fewer than 15 (revised from May 10, 2027)

days
hours
minutes
Hospitals · clinics · practices

Section 504 requires WCAG 2.1 AA

Web content and mobile apps must meet WCAG 2.1 AA by May 11, 2027 (15+ employees) or May 10, 2028 (fewer than 15), including content delivered through vendors.

All covered providers

Section 1557 covers documents and portals

Consent forms, discharge instructions, billing statements, prescription instructions, patient portals and digital forms are all in scope. OCR investigates complaints.

Public hospitals · health departments · EMS

DOJ Title II: April 26, 2027

State and local government entities serving 50,000+ people must meet WCAG 2.1 AA by April 26, 2027; smaller ones by April 26, 2028.

Covered: hospitals, clinics, physician practices, community health centers, nursing, home health, hospice, dental and vision providers.

The Americans with Disabilities Act applies regardless of federal funding. Title III (42 U.S.C. § 12181 et seq.) prohibits disability discrimination by private health care providers as public accommodations, and Title II (28 CFR Part 35, Subpart H) requires state and local government health entities to make their web content and mobile apps meet WCAG 2.1 AA. State laws, such as California’s Unruh Civil Rights Act, may impose additional statutory damages.

What we test

Every step a patient takes, end to end

We test journeys, not just pages. Select a step to see what we check and where healthcare sites usually fail.

Find a doctor or location

Provider directories, location finders and search filters, tested with screen readers, zoom and keyboard only.

Common failures we find

Map-only location search

Filters that update results silently

Provider cards with no heading structure

Book an appointment

Online scheduling, from choosing a reason for visit to a confirmed time.

Common failures we find

Time slots not announced to screen readers

Calendar grids that need a mouse

Session timeouts with no warning

Intake forms

Pre-visit questionnaires, insurance details, consent and e-signature.

Common failures we find

Unlabeled form fields

Errors shown only in red

E-signature widgets screen readers can’t operate

Portal & results

Patient portal login, messages, test results and prescriptions.

Common failures we find

CAPTCHA at login with no alternative

Results shown as images or charts only

Data tables with no header relationships

Telehealth visit

Joining a video visit, waiting room, in-call controls and chat.

Common failures we find

Unlabeled mute and camera buttons

No captions option

Waiting-room status not announced

Estimate & bill pay

Price estimates, statements, payment plans and confirmations.

Common failures we find

Third-party payment iframes with no labels

Confirmation not announced

Low-contrast amounts due

Discharge & aftercare

Discharge instructions, follow-up plans and patient education, online and as PDFs.

Common failures we find

Scanned PDFs with no text layer

Wrong reading order in instructions

No tagged headings to navigate

Contact & other formats

Contact forms, chat, callback requests and requests for large print, Braille or other formats.

Common failures we find

Chat widgets that trap keyboard focus

No way to request another format

Phone-only contact options

Who you serve

Your patients are this audience

Disability rises with age, and patients over 65 are a large share of hospital volume. Accessible care starts before the visit.

1 in 4

U.S. adults report a disability, more than 70 million people

43.9%

of adults 65 and older report a disability

What makes us different

Real testing, by the people who live it

Automated scans find the easy issues. The rest show up when someone actually tries to book a visit with a screen reader.

A

Lived-experience testers

Screen reader, voice control and keyboard users test every journey.

B

Manual, not just scanned

People find the barriers that block a booking; tools don’t.

C

Code-level fixes

Developers correct the code preventing access: widgets don’t.

D

No overlays

Widgets don’t fix source code; suits against sites using them ran 95–155 a month in 2025.

Common on healthcare sites every week

Scheduling widgets that don’t announce available times

CAPTCHA at portal login with no accessible alternative

Scanned discharge PDFs that read as a blank page

Patient documents & PDFs

Documents patients can actually read

Section 1557 guidance names these documents. Our IAAP ADS-certified team remediates them to tagged, screen-reader-ready PDFs, and fixes the templates so the next batch comes out right.

Consent & intake forms

Discharge instructions

Test results

Bills & statements

Notices of nondiscrimination

Patient education materials

Vendor tools

“But that’s our vendor’s code.” It’s still your responsibility.

The Section 504 rule covers content delivered through vendors, and a vendor saying “accessible” isn’t enough. We test their tools inside your site and give you evidence to push them.

Patient portals

Online scheduling

Telehealth

Payments

Chat & messaging

Vendor VPATs and ACRs checked against what we actually find, with findings written so you can send them straight to the vendor.

Services & pricing

Priced by scope, set after a 30-minute call

Start with one patient journey as a fixed-fee pilot, so a department can approve it without a long procurement cycle.

Fixed-fee pilot

Patient-journey audit

One patient journey, tested manually and with assistive tech, plus a retest after fixes.

from $X,XXX

Remediation

Our developers fix issues in your code, or pair with your team inside existing sprints.

from $X,XXX

Document remediation

Consent forms, discharge instructions, results and bills remediated to tagged PDFs.

from $XX / page

Vendor & VPAT review

Portal, scheduling and telehealth tools tested; VPATs checked. ACRs for digital health vendors.

from $X,XXX

Small-practice package

For practices under 15 staff (May 2028 date). May qualify for the Disabled Access Credit; check with your accountant.

from $XXX

Our proven process

Six steps, agreed before we start

1

Scoping call

30 minutes to pick the journeys, documents, vendors and deadlines that matter.

2

Access & patient data

Test accounts in a test environment, no real patient data. NDA, and a business associate agreement if PHI could be seen.

3

Testing & discovery

Manual and assistive-tech testing of every journey and vendor tool in scope.

4

Implementation & fixes

Prioritised fixes that fit your release schedule, not stall it.

5

Team training

Web, content and patient-document teams learn to keep it accessible.

6

Final audit & report

Retest and a report mapped to WCAG 2.1 AA, ready for an OCR review.

Deliverables

Documentation for an OCR review, not just a bug list

Every engagement ends with records that show what you tested, what you fixed and when.

Issue log by journey

Each issue tied to the step where it happens

Severity ratings

What blocks a patient vs. what slows them

WCAG 2.1 AA references

Every finding mapped to a success criterion

Fix guidance

Code-level, written for your developers

Retest results

Proof each fix actually works

Statement & conformance letter

Accessibility statement and letter, drafted

What our clients say

Work that holds up to review

[Real testimonial: VPAT / ACR work]
Name
Title, Organization
[Real testimonial: PDF / document remediation]
Name
Title, Organization
[Real testimonial: re-audit of another vendor's work]
Name
Title, Organization
[Real testimonial: EMS / fire-rescue client, if they agree to be named]
Name
Title, Organization
FAQ

Questions compliance, IT and legal ask

Does the Section 504 rule apply to us?

Most organizations that receive HHS funding, such as Medicare or Medicaid payments, are covered: hospitals, clinics, physician practices, community health centers, nursing, home health, hospice, dental and vision providers. Coverage depends on your funding and structure, so confirm with counsel.

Organizations with fewer than 15 employees have until May 10, 2028 to meet WCAG 2.1 AA. The duty to provide equal access, including on request, applies now.

Yes. The rule covers content delivered through contracts and vendors, and a vendor saying “accessible” isn’t enough. We test vendor tools inside your site and check their VPAT against what we find, so you have evidence to take back to them.

The May 2026 interim rule moved the technical date, not the duty to give equal access. OCR still investigates complaints today, and fixing portals, vendor tools and documents takes time.

Overlays don’t change your source code, so the barriers stay. Suits against sites using widgets ran 95 to 155 a month in 2025. We fix the underlying code and documents.

We test with test accounts in a test environment, not real patient records. We sign an NDA, and a business associate agreement if there is any chance PHI could be seen.

Get a free review of one patient journey

We test one journey, for example booking an appointment, and send a one-page summary plus a 2-minute screen reader video you can forward to leadership.