DocAccessible
Website document operations

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.

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

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

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

$0

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

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.