Website monitoring
Review website PDF inventory and source changes
Prioritize discovered PDFs, read scan history, handle plan limits, and respond when a public source changes.
- For
- Website accessibility owners and content operators
- Typical time
- 5 minutes per review session
Before you start
- A verified website connection with discovered PDF links
Procedure
Step by step
Open a connected website
Review detected, active, over-limit, changed, converted, and published counts before opening individual PDF records.
Prioritize active PDFs
Plan-eligible discoveries receive active scan slots. Over-limit records remain visible but are not fetched until capacity is available.
Read automated findings and history
Use scan results to prioritize work, then inspect the source pages and document purpose. Scores are machine evidence, not conformance decisions.
Respond to a source change
A changed content hash means the public PDF is different. Recheck the source and any published alternative before claiming the mapping is current.
How capacity works
Website domain and PDF allowances are separate from remediation uploads. If capacity changes, the oldest included domains and PDFs remain active first while excess inventory stays visible and paused.
Safe remote fetching
The worker revalidates redirects, enforces response bounds, validates the PDF signature, scans for malware, and runs automated inspection in a bounded process.
Related guides
- Connect a website and install PDF monitoringVerify a public domain, install the lightweight script, and begin building a bounded PDF inventory.
- Convert a discovered PDF and publish an accessible alternativeCreate a private remediation draft from a public PDF, review it, and explicitly map one completed version for website visitors.
- Understand automation, conformance, and manual remediationKnow what DocAccessible automates, what still requires human validation, and when exact-layout manual PDF remediation is the right path.