The [journal] emailed that my revised [manuscript] must meet accessibility tagging by [deadline=tomorrow]. I have the …
Open the PDF file you want to tag in Adobe Acrobat.
Select the Tools icon from the toolbar.
Choose Prepare for accessibility from the list of tools.
Click Automatically tag PDF to generate accessibility tags.
Best practiceAfter auto-tagging, review the tags using the Accessibility tags panel to ensure the structure matches the document content, as automated tagging may not always be perfect.
You can quickly access the Accessibility tags panel by right-clicking the Navigation pane and enabling it for easier tag review.
This runs in the Acrobat app - there is no separate API for this task.
PDF/UA is a specific standard for PDF documents, focusing on how the PDF itself is structured and tagged. WCAG (Web Content Accessibility Guidelines) is a broader, technology-agnostic standard for all web content, including PDFs. Many regulated tasks require meeting both standards. Think of PDF/UA as the 'how' for PDFs, and WCAG as the 'what' for overall accessibility.
Fixing accessibility in the original document, such as a Word file, saves a lot of time and effort. When you create an accessible source document, the PDF exported from it will often be accessible from the start. This means you spend less time fixing problems later in Acrobat, which can be very time-consuming for untagged PDFs.
Yes, the Accessibility Auto-Tag API is powered by Sensei, Adobe's AI. It can tag both native PDFs (made from digital files) and scanned PDFs. It identifies headings, tables, lists, and paragraphs, and can even detect the language.
Tagging is the most important part of PDF accessibility. Tags provide the structure and reading order for assistive technologies. Without proper tags, a PDF is very difficult for screen readers and other tools to understand, even if it looks fine visually.