A11ysaurio PDF Checker: First Look at the New Client-Side PDF Accessibility Plugin for WordPress

Quick take

A11ysaurio PDF Checker is a free WordPress plugin that hooks into the Media Library and flags accessibility problems in the PDFs you've uploaded — missing tags, no alt text on embedded images, undeclared document language, bad reading order, and other issues that trip up WCAG 2.1 and PDF/UA compliance. The notable design choice: everything runs client-side in the browser using JavaScript, so your PDFs never leave your machine or get sent to a third-party scanning API. If you run a site that publishes a lot of PDFs — syllabi, board minutes, grant reports, spec sheets — and you've never actually checked whether they're accessible, this plugin gives you a first pass for zero dollars and zero server uploads.

It's newly listed on WordPress.org, has a small install base, and no meaningful review history yet, so treat this as an early-adopter tool rather than a battle-tested one.

What it actually checks

Based on the plugin's stated scope, it evaluates PDFs against a mix of WCAG 2.1 success criteria and ISO 14289 (PDF/UA) requirements, including:

• Document tagging — whether the PDF has a proper tag tree at all (untagged PDFs fail almost every downstream check)
• Image alt text — flags images embedded in the PDF that lack alternative text
• Reading order — checks whether the logical structure matches visual layout
• Language declaration — confirms the document specifies a primary language
• Heading structure — looks for proper heading hierarchy rather than just bold, larger text
• Scanned/image-only detection — flags PDFs that are just scanned images with no underlying text layer (a common accessibility dead end)

Results show up as a report attached to the file in the Media Library, so editors can see problems at the point of upload rather than discovering them after publishing.

Pricing

There is exactly one tier: free. It's distributed as open-source software through the official WordPress.org plugin repository under the GPL, the same license every WordPress.org plugin must use. There's no premium upsell, no paid tier gating advanced checks, and no account or API key required to use it. Because analysis happens locally in the browser rather than through a hosted service, there's also no usage-based pricing to worry about — no per-document or per-scan fees, since there's no backend doing the scanning.

Practically, this means:

• Cost to install and use: $0
• Cost to scan unlimited PDFs: $0
• Hosting/server requirements: none beyond your existing WordPress install
• Support: community support via the WordPress.org plugin forum (no SLA, no dedicated support team as of this writing)

Concrete use cases

• A community college publishing course syllabi as PDFs can run existing uploads through the checker to catch untagged documents before an accessibility complaint or OCR audit forces a scramble.
• A nonprofit uploading annual reports and grant deliverables can verify PDFs meet funder accessibility requirements (many federal and foundation grants now require WCAG/PDF-UA conformance) without sending sensitive financial documents to an external scanning service.
• A WooCommerce store with downloadable spec sheets or manuals can check that product PDFs have alt text on diagrams and a sensible reading order for screen reader users comparison-shopping.
• An HR team posting PDF job listings can catch missing document language tags and heading structure issues that make listings hard to navigate with assistive tech.
• A city or county government site publishing meeting minutes and public notices can use it as a low-friction first screen before a full manual PDF/UA audit, since many public-sector sites are under ADA Title II PDF remediation deadlines.

How it compares

	A11ysaurio PDF Checker	Accessibility Checker (Equalize Digital)	PDF Accessibility Assistant	WAVE (WebAIM)
Price	Free, open source	Free tier + Pro plans from ~$99/year per site	Varies by build (often free/open-source utility, some paid audit tools share the name)	Free web tool; WAVE API is paid (starts around $0.04/page scan)
PDF-specific checks	Yes — core focus is PDF WCAG 2.1 + PDF/UA analysis	Limited — primarily checks HTML page content, not deep PDF structure	Yes — PDF-focused, similar scope to A11ysaurio	No — WAVE evaluates rendered HTML pages, not PDF internal structure
Where analysis runs	Locally in-browser, no upload	Server-side, within your WordPress install	Varies — desktop tools run locally, some web versions upload files	Cloud-based; files/URLs sent to WebAIM's servers
WordPress integration	Native — built into Media Library	Native — full plugin with dashboard, scan history, issue tracking site-wide	Usually none — standalone tool, not WP-integrated	None — browser extension or standalone site checker
Best for	Sites that want quick, private PDF-only checks with no cost	Sites wanting a full accessibility scanner covering pages, posts, and PDFs together, with reporting and Pro remediation guidance	Users who want a dedicated non-WordPress PDF audit tool	Auditing live web pages (not PDFs) for WCAG issues, quick spot checks

Where it falls short (for now)

• No site-wide dashboard. Unlike Accessibility Checker, which gives you a running list of issues across every post, page, and PDF, A11ysaurio reports live per-file in the Media Library — there's no single screen showing "you have 40 PDFs with untagged content" across the whole site yet.
• No remediation tools. It tells you what's wrong; it doesn't fix tags, insert alt text, or re-order content for you. You'll still need Adobe Acrobat Pro, PAC 2024, or a manual PDF/UA workflow to actually remediate flagged files.
• Early-stage maturity. As a brand-new WordPress.org listing, it hasn't accumulated the install numbers, support-thread history, or edge-case bug reports that older tools like Accessibility Checker or WAVE have. Expect some rough edges with unusual PDF constructions (heavily nested forms, complex tables, non-Latin scripts).
• Browser performance on large PDFs. Because checking happens client-side, very large or image-heavy PDFs may be slower to analyze than a server-side or dedicated desktop scanner.

Should you try it today?

If you manage a WordPress site with more than a handful of PDFs and you've never checked them for accessibility, yes — install it this afternoon. It costs nothing, requires no signup, and doesn't send your documents anywhere, which matters if you're dealing with anything sensitive (HR docs, financial reports, student records). Use it as a triage tool: run it across your existing Media Library uploads, get a list of what's untagged or missing alt text, then prioritize fixes in Acrobat or a dedicated PDF/UA editor.

If you already run Accessibility Checker and want one tool that handles both your HTML content and PDFs with a unified dashboard, A11ysaurio isn't a replacement yet — think of it as a narrow, privacy-conscious add-on specifically for the PDF layer Accessibility Checker doesn't go deep on.