Section 504 Website Accessibility for NEMT in 2027: The HHS Rule, WCAG 2.1, and Deadlines

Many rides now start on a screen. A case manager checks your service area on a laptop, a daughter fills out your ride request form on her phone, and a rider who is blind uses a screen reader to find your hours. If the form cannot be read aloud or submitted without a mouse, that rider cannot book with you. Section 504 of the Rehabilitation Act, and the HHS rule that applies it to websites and apps, turns that into a legal duty with a date on it.

Does Section 504 apply to a NEMT company’s website?

Section 504 bars disability discrimination in any program that receives federal financial assistance. HHS’s rule for the programs it funds is 45 CFR part 84, and its web and mobile app section, subpart I, applies to every program or activity that receives HHS assistance (84.82).

The rule reaches further than a direct grant. A recipient is any entity that receives federal financial assistance “directly or through another recipient” (84.10). In its May 9, 2024 final rule, HHS said state Medicaid programs are covered and so are the Medicaid health plans they pay, citing a federal appeals court holding that Medicare and Medicaid are federal financial assistance for Section 504. The same rule says that when a recipient contracts out work under its program, the duties pass down to the subcontractor. If Medicaid pays for your rides, whether through the state, a health plan, or a broker, plan as though the rule covers your website and apps.

It can cover more than your Medicaid work. For a private company principally engaged in health care or social services, HHS counts all of its operations as the program (84.10). Treat your private pay booking page the same as your Medicaid one. See private pay NEMT.

Broker contracts can require it too. Section 2.U of MTM Health’s provider agreement, in the January 1, 2023 version posted by Pennsylvania’s Department of Human Services, lists Section 504 among the laws you must follow. If your rides involve no HHS money at all, this rule does not reach you, but the ADA still can. See ADA requirements for NEMT.

The standard: WCAG 2.1 Level AA

The rule names one technical standard: the Web Content Accessibility Guidelines 2.1, the W3C Recommendation of June 5, 2018. Your web content and mobile apps must meet its Level A and Level AA success criteria and conformance requirements (84.84). Web content includes text, images, sound, video, buttons, form controls, and documents such as PDFs, Word files, and spreadsheets. Mobile apps are the apps people download to phones and tablets.

Three more rules shape what you must do:

• Vendors do not take it off your plate. The duty covers content and apps you provide or make available “directly or through contractual, licensing, or other arrangements.” HHS said recipients cannot delegate it away, and that “makes available” includes a third party that operates or supplies the content for you, such as a hosted booking form.
• A phone line is not an alternative. HHS said a phone line, even one staffed 24 hours a day, cannot realistically give equal access, because a website lets people get information or request service in minutes and on their own. A separate accessible version of content is allowed only when technical or legal limits make the main version impossible to fix (84.86).
• Tiny misses can be forgiven. If a gap is so small that it does not keep anyone from getting the same information, completing the same transactions, or using your service with the same speed, privacy, and independence, you are treated as meeting the rule. You must be able to show it (84.89).

There is also a defense when full conformance would cause undue financial and administrative burdens or fundamentally change your service. The owner or a designee must decide it after considering all available resources and put the reasons in writing, and you still have to do everything short of that burden (84.88). In May 2026, HHS said it had meant the defense for rare situations but now believes many small recipients may argue it.

Deadlines after the May 2026 extension

HHS’s 2024 rule took effect July 8, 2024, with two compliance dates based on company size. An interim final rule published May 11, 2026 and effective May 7, 2026 moved both back one year (91 FR 25496). Companies with 15 or more employees now have until May 11, 2027, instead of May 11, 2026. Smaller companies have until May 10, 2028, instead of May 10, 2027.

HHS took comments on the extension through July 6, 2026. It said it may propose changes to the substance of the rule during the extension, and that if it does not, and nothing else calls for more delay, it expects to put the rule in force on the new dates. Plan on those dates, and watch the Federal Register for any proposal.

The extension moved only the WCAG deadline. HHS said the delay does not relieve recipients of their other Section 504 duties, and that recipients “have an ongoing obligation” to make what they offer through websites and apps accessible under those duties. The next section lists them.

The duties that apply right now

These rules are in force today, whatever your size:

• Reasonable modifications. Change a policy, practice, or procedure when a rider with a disability needs it, unless the change would fundamentally alter your service (84.68(b)(7)). If a rider cannot use your online form, take the request another way that works for them, and fix the form.
• Effective communication. Communication with riders, applicants, and companions with disabilities must be as effective as with anyone else. Give primary consideration to the aid the person asks for, and provide it in an accessible format, on time, and in a way that protects their privacy and independence (84.77).
• Phones and relay calls. Answer calls from a telecommunications relay service the same way you answer any other call. If you use voicemail or a phone menu, it must work for callers using text telephones and relay services (84.78).
• Booking information for every rider. Under the Transportation Department’s ADA rules, a company running rides must give riders with disabilities adequate information, including communications capacity in accessible formats and technology, so they can get information and schedule service (49 CFR 37.167(f)).
• The Section 1557 rule. HHS’s rule under the Affordable Care Act requires covered health programs offered through information and communication technology to be accessible, unless that would be an undue burden, and points recipients’ websites and apps to Section 504 read consistently with title II of the ADA (45 CFR 92.204).
• A coordinator and a grievance process. A recipient with 15 or more employees must name a person to coordinate Section 504 compliance and adopt a grievance procedure (84.7). Every recipient must tell riders and staff about their Section 504 rights (84.8), and HHS can require a smaller company to follow 84.7 after finding a violation (84.9).

The Justice Department’s guidance of March 18, 2022 says the ADA’s rules apply to what businesses open to the public offer online. It points to WCAG as helpful guidance.

What the rule leaves out

The rule lists five exceptions (84.85). Read them narrowly:

1. Archived content. Material created before your compliance date, kept only for reference or records, never changed after archiving, and stored in an area clearly marked as an archive. A page you still update is not archived.
2. Older documents. PDFs, Word files, slides, and spreadsheets posted before your compliance date, unless people currently use them to apply for, sign up for, or take part in your service. A ride request form, a rider agreement, or a facility intake sheet still in use must be accessible. Anything you post after the date is covered.
3. Content posted by others. Comments or reviews the public posts on your page, unless someone posts them for you under a contract.
4. Private documents. A document about one person, their property, or their account, kept behind a password or otherwise secured, such as a trip receipt in a rider portal. Give it to that rider in an accessible format when they ask.
5. Old social media posts. Posts you made before your compliance date.

What a small NEMT site should fix first

Start where riders book. Each item below names the WCAG 2.1 success criterion and its level:

1. Ride request and contact forms. Every field has a visible label or instructions (3.3.2, A). Errors are named in text, not only by color (3.3.1, A), with a suggested fix where you can give one (3.3.3, AA). Fields that ask for the user’s name, phone, or address are coded for their purpose so browsers can fill them in (1.3.5, AA). Every button and control has a name assistive technology can read (4.1.2, A).
2. Time limits. If a form times out, let the user turn the limit off, extend it, or adjust it (2.2.1, A). A rider booking with a screen reader may need longer.
3. Keyboard use. Everything works with a keyboard alone (2.1.1, A), and the user can always see where the keyboard focus is (2.4.7, AA).
4. Images and icons. Photos of your vans and staff, logos, and icon buttons have text alternatives that serve the same purpose (1.1.1, A).
5. Readable on a phone. Normal text has a contrast ratio of at least 4.5 to 1 against its background, and large text 3 to 1 (1.4.3, AA). Text can be enlarged to 200 percent without losing content (1.4.4, AA), and pages work at a width of 320 CSS pixels without scrolling sideways (1.4.10, AA).
6. Video. Any prerecorded video with sound, such as a how to book video, has captions (1.2.2, A).
7. Documents in use. Rebuild your rate sheet, ride request form, and service area map as accessible web pages, or as accessible documents. A scan of a paper form is an image a screen reader cannot read.
8. Page basics. Every page has a title that says what it is for (2.4.2, A) and declares its language (3.1.1, A), and information is structured with real headings and lists (1.3.1, A).

Then ask your website and app vendors in writing whether their products meet WCAG 2.1 Level AA, and put that requirement in any new contract. Booking forms also collect health information, so check the privacy rules in HIPAA for NEMT providers, and keep the basics from building a website that answers the first call in place while you fix the code.

How complaints reach HHS

Anyone who believes they faced disability discrimination can file a written complaint with the HHS Office for Civil Rights, alone or through a representative. Section 504 complaints follow the procedures in 45 CFR 80.6 to 80.10 and part 81 (84.98). Under them:

1. The complaint is due within 180 days of the alleged discrimination, unless HHS extends the time (80.7(b)). It can be filed online through the OCR complaint portal.
2. OCR investigates and, if it finds a failure to comply, tries to resolve it informally (80.7(c) and (d)).
3. If that fails, HHS can move to suspend or end federal financial assistance, or refer the matter to the Justice Department (80.8).
4. Retaliation is barred. You may not threaten or punish anyone for complaining or taking part in an investigation (80.7(e)).

Log every accessibility complaint with the date, what the rider could not do, and how you fixed it, using a complaint log. If OCR or a broker asks, you have the facts in one place.