A Section 504 website checklist for practice managers

Confirm you're covered, list everything patients use, test it against WCAG 2.1 AA by machine and by hand, ask your vendors, fix or rebuild, publish a statement and keep a dated record. For a practice with 15 or more employees, start now to finish comfortably before 11 May 2027.

Written by the nextwebsite.co team, and last checked on November 9, 2026.

Who this is for

Practice managers, administrators and compliance leads at providers that take Medicare or Medicaid, who have been asked to get the website ready for the Section 504 deadline. The current dates are 11 May 2027 for providers with 15 or more employees and 10 May 2028 for smaller ones1.

1. Confirm you're covered, and count your employees

Write down which HHS programs pay you and how many people you employ. Medicaid, CHIP and Medicare Part A bring you in, and HHS treats Medicare Part B as federal financial assistance too2. Our guide does Section 504 apply to my practice? goes through it.

2. List everything patients use

The rule covers what you provide through vendors as well as your own pages1. List the website, online booking, intake and registration forms, bill pay, the portal and any telehealth or chat tool, with the vendor for each.

3. Check each one against WCAG 2.1 AA

Run an automated check on every page, then have a person try the important journeys with only a keyboard and with a screen reader: finding a location, booking, and filling in the intake form. Automated tools find only about 57% of accessibility issues3. Meeting WCAG 2.2 AA covers 2.1 AA4.

4. Ask your vendors

For each vendor, ask whether their product meets WCAG 2.1 AA, for their accessibility conformance report, and how fast they fix reported problems. Keep the answers.

5. Fix or rebuild

If the problems are in a few pages, fix them. If they're in the templates, the page builder or the forms, a rebuild is usually faster and lasts longer. Replace PDF intake forms with accessible web forms where you can. Don't rely on an overlay widget: the FTC has acted against one vendor for claiming its tool could make any site comply with WCAG5.

6. Publish an accessibility statement

One page that says which standard you aim for, how patients can report a problem, and how quickly you'll respond.

7. Keep a dated record

What was tested, when, how, what was found and what was fixed, plus each vendor's answers. It's what you'll show your administrator, and anyone who asks.

A timeline back from May 2027

  • Now to January: steps 1 to 4.
  • February: choose who does the work, and agree a launch date with time to spare.
  • March and April: build, test and fix.
  • Early May: publish the statement and file the record.

Smaller practices have until 10 May 2028, and can follow the same steps at a calmer pace1. The dates have moved once already6, so check them again before you rely on them. Our free check is a quick way to start step 3.

This guide is general information, not legal advice.

Checklist

  1. Confirm you're covered, and count your employees.
  2. List everything patients use, with the vendor for each.
  3. Check each one against WCAG 2.1 AA, by machine and by a person.
  4. Ask your vendors for their accessibility reports.
  5. Fix or rebuild, and replace PDF intake forms with web forms.
  6. Publish an accessibility statement.
  7. Keep a dated record of what was tested and fixed.

Check your own site

The free scan checks your pages for the accessibility problems a machine can find, and marks the checks that need a person. It takes under a minute.

Free, takes under a minute, and only reads what any visitor can see.

Or run just this check: the accessibility checker.

Read next

More on section 504 for healthcare, and what we build for medical practices, dental clinics and home health and hospice.