What is the difference between PDF/UA and WCAG for PDF accessibility?

Standard Focus. PDF/UA A standard specifically for PDF documents, ensuring their technical accessibility. WCAG A broader standard for web content accessibility, applied to PDFs as a type of web content.

If my PDF has complex tables, how do I make them accessible?

First, use auto-tagging to get a basic structure. Then, use the Reading Order tool to check how the table cells are read. Finally, use the Content and Tags panels to manually adjust table structure and add proper headers. Auto-tagging often struggles with complex tables, so human review is key.

Verify Code Compliance in Adobe Acrobat — How-to & AI prompts

AI prompts

2 ways to ask · copy any one

AExecute — “help me do it”Compare the proposed schematic change PDF with the current safety-approved version, add…+

Compare the proposed schematic change PDF with the current safety-approved version, add comments where the change affects protective devices or clearances, and save a comparison report for the safety review.

when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.

BImprove — “do it better”Evaluate code compliance so I can decide to proceed: run a version compare, highlight any…+

Evaluate code compliance so I can decide to proceed: run a version compare, highlight any changes to protective device ratings, creepage/clearance, and earthing connections, add comments linking each change to the specific safety clause it may affect, and produce a short decision note stating whether work can proceed or needs engineering sign-off.

when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.

How to do it

the tool · the steps · what to avoid

1
Open the PDF file to be checked in Adobe Acrobat Pro.
2
Select Tools in the upper left, then add or open the Accessibility tool.
3
In the Accessibility pane, select Full Check.
4
In the dialog that opens, under Report Options, ensure Create accessibility report is checked.
5
Under Checking Options, select the desired standard (e.g., WCAG 2.0 or PDF/UA) if available.
NoteIf your version of Acrobat does not list PDF/UA or WCAG options, the checker will still test for core accessibility issues relevant to both standards.
6
Click Start Checking to run the accessibility check.
7
Review the results in the Accessibility Checker panel; expand each section to see issues flagged.
8
Address all issues marked as Failed or Needs manual check by following the recommended fixes or using the Fix option where available.
Best practiceFor best results, avoid using 'Print to PDF' when creating documents, as this removes accessibility tags and formatting.
9
Repeat the accessibility check after making corrections to confirm compliance.
10
Save a copy of the accessibility report for documentation or auditing purposes.
Best practiceAlways verify that text is selectable and not an image; scanned PDFs are not accessible and should be remediated or recreated.

In the appWith the API

The Accessibility Checker panel provides a detailed breakdown of compliance issues and links directly to problem elements in your PDF.

This runs in the Acrobat app - there is no separate API for this task.

Glossary

words on this page

AccessibilityMaking sure everyone, including people with disabilities, can use something.ExampleThe website was designed with Accessibility in mind, so screen readers can easily navigate it.

Alt textA short description for images so people who cannot see them know what they show.ExampleA person using a screen reader hears 'a red bicycle leaning against a brick wall' when they encounter the image.

PDF/UAA specific standard for making PDFs accessible.ExampleA company creates a PDF/UA document so visually impaired users can access its content.

The real tasks

the one, listed here

Evaluate whether a proposed schematic change meets safety codes before I let the team implement it.

FAQ

about this task

Standard	Focus
PDF/UA	A standard specifically for PDF documents, ensuring their technical accessibility.
WCAG	A broader standard for web content accessibility, applied to PDFs as a type of web content.

Auto-tagging in Acrobat helps by automatically adding basic structure to your PDF. It identifies headings, paragraphs, lists, and tables. This makes the PDF easier for screen readers to understand and navigate. It is a good first step, but not the complete solution for full accessibility.

Fixing the source document, like a Word file, is better because it creates an accessible PDF from the start. This saves a lot of time and effort. When you fix a PDF after it's made, it often takes much longer. The original document already has the right structure, which transfers to the PDF.

First, use auto-tagging to get a basic structure.
Then, use the Reading Order tool to check how the table cells are read.
Finally, use the Content and Tags panels to manually adjust table structure and add proper headers. Auto-tagging often struggles with complex tables, so human review is key.

The Accessibility Checker is a tool in Acrobat Pro that scans your PDF for common accessibility problems. It flags issues like missing alt text, incorrect reading order, or problems with headings. It is important because it helps you find and fix these problems, making your PDF usable for everyone, including those who use assistive technologies.

Verify Code Compliance

When to use it

AI prompts

How to do it

Glossary

The real tasks

Who does this

FAQ

Sources

Adobe help

Other guides