NEMT website: the pages that book rides, safe booking forms, and the accessibility rules

A NEMT website does three jobs. It tells the people who book rides what you run and where, it takes a ride request without leaking health details, and it works for riders who use screen readers, keyboards, or enlarged text. The basics of getting found, from the Google profile to reviews, sit in the marketing guide. This guide covers the site itself: the pages, the notices a covered provider must post, the forms, the accessibility deadline for Medicaid providers, and what it all costs.

The pages that turn a visit into a ride request

Build the site around the questions callers already ask, one page per question, with your phone number and a request button on every page. Write for two readers: a family member arranging a ride for a parent, and facility staff such as a discharge planner or a dialysis social worker. Neither wants to dig.

• Home. The first screen names your service levels, the counties you serve, your phone number, and a “Request a ride” button. Everything else can sit lower.
• One page per service level. Ambulatory, wheelchair, and stretcher riders need different answers: what the rider must be able to do, whether an escort can come, how far the crew goes (curb-to-curb, door-to-door, or door-through-door), and the weight your lift and stretcher are rated for.
• Service area and hours. Name the counties and the hours a person answers the phone, and say so if you run early dialysis pickups or weekends. One clear page is enough. NEMT SEO explains why dozens of near-copy city pages can cost you rankings instead of earning them.
• For facilities. How staff request rides, how much notice you need, how standing orders and will-call returns work, and how invoices arrive.
• Prices, or how quotes work. If you publish prices, several states require the advertised price to include every mandatory fee. All-in pricing for ride companies covers which states and how distance-based prices comply.
• Medicaid and insurance riders. Where a state runs Medicaid rides through a broker, as 42 CFR 440.170(a)(4) allows, the broker or health plan arranges the trip, so tell members how to book through it rather than inviting calls you cannot schedule.
• Drivers. Requirements, schedule, and pay. Several states require a pay range in job postings; see pay ranges in driver job ads.
• About. Who owns the company, how long you have run, and the insurance and credentials you hold, stated plainly.

Keep federal program names factual. Saying you are an enrolled Medicaid provider is fine. Using “Medicaid,” “Medicare,” or a CMS or HHS emblem in a way that could suggest government approval is penalized under 42 U.S.C. 1320b-10, a disclaimer does not cure it, and for internet communications each viewing of the page counts as a separate violation. Naming a NEMT company covers the same rule for business names.

Notices a covered ride company must post on its site

Some pages are required, not optional, once your company is a HIPAA covered entity or takes Medicaid money.

• Notice of Privacy Practices. Under 45 CFR 160.103, a health care provider is a covered entity if it transmits health information electronically in a standard transaction, and an electronic claim is the common example. A covered entity whose website describes its customer services must post its privacy notice prominently on the site and make it available electronically there (45 CFR 164.520(c)(3)(i)). The notice has a required header that begins “THIS NOTICE DESCRIBES HOW MEDICAL INFORMATION ABOUT YOU MAY BE USED AND DISCLOSED.”
• Section 1557 notices. The notice of nondiscrimination belongs in a conspicuous location on the website (45 CFR 92.10), and so does the notice that free language help is available. Language access in NEMT covers what both must say.
• State privacy notices. Some states add website notices of their own for health information. State privacy laws stricter than HIPAA covers Texas and Washington.
• A way to report accessibility problems. No rule names it, but the Justice Department’s web guidance lists a public channel for reporting barriers among the practices that help, and it gives you a chance to fix a problem before it becomes a complaint.

Link all four from the footer so they appear on every page.

Booking forms that ask about health

A request form that asks about a wheelchair, oxygen, or the appointment is collecting health information. If your company is a covered entity, any outside company that receives, stores, or sends that information for you is a business associate under 45 CFR 160.103, and you need a signed business associate agreement with it before the first request comes in.

Map where a submission actually travels. On a typical builder site it can land in three places: the website builder’s form database, the inbox that receives the notification email, and any app that copies it into a spreadsheet. Each one holds rider information. If a vendor will not sign an agreement, take the health questions off its forms and ask them by phone. Some form tools keep HIPAA features for their upper plans: Jotform, for example, offers them only on its Gold and Enterprise plans, not on its free plan.

Ad and analytics tags are the other leak. In June 2024 a federal court in Texas (American Hospital Association v. Becerra) vacated one part of HHS’s guidance on tracking technologies, the part saying HIPAA applies when a tag links a visitor’s IP address with a visit to a public page about specific health conditions or providers, and the court wrote that its ruling should not be read as limiting the rest of the guidance. The online booking guide lists the safeguards for request pages, and Google Ads for NEMT shows how to count bookings without sending form contents to an ad platform.

Not every ride company is a covered entity. A private-pay company that never bills electronically may sit outside HIPAA and inside state health data laws instead, which the state privacy guide above covers.

Accessibility: three rules, one deadline

Your website has to work for riders with disabilities under three overlapping rules, and only one of them sets a technical standard with a date.

1. The ADA. In guidance dated March 18, 2022, the Justice Department takes the position that the ADA reaches what a public-facing business offers through its website. There is no regulation spelling out a technical standard for private businesses, so the guidance names WCAG and the Section 508 standards federal agencies follow as useful references.
2. DOT’s ADA transportation rule. 49 CFR 37.167(f), which applies to private as well as public transportation providers, requires adequate information about your service for riders with disabilities, including the communications capacity, in accessible formats and technology, to get information and schedule rides. For a ride company, the website is part of that capacity.
3. HHS’s Section 504 web rule. 45 CFR 84.84 requires recipients of HHS funding to meet WCAG 2.1 Level A and AA success criteria for the web content and mobile apps they offer, directly or through contracts and licenses. An interim final rule published May 11, 2026 moved the dates back one year: May 11, 2027 for recipients with 15 or more employees, and May 10, 2028 for smaller ones.

Whether the third rule reaches you depends on the money. HHS defines a recipient as anyone receiving its funding directly or through another recipient, its 2024 rule says Section 504 duties pass down to the contractors who carry out a funded program, and the Fifth Circuit held in 1984 that Medicaid is federal financial assistance under Section 504. A company paid with Medicaid dollars, directly or through a broker or health plan, should plan to be covered. HHS also says that, deadlines aside, recipients already have an ongoing duty to make their online services accessible.

The rule has narrow exceptions in 45 CFR 84.85:

• PDFs and other documents posted before your compliance date, unless people still use them to request or receive service. A PDF trip request form in daily use gets no pass.
• Content a third party posts on its own, such as a review, but not content a vendor posts for you under contract.
• Documents about one person behind a password, such as a rider’s invoice in a portal.
• Pages created before your compliance date and kept unchanged in a marked archive purely for reference, and social posts made before that date.

If full conformance would be an undue burden, the head of the company or a designee has to decide that in writing after weighing all available resources, and the company must still do as much as possible short of that burden (45 CFR 84.88).

What WCAG 2.1 Level AA asks of a ride company’s site

Most of the work comes down to a handful of checks, each tied to a numbered success criterion:

• Contrast. Body text at least 4.5:1 against its background, and 3:1 for large text (1.4.3). Pale grey text on white often fails.
• Zoom and small screens. Text readable at 200 percent (1.4.4), and pages that fit a 320-pixel-wide view without sideways scrolling (1.4.10).
• Images and video. Alt text that says what a van or ramp photo shows (1.1.1), and captions on any video tour (1.2.2).
• Keyboard. Every link, menu, and button usable without a mouse (2.1.1), with a visible outline showing where you are (2.4.7).
• Forms. Labels and instructions on every field (3.3.2), errors named in text (3.3.1), and a suggested fix when one is known (3.3.3). The online booking guide covers form layout in detail.

The Justice Department’s guidance warns that automated checkers and overlay plugins need careful use, because a report with no errors can still miss real barriers. Pair a scan with a manual pass: tab through the request form, zoom to 200 percent, and listen to the home page with a screen reader.

What a NEMT website costs

For a small fleet the cash costs are modest. The larger cost is the time to write pages that answer real questions and to check them against WCAG.

• A website builder. Squarespace’s Basic plan, as one example, costs $25 a month billed monthly or $19 a month billed annually, and annual plans come with a free first year of registration for an eligible domain.
• A form tool that signs a business associate agreement, if you collect health details online and are a covered entity. Price the tier that includes the HIPAA features, not the entry plan.
• Design help, if you hire it. HHS’s 2024 rule makes clear that hiring someone else to build the site does not shift the provider’s Section 504 duties to them. Write WCAG 2.1 Level AA conformance into the contract, keep the domain and the builder account in the company’s name, and ask for the designer’s test results before the final payment.

An example: an owner who builds the site on an annual builder plan pays $228 for the first year ($19 × 12) plus whatever the form tool’s HIPAA tier costs. A designer’s quote replaces most of the owner’s hours but none of the owner’s responsibility.

After the website does its job

The website’s job ends when a request arrives, and that is where HealthRide picks up. Families and riders can book online, then watch the driver approach on a live map from a link sent by text. Each facility gets its own login to request rides and track them. HealthRide is HIPAA compliant, and each person sees only what their role allows. See the live map.