The PDF sitting in your returns portal is a compliance liability nobody on your ops team is checking
Here’s an unglamorous thing I’ve watched bite cross-border sellers three times in the last eighteen months: a compliance officer at a marketplace, or a customer-support lead at a DTC brand, opens the PDF you attached to a product listing — the spec sheet, the warranty card, the safety data sheet, the return-authorization form — and it’s an untagged, unlabeled, screen-reader-hostile export from Canva or InDesign. Nobody on your side ever looked at it. It shipped from a template in 2022 and it’s been quietly reproduced ten thousand times since. In the EU, the European Accessibility Act enforcement wave is landing on exactly this kind of document; in the US, ADA and Section 508 exposure on published PDFs is the kind of thing that gets a demand letter before it gets a blog post. And almost no seller I talk to has a workflow for it. That’s why a free, no-signup PDF checker caught my eye on Product Hunt this week — not because it’s a Shopify app or a TikTok Shop integration, but because it sits in the blind spot every cross-border operator has: the documents we publish and never audit. PDF Accessibility Checker by WebYes is worth twenty minutes of your week, and here’s my honest read on what it does, what it doesn’t, and what you should actually do with it.
What the tool actually solves (and why the free tier matters more than the feature list)
The pitch from maker Subin Raj is straightforward: teams invest in website accessibility, then link PDFs from those sites — annual reports, brochures, application forms, policy documents — that “quietly shut people out.” Anyone using a screen reader opens one and gets lost in an unstructured jumble. The existing path to checking properly has meant either expensive desktop software (think Adobe Acrobat Pro’s accessibility tools, or the enterprise tier of axe DevTools-style suites) or hours of manual review. Most teams do neither, and the PDF ships.
The WebYes checker removes the friction: upload a PDF up to 50 MB or paste a public link, no account, no email, no install, and the file isn’t stored. It runs every machine-verifiable check in WCAG Level A and AA plus PDF/UA (ISO 14289), covering structure (reading order, heading nesting, lists, table headers), content (alt text, document language, title, bookmarks, font embedding), and interaction (text contrast, form-field labels, link descriptions, tab order). Results are ranked critical-to-minor, and clicking a finding highlights the problem directly on the page. That last part is the real product decision — the designer, Lukhman, framed the whole results screen around three questions: what should I fix first, where is the problem, how do I fix it.
For a cross-border seller, the “free, no signup, no storage” combination isn’t a nice-to-have — it’s the difference between a tool your agency account manager will actually use on a Friday afternoon and one that sits in a bookmarks folder. The privacy posture also matters if you’re uploading anything customer-facing that contains PII, order numbers, or supplier terms. Not storing the file is the right default, and I’d want that in writing before I pointed it at anything sensitive.
Why Amazon sellers should care more than Shopify ones
Shopify merchants think of their storefront as the product, and PDFs are an afterthought — a size guide here, a care-instructions card there. Amazon sellers live in a world where documents are the listing. Safety data sheets, compliance certificates, declaration-of-conformity PDFs, instruction manuals in five languages, and the increasingly common “product documentation” attachments in Seller Central all get published, versioned, and reproduced at scale. If you’re selling into the EU, the documentation burden is only getting heavier, and marketplace compliance teams are starting to treat document quality as part of listing quality. A free checker that flags missing document language, unembedded fonts, and untagged structure is a ten-minute audit you can run across your top twenty SKUs this week. Shopify sellers should care too, but for a different reason: your returns policy, warranty terms, and care guides are the documents customers actually open, and an inaccessible one is a support ticket waiting to happen.
How it differs from the incumbents — and where the comparison gets uncomfortable
The honest competitive set here is three-pronged. First, Adobe Acrobat Pro, which has had a built-in accessibility checker for years and is the default for anyone already paying for Creative Cloud — but it’s desktop-bound, priced per seat, and the output is a rule-ID list that assumes you know what “Tagged PDF” and “Logical Reading Order” mean. Second, specialist accessibility platforms like axe DevTools and the broader Deque ecosystem, which are excellent for web content and increasingly cover documents, but are priced and positioned for enterprise accessibility programs, not a five-person DTC ops team. Third, the free-but-thin tier: browser extensions and open-source validators that flag problems but don’t tell you where they are or how to fix them.
What PDF Accessibility Checker by WebYes does differently is the middle layer: it’s free like the thin tools, but it gives you the on-page highlighting and fix guidance you’d normally pay enterprise money for. The maker’s own framing — “most PDF checkers I tried gave you a long list of rule IDs and left you to work out where each problem was” — is a fair critique of the category, and the highlighting is a genuine UX upgrade. The severity ranking is the other differentiator: critical-to-minor filtering is how a non-specialist actually triages, and it’s the feature I’d point a marketing coordinator at without a training session.
But the comparison also exposes the ceiling. The tool tests against WCAG 2.1 Level AA and PDF/UA — not Level AAA, as the maker confirmed in the thread when Deethul K asked directly. For most commercial sellers, AA is the right target and AAA is overkill, so I don’t hold that against it. What I do hold against the category is the reading-order problem. As the maker explained to JC, reading order isn’t visually previewed because automated tools can’t reliably judge logical flow — the report flags the pages involved as a reminder for manual verification. That’s the honest answer, and it’s also the part that will bite you: reading order is exactly where exported InDesign and Canva PDFs fail, and it’s the one check you still have to do by hand.
Where the math breaks
Two numbers to keep in your head. First, 50 MB — the upload cap. That’s fine for a spec sheet or a warranty card, and it’s a real constraint for a 200-page catalog or a scanned manual with high-res imagery. Second, scanned PDFs: the maker confirmed you can upload them, but for image-only files the results are limited to what the checker can assess from the images, and structure checks (headings, tags) need a PDF with recognized text and tagging. Translation: if your supplier sends you scanned compliance certificates — and they will — this tool will give you a partial read at best. You’ll need OCR upstream before the checker is useful on those documents. That’s not a flaw in the product so much as a workflow gap the product makes visible, and it’s the gap most sellers don’t know they have.
What cross-border sellers can borrow from this launch
Three things, and none of them require you to adopt the tool.
One: treat published documents as a SKU-level asset with an owner. The reason PDFs go unchecked is organizational, not technical — nobody owns them. The launch thread itself is a useful template: the maker’s framing of “content and marketing teams, designers and document creators, web teams and agencies” maps almost exactly onto the roles inside a mid-size cross-border brand. Assign one person to own document accessibility across your top SKUs, give them a quarterly cadence, and put it in the same tracker as your listing health. The tool being free and no-signup removes the last excuse for not starting.
Two: use severity ranking as a triage discipline, not just a UI feature. The critical-to-minor filter is a model for how you should be running every compliance audit — start with the findings that will actually get you delisted, sued, or reviewed, and work down. Most sellers I know run audits in document order, which is the slowest possible path. Borrow the severity-first mental model even if you’re using Acrobat or an agency.
Three: verify the claims before you trust the check. The thread is unusually candid about limits — no AAA, partial coverage on scanned files, no automated reading-order judgment. That candor is a feature, and it’s the right posture for any compliance tool you put in front of a marketplace auditor. When you evaluate any accessibility or compliance SaaS, ask the same three questions the maker answered: what standard, what level, and what does the tool explicitly not check? If the vendor can’t answer the third, walk.
The part I’d push back on
The launch frames the tool as a step toward “ADA and Section 508 readiness,” and that’s accurate as far as it goes — but readiness is not compliance, and a free checker is not an audit trail. If you’re selling into the EU and the European Accessibility Act applies to your product category, or you’re a US seller with public-sector or enterprise customers, you need a documented remediation process, not just a scan result. The tool will tell you what’s broken; it won’t tell a regulator that you fixed it on a schedule. Budget for the human review — especially reading order — and keep a log. The free checker is the front door, not the whole house.
What I’d watch / test next
This week, pick your five most-downloaded or most-linked PDFs — the warranty card, the size guide, the returns form, the safety sheet, the instruction manual — and run each one through PDF Accessibility Checker by WebYes. Log the severity-ranked findings in a spreadsheet, note which ones are structural versus content, and flag any scanned documents for OCR before you re-run them. Then do the one thing the tool can’t: open each PDF with a screen reader (VoiceOver on Mac, NVDA on Windows) and listen to the reading order. If it’s a jumble, you’ve found your real project. Finally, put a recurring calendar block on your ops lead’s schedule for a quarterly re-scan, and add “document accessibility” as a line item in your next agency or freelancer brief. The tool is free; the discipline is the moat.
