# PDF Accessibility Checker

Traditional Chinese version: [https://accesserty.com/ai/products/pdf-accessibility-checker.md](https://accesserty.com/ai/products/pdf-accessibility-checker.md)

Inspect a PDF on your device without uploading it. Choose a file up to 25 MB and use DevCheck to review structure clues, including tags and form fields. Reading order and actual use need separate checks; the tool does not repair or auto-tag the document.

## Purpose

The page helps content, QA, product, engineering, and site-maintenance teams inspect whether a PDF exposes basic accessibility structure signals before publication, procurement delivery, or deeper remediation.

## What it checks

- Pages with tag structures and pages without detected tags; not tag correctness or reading order.
- Counts of specific image-paint operations, link annotations and form-field annotations, including whether fields have tooltip text. These are not issue totals or validation of individual image alternatives, link purposes or field names.
- Bookmarks and page-size variants; missing bookmarks or mixed sizes are not automatic accessibility failures.
- Local browser-based PDF checking without uploading the PDF to Accesserty.

For now, check document language in a PDF reader or editor’s document properties; do not treat DevCheck’s “No language set” result as a confirmed finding.

## Getting started

1. Open the Scan tab in DevCheck and find the PDF check.
2. In Firefox, first use the button to open the PDF checker, then continue in its separate window or tab.
3. Choose a PDF from your computer (up to 25 MB), then select Analyze PDF. You do not need to open it in the browser’s PDF viewer first.
4. Record the document name and version and copy the result summary. Start with pages without detected tags and fields without tooltip text, and compare them with the document; counts are not an issue list.
5. Repair the source or PDF, then select and check the newly exported file. Also review reading order, links and forms with a PDF reader, keyboard and screen reader. PDF checks do not require AI.

## When analysis does not finish

In addition to 25 MB, DevCheck limits page count (up to 500 pages), analysis time and document complexity. A limit, cancellation or parsing error means the check did not finish, not that the PDF passed or failed. Keep the error message and use a tool suited to the document; do not remove required content to get under a limit.

## What it does not do

DevCheck does not remediate PDFs, automatically tag PDFs, certify PDF/UA conformance, or provide a legal compliance decision. It helps teams decide whether fuller manual review, source-document repair, assistive technology testing, or professional PDF remediation is needed. The linked interpretation guide uses hypothetical results for a two-page document to explain confirmation, recording and re-testing, not a tested file or customer case.

## Related pages

- [PDF accessibility checker](https://accesserty.com/en/pdf-accessibility-checker/)
- [Accesserty DevCheck](https://accesserty.com/en/devcheck/)
- [Understand WCAG check results](https://accesserty.com/en/wcag-compliance-tool/)
- [Web accessibility checker](https://accesserty.com/en/web-accessibility-checker/)
- [PDF structure signal checks guide](https://accesserty.com/en/guides/pdf-accessibility-structure-checks/)
- [PDF accessibility glossary page](https://accesserty.com/en/glossary/pdf-accessibility/)
- [Chrome Web Store](https://chromewebstore.google.com/detail/accesserty-devcheck/ompbhahmipenipgiiiehbkiibkonoeec)
- [Firefox Add-ons](https://addons.mozilla.org/firefox/addon/accesserty-devcheck/)