Forms are where PDF accessibility goes wrong most often. A report with weak tagging is annoying; a form that a screen reader user cannot complete locks them out of a service entirely. With the European Accessibility Act applying and ADA Title II rules covering public bodies in the US, inaccessible forms are a compliance risk as well as a usability one.
Use this checklist when building or reviewing a fillable PDF.
Structure
1. Every field is a real form field. A line to "write on" is not a field. Use proper text fields, checkboxes, radio buttons and dropdowns. See PDF form field types explained.
2. The document is tagged, and each field is associated with its tag in the structure tree. Fields that exist only as widgets may be skipped by assistive technology.
3. The tab order follows the visual order. Set tab order to "use document structure" and test it: press Tab from the top and watch the focus move. Jumps between columns are the most common failure.
Labels and instructions
4. Each field has a tooltip (accessible name). Screen readers announce the tooltip, not the printed text next to the field. "Text1" is a failure; "Date of birth (DD/MM/YYYY)" is a pass.
5. Required fields say so in the tooltip and visually, not only with a red asterisk or colour.
6. Format instructions are in the label, for example "Phone number, digits only". Do not rely on placeholder text, which disappears.
7. Radio button groups have a group name that states the question, and each button has its own label.
Interaction
8. Targets are large enough. Checkboxes and radio buttons should be at least 24 by 24 pixels, as WCAG 2.2 requires. See WCAG 2.2 and PDFs.
9. No retyping. If the same information is needed twice, fill it automatically by using the same field name.
10. Validation messages are clear and say how to fix the problem. "Invalid entry" is not enough. See how to add validation to a PDF form.
11. No time limits, and no scripts that move focus unexpectedly.
Final checks
12. Test with a keyboard and a screen reader. Complete the whole form without a mouse, then with NVDA or VoiceOver. If you get stuck, so will your users.
Common mistakes to avoid
- Flattening the form before sending. Flattening removes the fields entirely. See how to flatten a PDF.
- Scanned forms with fields drawn on top. The printed text is an image, so labels are unreadable. Rebuild the form from source.
- XFA forms, which many readers and assistive technologies do not support. See XFA forms explained.
- Signature fields with no alternative. Offer a way to sign that works with assistive technology, such as a typed signature.
Offer an alternative
Even a good PDF form is harder to use than a well-built web form for many people. If you can, offer an accessible online form or another way to submit the same information, and say so at the top of the PDF.
Takeaway
A form is accessible when someone can complete it with a keyboard and a screen reader, without guessing. Name every field, fix the tab order, make targets large and test it yourself. For building the form in the first place, see how to create a fillable PDF form, and for the broader rules see the European Accessibility Act checklist.
