Check a PDF against WCAG 2.1 AA and PDF/UA — tags, reading order, alt text, contrast and document language. Runs entirely in your browser; the file is never uploaded.
or drop a file here
It reports whether the document is tagged, whether it declares a language and a real title, whether images carry alternative text, whether tables have header markup, whether multi-column pages will be read in the right order, whether any page is an un-OCR'd scan, whether text meets WCAG contrast ratios, and whether form fields and annotations have descriptions. Each finding cites the WCAG success criterion and PDF/UA clause it relates to.
No. Parsing, rendering and every check run inside your browser tab using our own PDF engine, so the file never leaves your device. That matters for exactly the organisations facing accessibility deadlines — government, healthcare and legal teams — who often cannot send documents to a cloud service at all. The one exception is a password-protected PDF, which needs a server step to unlock before it can be read.
No, and any tool claiming otherwise is misleading you. Software can prove a document fails — a missing tag tree is a fact. It cannot prove a document passes, because whether alt text is meaningful, or a heading level is right, needs human judgement. This checker lists those items separately as manual checks rather than quietly counting them as passes.
Almost every PDF produced by a normal Save as PDF is untagged: it has no structure tree, so assistive technology sees one undifferentiated block of text with no headings, lists, tables or reading order. It looks perfect on screen and is close to unusable with a screen reader. That gap is the entire reason accessibility remediation exists as an industry.
Both are legal requirements that documents published by covered organisations be accessible. The European Accessibility Act has applied since June 2025, and the US Department of Justice's ADA Title II rule sets compliance dates through April 2026 and April 2027 depending on the size of the public entity. PDFs are in scope, which is why document accessibility moved from good practice to a deadline.
Not yet — this release reports only, and never modifies your file. Automatic tagging and remediation are being built on the same engine; reporting shipped first precisely so a checker can never damage the document you are checking.