CASE STUDY : FEDERAL FILLABLE PDF FORM REMEDIATION
Giving Every Form Field an Accessible Name and a Logical Place in the Structure
Project Context:
Federal Agency, Office of the Chief Information Officer | IT Exception Request Form
Role: Accessibility Remediation Consultant (Federal Contract)
Document Type: 2-page fillable PDF form with 22 fields, including 7 dropdown menus and 2 digital signature fields
Tools: Adobe Acrobat Pro (Accessibility Checker, Accessibility Tags, Reading Order, Prepare Form, Field Properties, Document Properties)
About the images on this page: Screenshots are not included. The original form belongs to a federal agency and cannot be shared, so this case study describes the work in text, using the checker results and tag structure from the actual project.
Challenge
A federal office needed a 2-page exception request form made Section 508 conformant so it could be completed and signed electronically. The form collects request details, mission need, prior troubleshooting, cost and risk impacts, an optional regulatory variance, agency approval, and two digital signatures.
On screen, the form looked organized and easy to complete. Underneath, its labels and fields had been grouped into layout tables, none of the fields had descriptions, and the fields themselves were missing from the tag structure. A screen reader user tabbing through the form would reach each field without hearing what it was asking for.
The existing structure was arranged so poorly that it could not be corrected piece by piece. Fixing individual tags would have left the underlying order broken, so I removed all of the existing tags and reading order and tagged the form again from scratch.
Initial Accessibility Assessment
The Adobe Accessibility Checker flagged failures in three of its categories: Document, Page Content, and Forms.
| Checker Category | Rule | Baseline Result |
|---|---|---|
| Document | Title | Failed |
| Document | Logical reading order | Needs manual check |
| Document | Color contrast | Needs manual check |
| Page Content | Tagged content | Failed (3 elements) |
| Page Content | Tagged annotations | Failed (4 elements) |
| Forms | Tagged form fields | Failed (20 fields) |
| Forms | Field descriptions | Failed (20 fields) |
Critical Issues Identified:
- Form fields missing from the tag structure – 20 fields were not tagged, so assistive technology could not place them in the document’s structure
- No field descriptions – None of the fields had a tooltip, which is the accessible name a screen reader announces when a user enters a field
- Layout misread as tables – Each row of labels and fields was grouped into a table, which split labels from their fields and cut off longer labels
- Logo read last – The agency logo appeared at the end of each page’s reading order instead of at the top
- Untagged content and annotations – Three content elements and four annotations sat outside the tag structure
- Title failed – No document title set, so the file name displayed instead
Remediation Process
Phase 1: Document Title and Display
- Added a descriptive title in Document Properties
- Changed Initial View from Show: File Name to Show: Document Title, so the title appears in the window title bar
Phase 2: Form Field Names and Tags
- Added a tooltip to every field that matches its visible label, such as “Request title,” so screen reader users hear the same question sighted users see
- Confirmed the required setting on each required field, so its required status is announced along with its name
- Tagged all form fields and annotations so each one sits in the tag structure next to its label
- Reviewed the 7 dropdown menus so each one opens with a clear “Select” prompt and offers complete, readable options
Phase 3: Retagging the Form From Scratch
- Assessed the existing tag tree and found it too disordered to repair, with labels and fields split across layout tables
- Removed all existing tags and the existing reading order, then tagged every element again, in order, from the top of page 1
- Tagged the form title as the H1 heading (
<H1>) and each numbered section, such as “1. Mission Need” and “Requesting Agency Approval,” as an H2 heading (<H2>) - Tagged instructions and each field label as its own paragraph (
<P>), keeping long labels whole - Moved the logo to the start of each page as a Figure with alternate text
- Resolved the three untagged content elements, so real text is read and decorative content is skipped
Phase 4: Reading Order and Color Contrast
- Verified with the Reading Order tool that each page reads top to bottom: logo, form title, instructions, then each section’s heading, instructions, labels, and fields
- Confirmed that the tab order follows the document structure
- Checked label, heading, and banner text against their backgrounds
Phase 5: Final Validation
- Final Accessibility Report: The checker found no problems in this document. Needs manual check 0, Passed manually 2, Failed manually 0, Skipped 1, Passed 29, Failed 0
Testing Performed:
- Adobe Accessibility Checker: Zero failures
- Field properties review: Confirmed every field has a tooltip that matches its visible label
- Tag tree review: Confirmed the new tag tree places headings, labels, and fields in the order the form is completed
- Reading order: Passed manually
- Color contrast: Passed manually
Before vs. After Comparison
| Check | Before Remediation | After Remediation |
|---|---|---|
| Title | Failed | Passed, shown in title bar |
| Tagged form fields | Failed (20 fields) | Passed |
| Field descriptions | Failed (20 fields) | Passed, every field named |
| Tagged content | Failed (3 elements) | Passed |
| Tagged annotations | Failed (4 elements) | Passed |
| Page structure | Labels and fields grouped in layout tables, too disordered to repair | All tags removed and the form retagged from scratch as headings, paragraphs, and fields |
| Reading order | Needs manual check, logo read last | Passed manually |
| Color contrast | Needs manual check | Passed manually |
| Checker total | Failures in 3 categories | 0 failed |
Results & Impact
- Original federal form: 0 failed, 29 passed, 2 passed manually
- Every field announces its purpose – Screen reader users hear each field’s name and required status as they move through the form
- Completed and signed electronically – Requesters using assistive technology can fill out, sign, and submit the form without help
- Section 508 and WCAG 2.1 AA conformant – Ready for agency distribution
Key Lesson: A Visible Label Is Not an Accessible Name
A label printed beside a field tells sighted users what to enter, but a screen reader announces the field’s tooltip. When the tooltip is blank, the user hears only “edit text” or “combo box.” Field descriptions are where form accessibility starts, and the tag structure decides whether each label and field are read together and in the right order.
Compliance Standards Met
- Section 508 (federal accessibility standard)
- WCAG 2.1 Level AA (Web Content Accessibility Guidelines)
- PDF/UA (ISO 14289-1) – Universal Accessibility standard for PDF documents
Tools & Technologies
Primary Tools: Adobe Acrobat Pro (Prepare Form, Field Properties, Accessibility Tags panel, Reading Order tool, Document Properties)
Validation Tools: Adobe Accessibility Checker
Standards: Section 508, WCAG 2.1 Level AA, PDF/UA (ISO 14289-1)
Reflection
Forms are where accessibility gaps have the most direct cost: a person who cannot tell what a field is asking cannot complete the request at all. This form looked finished, yet every field was unnamed and outside the structure. Fixing the field descriptions first, then correcting the structure around them, turned a form that only worked visually into one that works for everyone who needs to submit it.
It also showed when to stop patching. The existing structure was so poorly arranged that repairing individual tags would have kept the broken order in place. Removing all of the tags and retagging the form from scratch took more effort up front, but it was the only way to deliver a structure that reads correctly from start to finish. Layout tables never appeared as a single checker error, which is why the tag tree, not the checker summary, guided that decision.
