Find the PDFs your website forgot.

Keep a live PDF inventory, turn selected public files into private remediation drafts, and publish reviewed accessible alternatives without handing the website over to an opaque overlay.

Monitor one site free Compare limits

Free includes one domain and 20 monitored PDFs. No credit card is required.

public.example.gov

Website PDF inventory

Script verified

Detected: 84
Needs action: 12
Viewer live: 9

council-agenda.pdf2 pagesManual reviewCheck findings

benefits-guide.pdf6 pagesSource changedReview change

annual-report.pdf3 pagesDraft readyPublish viewer

permit-form.pdf1 pageWaitingPlan limit

Video guide

Watch monitoring end to end.

Count your public PDFs, connect the observe-only script, triage the inbox, and publish an approved accessible viewer, in one six-minute guide.

All video guides

Find the PDFs your website forgot

5:56 · Captions on screen · No narration

Count your public PDFs with the free scanner, connect one observe-only script, build a live inventory, triage alerts, and publish reviewed accessible alternatives.

Read the full transcript

0:00Find the PDFs your website forgot.

Count every public PDF, keep a live inventory, notice when files change, and publish reviewed accessible alternatives without handing your site to an overlay.

0:14Count your PDFs

You cannot fix what nobody has counted. Start with the free scanner: no account, nothing to install.

0:20Scan a domain

Open the free Website PDF scanner and type your domain.
Click Count them. The crawler reads your homepage and sitemap, then follows links to collect documents.
It opens the most-linked documents and checks what is inside each one.

0:44A real number, with evidence

The report counts the public PDF files linked from every page the crawler could reach.
It shows what automation can prove: missing tags, titles and language. Everything else is marked Needs a person.
Every row has a Convert button when you are ready to fix it.

1:08Connect your website

One script, installed once. It only observes where PDF links appear on your pages.

1:13Connect a website

Open Website monitoring. Your plan's websites and monitored PDF allowance are shown up top.
Enter the domain. The apex domain and www count as one website.
Click Connect website. It appears in your list with Setup needed until the script reports in.

1:37One line, before </body>

Copy the installation code and place it once in your site template, before the closing body tag.
It is observe-only: no visitor identity, cookies, form values or page content are collected.
A first report starts verification. DocAccessible confirms the exact website key before any PDF is checked.

2:05Build the inventory

Every PDF your pages link to, normalized, checked, and kept with its history.

2:11Every PDF, with evidence

Duplicate URLs are normalized. Each PDF keeps every page where it appears.
Eligible PDFs are fetched safely, malware-scanned, and checked with the same audit and veraPDF validation as the checker.
Each card shows an automated score, open findings, and what still needs manual review.

2:38Know what changed

Open History on any PDF. Every check is kept as an immutable record.
Pick a base and a candidate check, then Compare to see new and resolved findings.
A new file hash always creates a fresh check. An old result is never reused for a changed file.

3:04Triage and monitor

One inbox across every connected website, with alerts that never act on your behalf.

3:09The monitoring inbox

Open alerts surface what changed: a source PDF, a failed check, or a script that stopped reporting.
Filter the portfolio, select PDFs, and act in bulk: acknowledge, check again, assign an owner, or snooze.
Export evidence as CSV for your program records, scoped honestly as automated evidence.

3:39Cadence and alerts

Choose how often PDFs are rechecked, down to your plan's minimum, and when a silent script counts as a problem.
Pick which conditions create alerts, and who gets them by email.
Alerts never convert, remediate, or republish a PDF on their own.

4:03Convert and publish

Turn a public PDF into a private draft, review it, then publish an exact approved version to visitors.

4:09From public PDF to private draft

Convert to accessible draft imports the PDF into your workspace and runs the normal remediation pipeline.
The draft stays private. Review it exactly as you would any uploaded document.
Detection is not publication. Nothing reaches visitors until you decide.

4:33Publish deliberately

Publish viewer maps this exact PDF link to one exact, completed document version.
Release checks must pass, and you confirm two plain statements, including that automation does not certify conformance.
The card now reads Viewer live, pinned to an exact version.

5:02The accessible view

On your site, the PDF link gains a View accessible document button. The original link stays.
It opens a keyboard-accessible dialog with the approved HTML and a link to the original PDF.
A plain limitation notice tells readers what automation can and cannot claim.

5:28What you now know

The free scanner counts public PDFs with no account.
One observe-only script builds a live inventory.
Every check is kept; changed files get a fresh check.
One inbox for alerts, bulk triage and evidence export.
Convert selected PDFs into private remediation drafts.
Publish a viewer only for an exact, approved version.

5:45Monitor one site free.

One domain and 20 monitored PDFs. No credit card required.
Monitoring produces automated evidence for prioritization. It does not certify WCAG, PDF/UA, ADA or Section 508 conformance; manual review is still required.

Controlled by design

Detection is not publication.

Each step has its own decision boundary, so finding a URL can never automatically turn an unreviewed output into a public accessibility claim.

01
Connect one script
Add an asynchronous, dependency-free script to the verified domain. It starts in observe-only mode and also detects PDF links added by client-side navigation.
02
Build a useful inventory
Normalize duplicate URLs, show where each PDF appears, preserve over-limit discoveries, and keep automated checks separate from manual-review requirements.
03
Convert selected PDFs
Import one eligible public PDF into the private document workspace and run the normal remediation pipeline. Conversion uses document quota and never publishes by itself.
04
Notice source changes
Scheduled checks record immutable history and compare the file hash, so a changed source becomes visible instead of silently inheriting an older result.
05
Publish deliberately
Map a source URL to one completed document version. Visitors receive a keyboard-accessible dialog only after explicit owner confirmation or reviewer approval.

No blanket accessibility claim

A controlled alternative to blanket conversion.

The script never claims that the source PDF is compliant and never replaces every link by default. It can present an approved, reflowed HTML alternative in a native dialog while keeping the original PDF available. Exact-layout PDF remediation, complex documents, and assistive-technology verification can still need qualified human work.

Compare remediation paths Understand manual remediation Compare DocAccessible and DocAccess

Operational status

Know what changed and what happens next.

Discovery, checking, review, and publication remain separate states. That makes ownership clear and prevents an old result from silently carrying over to a changed file.

Detected: The normalized PDF URL and every page where it appears are recorded.
Waiting for a slot: Over-limit discoveries stay visible but are not fetched or checked.
Needs manual review: Automated findings identify questions a person still needs to verify.
Draft processing: A selected public PDF is being imported and remediated in the private document workspace.
Accessible draft ready: The converted document can be opened, reviewed, and revised before any publication decision.
Source changed: A new file hash creates a fresh check instead of reusing an older decision.
Viewer published: One completed, approved HTML version is mapped to the exact source URL.
Original available: Visitors can still open the source PDF; the viewer is an explicit alternative.

Verified before crawling

The script key proves control of the page.

After the browser reports the installation, the server fetches that same public page and confirms the exact site key. Crawling stays bounded to the verified domain and its allowed subdomains, with redirect and private-network protections.

Minimal browser data

Inventory links, not visitors.

The script reports the page URL, PDF URL, visible link label, element type, script version, and site key. It does not send visitor identity, cookies, form values, or the surrounding page content.

Included with every plan

Start with a real public website.

Limits apply to actively monitored domains and PDFs. Extra discoveries remain visible as waiting inventory, and there are no automatic overage charges.

Free monitoring limits

Monitored websites: 1
Actively monitored PDFs: 20

Exchange monitoring limits

$19/ month

Monitored websites: 1
Actively monitored PDFs: 100

Pro monitoring limits

$29/ month

Monitored websites: 3
Actively monitored PDFs: 250

Team monitoring limits

$49/ month

Monitored websites: 10
Actively monitored PDFs: 2,000

Organization monitoring limits

$199/ month

Monitored websites: 25
Actively monitored PDFs: 5,000

Compare complete plans Monitor one website free

Live demonstration

Walk a real public-sector document surface.

Northstar Public Schools is a demonstration district we publish so you can see exactly what monitoring works on before connecting your own site: a document centre with nine public PDFs spread across the calendar, board agendas, the family handbook, budget summaries, and safety guidance, in English and Spanish.

Every school, person, figure, and document on it is fictional, and the site is marked so search engines never present it as a genuine institution.

Open the demonstration district Go straight to its document centre

dummy.docaccessible.com

District document centre

Demonstration

2026-27 School Year CalendarOffice of the Superintendent

PDF · 3 pages

School Board Regular Meeting AgendaSchool Board Office

PDF · 4 pages

Family Handbook 2026-27Family and Community Engagement

PDF · 5 pages

Calendario Escolar 2026-27Language Access

PDF · 3 pages

Nine documents in total. This is the inventory a connected site produces, and the surface an accessible alternative is published against.

Conversion quality

Measure fidelity before making an accuracy claim.

Our planned 50-document pilot separates text, reading order, structure, links, images, tables, and routing safety by document class. The corpus is still being prepared, so no conversion accuracy result is published.

Review the methodology

Questions

How monitoring and conversion behave

What does the website script collect?

It reports the current page URL, detected PDF URLs, visible link labels, element type, script version, and site key. It does not send visitor identity, form values, cookies, or page content.

Does installing the script replace every PDF link?

No. Installation starts in observe-only mode. Converting a selected PDF creates a private draft but does not change the website. A link changes only after an authorized workspace member maps that exact PDF URL to a completed document version, confirms the publication requirements, and keeps the site viewer enabled.

Does an automated check certify that a PDF is accessible?

No. Automated findings help prioritize work but cannot prove reading order, complex tables, charts, forms, or the assistive-technology experience. Important documents still need appropriate human review.

What happens after the monitoring limit is reached?

Additional PDF URLs remain visible in inventory as waiting items, but they are not fetched or checked. Ignoring an active item releases its slot to the oldest waiting PDF.

How is website ownership verified?

The first browser report starts verification, then the monitoring worker fetches that exact public page and confirms the site key in the installed script. A browser Origin header alone is not treated as proof of control.

Is website monitoring the same as PDF remediation?

No. Monitoring discovers files, records automated findings, and notices source changes. An authorized member can import a selected public PDF into the normal automated remediation workflow as a private draft. Complex, important, or exact-layout PDFs can still require qualified human remediation and assistive-technology review.

Can a vendor remediate documents found by monitoring?

Yes. An owner can use Exchange to create a restricted case for an internal team or external vendor, review immutable returned revisions, approve one version, and then map that exact approved HTML output to the website viewer.

How is this different from an automatic website PDF transcript service?

DocAccessible discovers website PDFs automatically but keeps conversion and publication as separate authorized actions. A selected file becomes an editable private draft with findings, version history, hosted HTML, and rebuilt tagged PDF output. Teams that prefer automatic site-wide transcripts, translation, document Q&A, or live reader assistance should compare that workflow with products built around those services.