Website Accessibility Checker
Scan a public web page for WCAG 2.2 Level A and AA issues that automated testing can detect.
Free tool · WCAG 2.2 and PDF/UA
PDF Accessibility Checker
Check your PDF for common accessibility issues, understand what needs fixing, and prepare your document for a more accessible reading experience.
Automated checks find many technical problems, but they can't confirm on their own that a PDF is accessible or conforms to a standard.
- Free, no sign-up
- Checked on your device
- 36 checks with fix guidance
What we check
What the PDF checker tests
The checker reads your PDF's tag structure, metadata, annotations and fonts with the open-source PDF.js (opens in a new tab) engine, then runs checks mapped to WCAG 2.2 (opens in a new tab) Level A and AA and to PDF/UA-1.
Every result is marked failed, passed, needs manual review or not tested, with the pages involved and how to fix it.
- Title and languageDocument title, title display and the declared language
- Tags and structureTagging, untagged content and non-standard tag types
- Alternative textFigures without alt text, and pages that may be scanned images
- Headings, lists and tablesHeading levels, list items, table headers and scope
- Links and formsTagged links and fields, link descriptions and field names
- Fonts and textEmbedded fonts and text that can be extracted
Know the limits
What automated PDF checks can't tell you
Automated checks can confirm that tags, alternative text and metadata exist. They can't tell whether the reading order is logical, whether alternative text is accurate, whether colour carries meaning on its own, or whether text has enough contrast. A PDF with no automated failures can still be hard to use. Review the manual checks in your report, test with a screen reader, and consider a professional audit for important documents.
Your file stays on your device
The PDF is opened and analysed by this page in your browser using PDF.js. It is not uploaded to AccessMate or sent to any other service, it isn't stored, and it is released from memory when you check another file or leave the page. Read how these tools handle data.
Frequently asked questions
-
Is my PDF uploaded anywhere?
No. The PDF is read and checked by this page in your browser. Its contents are not sent to AccessMate or anyone else, and nothing is stored after you close or leave the page.
-
If the report finds no failures, is my PDF accessible?
Not necessarily. Automated checks can find many technical problems, but they can't judge reading order, whether alternative text is accurate, whether colour is used alone, or how the document works with a screen reader. Use the manual checks in the report, and test with assistive technology.
-
Which standards does it check?
It runs 36 checks mapped to WCAG 2.2 Level A and AA and to PDF/UA-1 (ISO 14289-1) where the mapping is technically justified. It does not perform a full PDF/UA validation; for that, use a dedicated validator such as veraPDF or PAC.
-
What files can I check?
PDF files up to 10.0 MB and 300 pages. Password-protected PDFs and dynamic XFA forms can't be checked. Remove the password first.
-
Why are some checks marked “Not tested”?
Some properties, such as colour contrast or the page tab-order setting, can't be read reliably by the PDF engine this tool uses. Rather than guess, the report marks them as not tested so you know to check them another way.
-
Can I save the results?
Yes. Download it as a PDF report, which is tagged so screen readers can read it, or as JSON. The report doesn't include your PDF's content.
Related tools
Accessibility Statement Generator
Answer three short steps to create an honest accessibility statement you can publish. Built in your browser; nothing is sent to us.
Alt Text Generator
Upload an image and get a suggested alt text from AI, tailored to how the image is used. Review it, edit it and copy it into your page.
