The Form That Sets the Price

Accessibility essays

What one Florida health center’s forms say about the May 2027 date, and why the sliding-fee application comes first.

Last week I sampled eight pages on a Florida community health center’s website and the five PDFs linked from them. Four of the five had no tag structure at all. The sliding-fee application was one of them.

That application is how a patient without insurance finds out what a visit will cost. It asks for household size and income, and the answer sets the discount. The words are in the file, but nothing tells software what they are. No headings, no reading order, no form fields. Read in the order the file stores it, the application starts with the office-use box in the corner, jumps to the page footer, and only then reaches the one line written for anyone who’s stuck. “If you need help filling out these forms, please let us know.”

The patients a sliding-fee scale exists for are the ones with the least room to work around a broken form. Some of them use screen readers. The document that sets their price is one they can’t fill in on their own.

What the rule says

In May 2024 the Department of Health and Human Services finalized its update to the Section 504 regulations, 45 CFR part 84. Subpart I covers web content and mobile apps: any recipient of HHS federal financial assistance has to meet WCAG 2.1 Level AA, by May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for the smaller ones. Those are the dates after HHS pushed the original deadlines back a year, so anything printed in 2024 still shows 2026.

A federally qualified health center takes a Section 330 grant from HRSA. That makes it a recipient, and no one at a health center will argue the point.

PDFs are covered too. The rule calls them conventional electronic documents, and like the ADA rule for cities and counties, it has an exception for documents posted before the compliance date. The exception stops at any document a person uses to apply for, gain access to, or take part in the recipient’s programs.

Run a health center’s forms library through that sentence. The sliding-fee application is how a patient applies for the discount. The new-patient intake packet is how a patient gets access to care. The consent and authorization forms are how a patient takes part in it. None of the three qualifies for the exception, whatever date is on the file.

People will reach for a second exception, for documents about one patient that sit behind a password, like a lab result in the portal. It’s real, and it covers that patient’s own records. It doesn’t cover the blank forms on the public site that every new patient is told to download.

Why these three are on the site

Nobody posts them by accident. Section 330 requires every health center to run a sliding-fee discount program and to tell patients it exists, and the website is where most of them do the telling. Intake packets go online because filling them out at home saves twenty minutes at the front desk.

They’re there because the health center is doing what it’s supposed to do. That’s also why they’re the documents the rule reaches first.

In the sample, the sliding-fee application runs four pages and every blank is a printed line. The intake packet runs ten, built the same way, and the consent forms live inside it. Nine sections, each with its own box to initial, and one signature at the end. One of those nine consents names the people who may hear about the patient’s care, and it covers HIV, behavioral health, and substance use treatment.

What “no tags” means at the front desk

A PDF has two layers: what you see, and a structure underneath that tells software what each part is. Heading, paragraph, list, table, form field. A screen reader reads the structure. Take it away and the reader gets text in whatever order it was drawn, or, for a scanned form, silence.

A form adds one more layer. Each fill-in box needs a label the software can read. Without one, the screen reader announces “edit text, blank,” and the patient has to guess which box is household income and which is the number of dependents. The forms in this sample don’t even get that far. The application and the intake packet have zero fill-in boxes between them, only printed lines, so the only way to complete either one is with a pen.

So the patient asks for help, which is fine, until the person helping is reading their income out loud at the front desk. Then the consent that covers HIV and substance use treatment.

I’ve filled out that clipboard in an ER waiting room, and I could at least see what I was writing. You get better privacy in a cubicle farm than at a check-in desk, and the patient who needs someone to read the form to them doesn’t even get that.

What to do with that

Start by counting. Catalog every PDF on the health center’s web properties and clinic microsites in four columns. Retire it, replace it with a web page or web form, remediate it, or leave it under the exception with a note saying why. Remediation vendors charge by the page, and the count is what turns that into a budget line instead of a guess.

Put the sliding-fee application, the intake packet, and the consent forms at the top of the list. They’re short, they’re used every day, and they’re the first documents a complaint would name.

Then look hard at whether each one should be a PDF at all. A web form built right is easier to keep accessible than a PDF someone edits in a desktop program every January when the poverty guidelines change.

And don’t count the accessibility widget in the corner of the home page as the plan. It doesn’t touch the PDFs.

May 2027 is seven months out as I write this. The tagging is the fast part. The slow part is someone on staff deciding, form by form, what each document is for.

I write Accessibility Conformance Reports and document inventories for health centers, and I don’t do the remediation. Start with the form that sets the price.

Figures are from a recon sample of one Florida community health center’s public website, run October 16, 2026, with the organization and every identifying detail removed. Eight pages and five linked PDFs, counts and verdicts as recorded, no screen reader test run. A sample, not an audit.

© Brian Beals, LLC · brianbeals.com/accessibility