
Text printed beside a PDF form field does not automatically establish that a screen reader can identify the question belonging to that field. In Acrobat, inspect the field's description and its place in the tagged document structure. Adobe documents the Tooltip property as the place to add a text description. Then test the saved form through the recipient's reading route rather than approving it from the visible layout alone.
Key Takeaways
- A visible question, an internal field name and a useful spoken description are different objects.
- Acrobat's field Tooltip can communicate the question or instruction.
- Descriptions, navigation and saved answers each need their own check.
Identify the question behind each field
Start with the brief's approved questions. For a hypothetical portrait commission, distinguish the client's contact name from the person pictured, then separate both from a project title. Three fields described only as Name would leave an avoidable ambiguity even if each field technically has a description.
Use the fillable-field authoring guide to confirm actual form objects and distinct internal field names. Those names help the author manage the document; do not assume a short production identifier communicates the full question to its recipient. Keep the intended visible label and proposed description together for review.
Do not expand the description into a long unrelated policy statement. Include the information needed to understand this entry. If the field asks for a photo identifier, explain that role instead of merely repeating a generic phrase such as text field. These are editorial wording recommendations, not automatically generated descriptions verified in a reading tool.
Add the field description in Acrobat
Adobe's form-accessibility guidance describes this route:
- Use an appropriate Form tool and select the relevant field.
- Open the field's Properties through its context menu.
- Choose the General properties tab.
- Enter an appropriate description in Tooltip.
- Confirm the description belongs to the intended field before saving the candidate.
Inspect repeated or nearby fields individually. A useful description attached to the wrong box can mislead more than an obvious missing label. Preserve the approved visible wording unless the author has agreed that it also needs correction.
Retain the field's structural relationship
Adobe also says accessible form fields are tagged and part of the document structure. A description is not a substitute for that relationship. Review tags through the documented accessibility workflow, and preserve them through a supported tagged export when returning to the source.
Keep field-description work distinct from navigation order. A correctly named control reached at the wrong point can still make the brief confusing. Conversely, a perfect forward sequence does not tell the recipient what an unnamed field asks. Record these as separate findings instead of applying one blanket accessible label to the entire form.
Complete the saved brief as a recipient
Reopen the exact delivery copy with the intended assistive reading setup. Reach each disputed field and check whether its question is understandable, whether entered text belongs there and whether the surrounding instructions remain available. Include similarly named fields and choice controls relevant to the task. This is a proposed receiving procedure; no announcements have been observed for this article.
Finally, verify the retained answers using the saved-value handoff check. Do not flatten the form merely to conceal an unresolved description problem if the client still needs to enter information. Accept when the descriptions, visible questions and saved responses agree in the tested workflow, while retaining the editable master for future corrections.
Related tasks
- How Do I Make a Fillable Scribus PDF Instead of a Page of Static Text Boxes?
- Why Does a Filled PDF Look Blank After I Send It to Someone Else?
- Why Did My Word or PowerPoint PDF Lose Alt Text and Document Structure?
Sources and scope
- Adobe Acrobat: Create and verify PDF accessibility: Interactive form fields should be tagged in document structure and have a text description. The documented field Properties > General > Tooltip route supplies a field description.
Based on supplied complete Adobe form-accessibility guidance, reviewed October 29, 2026. No form property was edited and no screen reader was tested. Field-description examples are proposed wording requiring author approval, not an assertion of universal reader announcements.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.