PDF · THE NO-PANIC PLAN
Create and test an accessible fillable PDF form
Turn an approved blank document into a tagged, fillable PDF form that can be understood and completed with a keyboard and assistive technology. Automated checks help find issues, but field names, reading order and error behavior require hands-on testing; a passing preflight alone is not proof of WCAG conformance.
MISSION create and test an accessible fillable pdf form
Start this workflowTHE REAL-WORLD BIT
What happens outside this browser tab?
Plan the audience and fields, preserve accessible structure, create and label interactive controls, run a bounded preflight and repair its findings, then test the complete form by keyboard and screen reader before release.
YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES
One step at a time.
Follow the order below. If a step names a Nirmion tool, its link is right there with it.
- 01
Define the form task, fields and safe source copy
Start from the owner-approved blank source form and record its purpose, audience, submission route and document version. List each field, its visible label, expected type/format, whether it is truly required, and any group or instruction. Use the document authoring source where possible because a well-structured source can carry headings and reading order into the PDF. Keep an untouched master. Do not use a completed form containing personal or confidential data as the test file.
- 02
Prepare the document structure before adding fields
Use a clear title, descriptive section headings, the correct document language and a logical reading sequence. In Acrobat Pro, run Prepare for Accessibility, review the tags and correct the reading order; do not accept auto-tagging without inspection. Keep form prompts and visible labels close to their controls. W3C PDF techniques are examples, not a complete conformance test: use the applicable accessibility standard and organizational requirements for the actual acceptance decision.
- 03
Create well-named controls, instructions and tab order
In Acrobat, choose All tools > Prepare a form and add or correct each text field, checkbox, radio group, list, button or signature control. Give every control a meaningful tooltip/accessible name that identifies its purpose and includes its visible label; use button labels for push buttons. Mark only genuinely mandatory fields as required and explain that status in visible text, not color alone. Put the expected format in the label/instructions (for example, ?Date (YYYY-MM-DD)?) and provide a useful error message for invalid input. Set the tab order to follow the tag/reading structure and verify it visually; the W3C PDF12 technique identifies tooltip as the name exposed to assistive technology and recommends checking name, role and value with a screen reader or equivalent tool.
- 04
Run automated checks and repair observable issues
Run Acrobat Pro?s Check for Accessibility, review every Failed, Skipped and Needs Manual Check result, repair the applicable items, and rerun the check. Inspect tags, reading order, document language, labels, required fields, keyboard order, links and alternate text; automated success does not replace manual checks. Nirmion PDF Accessibility Preflight can report observable signals such as title/language metadata, text presence and link counts by page. It does not inspect the tag tree, form-field names/roles, reading order or WCAG conformance. The tool sends the supplied PDF to Nirmion?s PDF processing service, so use only a public blank template or another file explicitly approved for this processing; never submit completed personal or confidential forms.
- 05
Test the actual user path and save a controlled release copy
With the blank template, navigate every field using keyboard only and confirm focus order, announced name/type/state, grouping and instructions. Complete a sample using synthetic data; test required-field and invalid-format errors, radio/checkbox selection, save/print or submit behavior, and reopening the saved result. Ask a screen-reader user or accessibility specialist to review the intended workflow where required. Use Nirmion PDF Accessibility Checklist to record these manual checks; it is a client-side checklist and does not inspect or certify the PDF. Correct failures, retest, retain the blank master and the released version, and document any unresolved barrier and owner-approved exception.
THE HELPER CREW
Tools for the fiddly bits.
These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.
RECEIPTS, PLEASE
Sources & review notes
Each source is linked to the steps it supports. Open it to check its scope and current guidance.
Source checked 2026-10-04