Prepare for the HHS Section 504 Deadline: Turn PDF Patient Intake Forms into Mobile Web Forms Built to Support WCAG 2.1 AA
Clinics, hospitals, and practices that receive federal funds are expected to make their web content and patient forms usable by people with disabilities. ToWebForm turns each intake, consent, and history PDF into a web form patients can finish on a phone, and your front desk still receives the exact PDF it files today.
The problem: Patients receive a link to a fillable PDF packet that is hard to read on a phone and hard to use with a screen reader. Staff end up re-typing paper copies at check-in, and the practice carries the accessibility risk.
or drag and drop any PDF here to detect fields automatically
No account required · Test your web form, switch languages, and download the filled PDF
01 / At a Glance
How ToWebForm Replaces PDF Form Remediation
The HHS Section 504 final rule requires recipients of HHS federal financial assistance, including many hospitals, clinics, and practices that bill Medicare or Medicaid, to make web content and mobile apps conform to WCAG 2.1 Level AA. Recipients with 15 or more employees must comply by May 11, 2027, and recipients with fewer than 15 employees by May 10, 2028. Downloadable patient forms are part of that web content.
ToWebForm converts patient intake, consent, medical history, and release forms into semantic HTML web forms built to support WCAG 2.1 AA. Patients complete them on any phone with a screen reader, keyboard, or large text, and each submission is stamped onto the exact coordinates of the original PDF, so the chart, EHR upload, and billing team receive the same document as before.
Submission data, signatures, and uploaded insurance cards are encrypted with AES-256-GCM, and completed PDFs are shared only through time-limited signed links. Patients can choose from 18 supported languages (active languages depend on your plan), with answers translated back for your staff on every plan, including Free. Team plans can use Zero-Storage Fill and Download mode when the practice should not store answers at all.
Key Facts
- HHS Section 504: WCAG 2.1 AA by May 11, 2027 for recipients with 15 or more employees
- Fewer than 15 employees: May 10, 2028
- Patients use a responsive web form instead of a fixed PDF packet
- Answers are stamped onto your original intake and consent PDFs
- AES-256-GCM encryption, signed download links, and an ESIGN and UETA signature audit trail
- Language access: patients choose from 18 supported languages (active languages depend on your plan)
1. Upload the PDF you already use
Interactive AcroForms and flat or scanned PDFs both work. Fields, labels, and coordinates are detected automatically.
2. Respondents fill out a semantic web form
Single-column HTML built to support WCAG 2.1 AA, with labels, fieldset groups, keyboard focus order, and screen-reader status messages.
3. Your team receives the original PDF
Answers are stamped onto the exact coordinates of the original document, encrypted with AES-256-GCM, and ready for your existing process.
02 / Side-by-Side Comparison
Manual Acrobat Tagging vs. Remediation Agencies vs. ToWebForm
Three ways to handle an inaccessible PDF form, compared on cost, phone use, assistive technology, maintenance, language access, and data handling.
| Criterion | Manual Acrobat Pro Tagging | PDF Remediation Agencies ($25 to $75/page) | ToWebForm |
|---|---|---|---|
| A multi-page new patient packet | Every page of the packet needs tags, tab order, and field tooltips, then testing in several PDF readers | Billed per page for the whole packet, and again whenever a consent form changes | Upload each PDF once. Patients finish one web form per document, or one Smart Packet for the set on Starter and above |
| Cost model and turnaround | Staff time: often 1 to 3 hours per complex form to build and verify the tag tree, reading order, and field tooltips | Commonly quoted at $25 to $75 per page, with turnaround measured in days or weeks per batch | Flat monthly plan with unlimited standard submissions. Upload a PDF and get a working web form in seconds |
| Phone use (WCAG 1.4.10 Reflow) and touch targets | Still a fixed 8.5x11 page. Respondents pinch, zoom, and scroll sideways on a 320px screen | Same fixed page layout. Tags help screen readers but do not make the page reflow on phones | Single-column responsive HTML that reflows at 320px with 48x48px minimum touch targets |
| Screen reader and keyboard use (WCAG 1.3.1, 2.1.1, 4.1.3) | Depends on tag quality and the PDF reader. Mobile screen readers often read fields out of order | Usually tested in desktop Acrobat with JAWS or NVDA. Mobile reader behavior varies | Semantic labels, fieldset and legend groups, visible focus rings, linked error messages, and ARIA live status regions |
| When one line of the form changes | Re-exporting from Word or InDesign drops the tags, so the file must be re-tagged and re-checked | Send the file back and pay the per-page rate again | Edit the label, help text, or screen-reader hint in the builder. No re-remediation of the PDF |
| Multilingual and Title VI LEP access | Translate, re-typeset, and re-tag a separate PDF for every language | Each translated PDF is a new remediation job billed per page | One link where respondents choose from 18 supported languages (active languages depend on your plan), including right-to-left Arabic and Urdu. Bidirectional translation stamps English answers onto your original PDF on every plan, including Free |
| Back-office output and PII retention | Respondents email or upload the filled PDF, which then sits in inboxes | Same as manual tagging. The workflow after remediation does not change | Answers are stamped onto the exact coordinates of the original PDF and encrypted with AES-256-GCM. Team plans can enable Zero-Storage Fill and Download mode so no respondent PII is stored |
Agency rates reflect commonly quoted per-page pricing for form remediation and vary by vendor, document complexity, and turnaround.
03 / Language Access and Privacy
Beyond Accessibility: Language Access and Zero-PII Options
Bidirectional Answer Translation
Title VI language access · 18 supported languagesRespondents choose from 18 supported languages (active languages depend on your plan), including right-to-left Arabic and Urdu. They answer in their own language, and open-text answers are translated back into your PDF language before stamping, with both versions kept in a Bilingual Verification Log. Included on every plan, including Free.
Zero-Storage Fill and Download Mode
No respondent PII retained · TeamFor court, records, and resident forms where you should not hold the data. Respondents complete the web form, and the official stamped PDF is generated in memory and streamed straight to their browser. No answers are written to the database.
Accessibility Overrides Workbench
Per-field controlAdjust ARIA labels, screen-reader hints, helper text, error messages, autocomplete tokens, and high-contrast colors on any field without touching the source PDF.
See every success criterion mapped to its implementation in the WCAG 2.1 AA technical conformance matrix.
For agencies and consultants
Remediating PDF forms for clients? Convert the whole library instead of tagging it page by page
Web, digital, and accessibility agencies use the ToWebForm Team plan to turn a client's PDF form library into web forms built to support WCAG 2.1 AA in an afternoon, then keep those forms current without re-billing per page. Your client still receives the original PDF for every submission.
A workspace per client
Keep each client’s forms, submissions, and team access separate in Multiple Workspaces.
Their domain, their brand
Publish on a custom subdomain such as forms.yourclient.com with White-Label Branding and no ToWebForm badge.
5 seats included
Give your team and the client’s staff role-based access as Owner, Admin, or Member, and add seats as you grow.
Zero-Storage when required
Turn on Zero-Storage Fill and Download mode for clients whose respondents’ answers must not be stored.
03 / PRICING & PLANS
Simple, transparent pricing
Start free with unlimited submissions. Upgrade when you need more forms, languages or signers; your forms carry over.
04 / FAQ
Frequently Asked Questions
Answers on cost, deadlines, workflow changes, privacy, and what ToWebForm does and does not guarantee.
Who has to meet the HHS Section 504 web accessibility rule?
When are the HHS Section 504 deadlines?
Will our front desk and EHR workflow change?
How is patient information protected?
Does using ToWebForm make our practice compliant with Section 504?
More Accessibility Guides
All solutions →PDF Form Remediation
Skip per-page PDF form remediation. Convert legacy PDFs into web forms built to support WCAG 2.1 AA, and get answers stamped back onto your original PDF.
ADA Title II PDF Forms
Help your city, county, or school district meet DOJ ADA Title II web rules. Turn agency PDF forms into web forms designed for WCAG 2.1 AA.
Section 508 PDF Forms
A Section 508 PDF form alternative: semantic HTML web forms built to support WCAG 2.1 AA that stamp answers back onto your original PDF.
WCAG 2.1 AA PDF Forms
Convert flat or scanned PDFs into mobile web forms built to support WCAG 2.1 AA, with 320px reflow, 48px touch targets, and answers stamped on your PDF.
Australia: DDA and DSS
Replace downloadable PDF forms with responsive web forms built to support WCAG 2.1 AA for Australian agencies and businesses, with your original PDF as output.
UK: PSBAR and GDS
Publish HTML forms instead of fillable PDFs, as GDS advises. For UK councils, NHS trusts, and universities, with your original PDF stamped as the record.
Canada: AODA and ACA
Turn PDF forms into web forms built to support WCAG 2.1 AA for AODA and the Accessible Canada Act, with English and French translation and your original PDF.
EU: EAA and EN 301 549
Turn PDF forms into multilingual web forms built to support EN 301 549 and WCAG 2.1 AA for the European Accessibility Act, in 18 supported languages.
Accessibility Overview
Federal deadlines, the full WCAG 2.1 AA conformance matrix, and Title VI language access.
Try it on one of your own PDFs
Upload a form in the live demo above, or compare plans on the homepage.
ToWebForm's web form renderers are built to support WCAG 2.1 Level AA technical standards and engineered to help organizations meet DOJ ADA Title II, Section 508, HHS Section 504, and ADA Title III web accessibility requirements. Because end-user accessibility is a shared responsibility that depends on how forms are authored, labeled, configured in the Accessibility Overrides Workbench, and embedded within external websites, Foresight Technologies LLC does not warrant or guarantee that any specific customer form achieves full regulatory compliance. Regulatory dates and agency pricing on this page are provided for general information and are not legal advice. Review our full Accessibility & Shared Responsibility clause in our Terms of Service.