Run a quick automated check to identify common accessibility issues in a PDF document before sharing or publishing it.
Automated checks can help detect issues such as missing alternative text, incorrect table structure, or missing document titles. These issues may prevent people using assistive technologies, such as screen readers, from accessing the information in the document.
Several applications, such as Adobe Acrobat Pro, can be used to check a PDF for potential accessibility issues. However, Acrobat Pro requires a license and is not available to every UMB employee. PDFAudit has been identified as a free alternative, available to those who cannot use other tools such as Acrobat.
Use this tool as a first step to determine whether a document may need accessibility remediation before it is distributed.
Before You Upload a Document
The PDF checker is a third-party service. Do not upload documents that contain restricted, confidential, or sensitive university information.
Only upload documents that are appropriate to share with an external tool.
Examples of documents that should not be uploaded include:
- documents containing protected health information
- student records or FERPA-protected information
- HR or personnel documents
- internal administrative documents not intended for public sharing
- documents containing confidential research or financial data
If a document contains restricted information, contact your school or unit for assistance with accessibility review instead of using this tool.
Run the Check
Run PDF Accessibility Check with PDFAudit
- Upload the PDF and click Run Validation
- Results will display in two columns: “PDF/UA-1” and “WCAG 2.2 Profile.” For the purposes of Title II compliance, refer only to the WCAG column.
- Make note of the Compliance Score and the Issues that are listed in the WCAG column
Understanding the Results
Automated accessibility tools cannot detect every accessibility issue, and some results may require interpretation.
Use the guidance below to understand what the results mean and whether action is needed.
Issues That Usually Need to Be Fixed
If the checker flags any of the following issues, the document likely requires remediation before it is shared or published.
Common examples include:
- Missing document title
Screen readers rely on the document title to identify the file. - Images missing alternative text
Images, charts, or graphics must include alt text so screen reader users can understand their content. - Untagged PDF
A PDF must contain proper structural tags so assistive technology can interpret the document. - Table structure problems
Tables must include proper headers and structure so they can be navigated by screen readers. - Incorrect reading order or structural tagging issues
Content must be organized so assistive technologies read the document in the correct order.
If these issues appear, the document likely needs remediation using tools such as Acrobat Pro, Equidox, or other accessibility remediation tools.
Issues That May Not Affect Accessibility
Some warnings may appear even in documents that are accessible and usable.
Examples include:
- Content shall be marked as Artifact or tagged as real content
- Fonts not embedded
- Minor structural warnings or low-level technical messages
These warnings often relate to internal PDF structure and may not create barriers for users of assistive technologies.
If these are the only issues detected, and the document’s overall compliance score is high (recommended 95% and higher), the document may still be usable. However, if the document will be widely distributed or used in programs, services, or activities, a more thorough accessibility review may still be appropriate.
What the Results Mean
After running the check, review the issues reported in the results.
If the report includes issues listed under “Issues That Usually Need to Be Fixed”
The document should be remediated before it is shared or published.
For next steps, refer to the university’s guidance on creating accessible documents.
If the report shows only the warnings listed under “Issues That May Not Affect Accessibility”
The automated check did not detect common accessibility barriers such as missing alt text, missing document title, or structural tagging problems., and the document’s overall compliance score is high (recommended 95% and higher)
In most cases, this means the document is likely accessible or close to accessible.
These warnings relate to internal PDF structure and may appear even in documents that work correctly with assistive technologies.
If these are the only issues reported, the document may be acceptable to use. If additional accessibility concerns are suspected, the document can be reviewed further and possibly remediated.
Important Reminder
Automated accessibility tools help identify common issues but cannot detect every accessibility problem. Passing an automated check does not guarantee that a document is fully accessible, but it can help identify documents that likely require remediation.