Skip to main content
Back to Blog
Guides2 min read

How Do I Make a PDF Form Accessible?

Build PDF forms with meaningful field labels, usable keyboard order, clear instructions and tested error handling. Check the completed form in its intended reader.

Aelira Team•Updated on
Share:LinkedInX

A PDF form needs to be usable from instructions through submission. A visible label and an apparently working mouse interaction are insufficient evidence of keyboard or screen-reader access.

Check labels and structure

Give fields meaningful programmatic labels that match their visible purpose. Explain formats and required fields in text. Group related choices appropriately and verify what a reader announces. Do not rely on a red border or unexplained asterisk alone.

Use the supported form-authoring workflow in the installed Acrobat or other editor. Interface names vary by release. Inspect the saved form's tags and field associations rather than assuming that converting a Word template creates a complete accessible interactive form.

Test the entire task

Follow keyboard focus through every page and control. Confirm a logical order, visible focus, selectable choices and usable submission. Check errors by deliberately leaving required fields empty and entering invalid data. The user needs to identify the error and understand how to correct it.

A scan of paper may require text recognition and rebuilding interactive fields. Flattening may remove interaction; evaluate whether the resulting static document still serves the required task.

Keep the original and inspect the actual saved output. Combine relevant automated checks with manual review of meaning, reading order, navigation and content preservation. Test important student tasks with the intended reader and assistive technologies. A clean checker report alone does not establish conformance.

Aelira Core is beta software. Supported workflows can apply eligible partial fixes and record outcomes, but some inputs need manual work or cannot produce a downloadable remediated file. Review the actual saved output, unresolved findings and content preservation before publication. Automated scores describe implemented checks rather than accessibility conformance. Inspect the public source and release documentation and evaluate a representative authorized sample before planning a rollout.

For covered US public entities, determine the correct 2027/2028 population cohort and rule scope in DOJ guidance. Australian DDA/DSE duties require a separate assessment.

Aelira Team

Aelira Team

•Accessibility Engineers

The Aelira team is building beta accessibility tools for higher education. Institutions can evaluate selected checks and partial fixes on their own files, with human review required before publication.

Explore accessibility remediation with Aelira

Join the pilot to evaluate Aelira's beta workflows. Support varies by format; outputs can be partial and need human review.