Reactive Accessibility Fixes — AI Prompts for Adobe Acrobat

The moments that lead here

If one of these is your afternoon, you are in the right place.

we keep patching accessibility problems instead of preventing them

1 ready prompt

Written for the moment this actually comes up.

Become — change the pattern

We continually patch accessibility after release rather than building it into authoring. Diagnose…

We continually patch accessibility after release rather than building it into authoring. Diagnose where authoring fails to produce accessible output and recommend one change—a mandatory accessibility preflight, template constraints, or author checklist—that ensures accessible manuals without slowing contributors. Show how to measure improvement over the next two releases.

Who does this, and with what

The same task is different work inside a different job.

Technical WriterAdobe Acrobat

Next to this one

Other convince work people do in Adobe Acrobat.

Raise Typographic Standards Rapid Needs Assessment Rapid Post-Shift Feedback Rapid Stakeholder Consolidation Rapid Tooling Method Decision Reactive Rebuttal Cycle Readable Hotspot Summary Needed Record Decision Rationale Recurring Daylighting Flags Recurring Scene Shortfalls

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt