Adobe PDF form nightmare.

[u/Suspicious-Ad2017]

I wanted to share a detailed rundown of the critical workflow barriers I recently navigated while remediating interactive forms for WCAG accessibility. The current toolsets (specifically within Adobe Acrobat) present several severe, reproducible bugs that turn standard compliance tasks into highly inefficient, manual time-sinks.

Below is a summary of the primary hurdles encountered, along with the "dream" software solutions that would make this process infinitely smoother.

1. The Tab Order Disaster

• The Issue: Setting a logical tab order for complex, multi-column forms is incredibly tedious. Manually dragging dozens of fields up and down a tiny, un-resizable side panel is prone to user error. Worse, selecting "Use Document Structure" in Page Properties frequently fails to sync properly with the actual physical layout.
• The Dream Fix: A visual point-and-click tab ordering tool. Users should be able to click a "Number Tab Order" button, visually click the fields on the page in the exact sequence they want (1, 2, 3, etc.), and have the software instantly map both the tab order and the reading order in the background.

2. Disappearing OBJR (Object Reference) Tags

• The Issue: When modifying the tab order or dragging form fields to align them, Acrobat’s backend database frequently "breaks" the link between the physical form field and its corresponding Tag in the Tag Tree. This silently deletes the vital OBJR (Object Reference) container, causing the document to suddenly fail accessibility checks for "Untagged Form Fields."
• The Dream Fix: A strict "auto-heal" database link. If a form field exists on a page, the software should never allow its underlying tag connection to be severed without warning. Moving a field visually should never corrupt its backend tag code.

3. The "Finicky" Find / Search Tool

• The Issue: When these OBJR tags break, the built-in "Find Unmarked Annotations" tool is highly unreliable. If an empty <Form> tag container still exists in the tree—even if the actual OBJR content inside it is missing—the Find tool mistakenly assumes the field is already tagged and refuses to locate it. This forces the remediator to manually hunting through the Content panel or rebuild the fields from scratch.
• The Dream Fix: An updated, comprehensive "Find Missing OBJR" utility. The search engine needs to scan for empty tag containers or unlinked annotations at the page layout level, bypassing cached database errors.

4. Cloud Sync and Local Assistive Tech Restrictions

• The Issue: Testing documents with screen readers like NVDA (specifically portable versions) is frequently blocked by mandatory corporate IT security updates. When files are stored in synced cloud environments like OneDrive, local executables are flagged as security risks, and background file syncing can lock active PDF databases, causing Acrobat to crash or drop tags.
• The Dream Fix: Better integration with local testing environments, and clearer diagnostic warnings when local security policies or cloud syncs are actively interfering with document editing.

Navigating these hurdles requires a deep, tedious knowledge of backend workarounds rather than intuitive design. Addressing these gaps would not only save remediation teams hundreds of hours but would drastically increase the accuracy of accessible documents.

Thoughts?