Skip to main content
Participant
August 21, 2020
Répondu

Recommended workflow for creating accessible PDFs with Acrobat

We are looking to audit and adapt a PDF for one of our public sector clients to make it accessible, based on the new UK law that requires public sectors to meet WCAG 2.1 guidelines. I noticed on your website the PDF accessibility tool only goes to WCAG 2.0 which is the previous version. When looking into the differences between these versions, it appears the updates to 2.1 could be relevant to websites only, and not applicable to PDF's - are we right in thinking that? Can you confirm your accessibility guidelines and checker will meet the standards that are to be in place from 23 September 2020?

 

Any help would be much appreciated.

    Ce sujet a été fermé aux réponses.
    Meilleure réponse par BaniVerma

    Hi all,

     

    Is Acrobat's Accessibility Check enough for WCAG 2.1 compliance?

    No. Acrobat's Accessibility Check is documented as verifying conformance against PDF/UA and WCAG 2.0. Adobe's published rule-mapping table for the checker is built on WCAG 2.0 success criteria. Passing the checker alone doesn't guarantee WCAG 2.1 compliance or conformance with other accessibility requirements.

    Accessibility Check helps identify and remediate accessibility issues while supporting the creation of PDFs that align with accessibility standards such as PDF/UA and WCAG. Some accessibility requirements require manual evaluation because they can't be determined automatically.

    References

     

    What is the recommended workflow for creating accessible PDFs?

    Adobe recommends incorporating accessibility throughout the document creation process.

    Workflow step Purpose
    Create an accessible source document Build accessibility into the document before converting it to PDF.
    Convert to PDF Preserve the document structure in PDF format.
    Run Accessibility Check Identify and remediate common accessibility issues, documented against PDF/UA and WCAG 2.0.
    Perform manual accessibility review Verify items that require human judgment, such as meaningful alternative text, reading order, and document structure.
    Validate with the PDF/UA Preflight profile (Acrobat Pro, when required) Verify technical conformance with the PDF/UA standard.

    References

     

    Why is manual accessibility review still required?

    Some accessibility requirements can't be evaluated automatically.

    For example, automated tools can't determine whether alternative text is meaningful, whether the reading order is appropriate, or whether headings, tables, and other document structures accurately communicate the intended content.

    Adobe recommends combining Accessibility Check with manual review as part of an accessible PDF workflow.

    Reference: https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html

     

    When should I validate with the PDF/UA Preflight profile?

    If your workflow or organization requires PDF/UA conformance, Acrobat Pro includes a PDF/UA Preflight profile that runs syntax-level checks for technical conformance with the PDF/UA standard.

    The PDF/UA Preflight profile complements Accessibility Check. Accessibility Check helps identify and remediate accessibility issues throughout the document, while PDF/UA Preflight validates technical, syntax-level conformance with the PDF/UA specification. Because it checks syntax only, it doesn't confirm full PDF/UA compliance on its own.

    Reference: https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html

     

    Thanks,

    ^BS

    4 commentaires

    BaniVerma
    Community Manager
    BaniVermaCommunity ManagerRéponse
    Community Manager
    August 10, 2026

    Hi all,

     

    Is Acrobat's Accessibility Check enough for WCAG 2.1 compliance?

    No. Acrobat's Accessibility Check is documented as verifying conformance against PDF/UA and WCAG 2.0. Adobe's published rule-mapping table for the checker is built on WCAG 2.0 success criteria. Passing the checker alone doesn't guarantee WCAG 2.1 compliance or conformance with other accessibility requirements.

    Accessibility Check helps identify and remediate accessibility issues while supporting the creation of PDFs that align with accessibility standards such as PDF/UA and WCAG. Some accessibility requirements require manual evaluation because they can't be determined automatically.

    References

     

    What is the recommended workflow for creating accessible PDFs?

    Adobe recommends incorporating accessibility throughout the document creation process.

    Workflow step Purpose
    Create an accessible source document Build accessibility into the document before converting it to PDF.
    Convert to PDF Preserve the document structure in PDF format.
    Run Accessibility Check Identify and remediate common accessibility issues, documented against PDF/UA and WCAG 2.0.
    Perform manual accessibility review Verify items that require human judgment, such as meaningful alternative text, reading order, and document structure.
    Validate with the PDF/UA Preflight profile (Acrobat Pro, when required) Verify technical conformance with the PDF/UA standard.

    References

     

    Why is manual accessibility review still required?

    Some accessibility requirements can't be evaluated automatically.

    For example, automated tools can't determine whether alternative text is meaningful, whether the reading order is appropriate, or whether headings, tables, and other document structures accurately communicate the intended content.

    Adobe recommends combining Accessibility Check with manual review as part of an accessible PDF workflow.

    Reference: https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html

     

    When should I validate with the PDF/UA Preflight profile?

    If your workflow or organization requires PDF/UA conformance, Acrobat Pro includes a PDF/UA Preflight profile that runs syntax-level checks for technical conformance with the PDF/UA standard.

    The PDF/UA Preflight profile complements Accessibility Check. Accessibility Check helps identify and remediate accessibility issues throughout the document, while PDF/UA Preflight validates technical, syntax-level conformance with the PDF/UA specification. Because it checks syntax only, it doesn't confirm full PDF/UA compliance on its own.

    Reference: https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html

     

    Thanks,

    ^BS

    maxwithdax
    Community Expert
    Community Expert
    June 16, 2022

    Passing the Adobe Acrobat Checker is not a validation of meeting WCAG (2.0 or 2.1). The Acrobat Checker is a good place to start but meeting EN 301-549 standards will always be a series of automated checks and manual review. As a good practice you start with accessibility in the source doc. Then you check with Acrobat and fix the errors then you should use a checker like PAC 2021 that takes a much deeper look at the technical compliance of the code behind your PDF and will give you the best response to the question "Is my document accessible?" Let me know if you have more questions.

    Known Participant
    February 16, 2023

    PAC 2021 is not compatible with MacOS (we use both OS here). Not sure if you know of an alternative with the same ability to help us check/ confirm compliance with WCAG 2.1  but thought I would ask!

    maxwithdax
    Community Expert
    Community Expert
    April 27, 2023

    When it comes to MAC you really are at a disadvantage for validating accessibility unless you are running Parallels or another PC emulator. PAC does have an online version of PAC 2023 but it is limited and only gives you a report.