How Do I Make a PDF Form Accessible?

To make a PDF form accessible, every form field must have a descriptive label, a logical tab order, and clear instructions that assistive technologies can read aloud. Accessible PDF forms go beyond visual design — they require proper tagging, programmatic labels, and thoughtful error handling so that users navigating with screen readers, keyboards, or alternative input devices can complete them independently.

PDF forms are among the most common documents in higher education — enrollment applications, financial aid requests, course evaluations, accommodation forms — yet they are also among the most frequently inaccessible. A visually clean form can be completely unusable for someone relying on a screen reader if the underlying structure is missing.

Why PDF Forms Need Special Attention

Standard PDF accessibility practices like tagging your PDF and adding alt text to images are necessary but not sufficient for forms. Interactive form fields introduce a layer of complexity that static documents do not have. Each field is an interactive element that must communicate its purpose, its current state, and any constraints to the user — all without relying on visual cues alone.

Under WCAG 2.1 (and the DOJ's ADA Title II requirements taking effect in 2026), form fields must meet several success criteria, including labels or instructions (1.3.1, 3.3.2), keyboard accessibility (2.1.1), and error identification (3.3.1). Failing on any of these means your form creates a barrier.

Form Field Labels and Tooltips

Every form field — text input, checkbox, radio button, dropdown — needs a programmatic label that a screen reader can announce. Visual labels alone are not enough. In Adobe Acrobat Pro, this is set through the Tooltip property in each field's settings.

The tooltip should match or closely mirror the visible label. For example, if the visible label says "Student ID Number," the tooltip should read "Student ID Number," not "Field 3" or "Enter text."

Best practices for labeling:

• Be specific. Use "Date of Birth (MM/DD/YYYY)" rather than "Date."
• Include format hints. If a phone number requires a specific format, state it in the tooltip.
• Label every field. Even fields that seem obvious (like a single text box next to the word "Name") need programmatic labels.
• Group related fields. Radio buttons and checkboxes that belong together should share a group label explaining the question they answer.

Tab Order

Sighted users scan a form visually and fill it in a predictable order. Keyboard and screen reader users navigate field by field using the Tab key. If your tab order does not follow the visual reading order, users will jump unpredictably around the page, making the form confusing or impossible to complete.

In Acrobat Pro, set tab order by opening the Fields panel and arranging the fields in the correct sequence. For multi-page forms, verify the order across page breaks. A common mistake is adding fields during editing without updating the tab order afterward — always recheck after making changes.

Required Field Indicators

Marking required fields with a red asterisk is a widespread convention, but it fails accessibility on two levels. First, color alone cannot convey information (WCAG 1.4.1). Second, the asterisk is meaningless unless its purpose is explained somewhere on the form.

To handle required fields accessibly:

• Add "(required)" to the field's tooltip label.
• Include a note at the top of the form explaining any symbols used, such as "Fields marked with * are required."
• Use the "Required" property in Acrobat Pro's field settings so the form enforces completion before submission.

Error Messages and Validation

When a user submits a form with errors, the feedback must be clear, specific, and accessible. "There was an error" is not helpful. "The email address field is empty. Please enter your university email address." is.

For accessible error handling:

• Identify the specific field that has the error.
• Describe what went wrong and how to fix it.
• Make sure error messages are announced by screen readers, not just displayed visually.
• Do not rely solely on color changes (like turning a field border red) to indicate errors.

Creating Forms in Word First

If you are starting from scratch, consider building your form structure in Microsoft Word before converting to PDF. Word's built-in form controls (found under the Developer tab) carry over more cleanly into tagged PDF form fields than forms built entirely in Acrobat. This approach also gives you a more accessible source document for future edits.

After exporting to PDF, open the file in Acrobat Pro to verify that all fields, labels, and reading order transferred correctly. Some manual cleanup is usually necessary, but starting in Word reduces the amount of remediation work significantly. For more on the full process, see our guide on how to make a PDF accessible.

Testing with Screen Readers

No form should be published without testing. The most reliable way to verify form accessibility is to navigate it with a screen reader:

• NVDA (free, Windows) or JAWS (Windows) for desktop testing.
• VoiceOver (built into macOS and iOS) for Apple devices.

Tab through every field and listen. Can you tell what each field is asking for? Do you know which fields are required? Does the tab order make sense? Can you understand the error messages? If the answer to any of these is no, the form needs more work.

Common Form Accessibility Mistakes

• Flattened forms. Saving a filled-in form as a static PDF removes all interactive fields. The result looks like a form but cannot be filled in by anyone.
• Scanned paper forms. A scan of a paper form is just an image. It has no form fields, no tags, and no text layer. These must be fully rebuilt.
• Missing tooltips. The single most common issue. Fields exist but have no programmatic labels.
• Inconsistent naming. Tooltips that do not match visible labels create confusion for speech-input users who say "click Student Name" but the tooltip reads "txtField_01."
• Ignoring tab order after edits. Adding or rearranging fields without updating tab order breaks the navigation sequence.

Simplify Form Remediation

Fixing form accessibility manually in Acrobat Pro is effective but time-consuming, especially when departments manage hundreds of PDF forms across courses and programs. Aelira's document remediation platform can scan your PDF forms, flag missing labels, broken tab order, and inaccessible error handling, and auto-remediate common issues — helping your team bring forms into compliance faster without sacrificing quality.