# DocAccessible complete public product documentation
> A consolidated, plain-text rendering of DocAccessible product documentation for retrieval tools and AI agents that need more context than the curated llms.txt index.
Canonical site: https://docaccessible.com
Curated index: https://docaccessible.com/llms.txt
Content review date: 2026-09-02
This file contains public product guidance only. It excludes authenticated workspaces, private documents, customer data, tokens, and API responses. Canonical HTML pages remain the source to cite and share.
## Safety and conformance boundaries
- Automated checking and remediation assist accessibility work; they do not certify conformance.
- Preserve unresolved manual-review findings until a qualified person has evaluated them with representative assistive technology and tasks.
- Rebuilt tagged PDFs may reflow. Use separately scoped specialist remediation when exact pagination, forms, or presentation must remain intact.
- Published alternatives are deliberate, version-bound actions. Discovery or processing alone does not make a document public.
## Key facts
Manual PDF remediation pricing:
- Rate: $5 USD per accepted source page, flat regardless of page complexity.
- Minimum project: 501 source pages, so the smallest eligible engagement is $2,505 USD before applicable tax.
- Scope: exact-layout repair of the original PDF, performed by a specialist, billed separately from any software plan.
- Projects of 500 pages or fewer are not accepted at this rate; use the software plans or coordinate an independent vendor through Exchange.
Software plan pricing and enforced allowances:
- Free: $0. 3 documents per month, files up to 10 MB, 1 seat, 2 active Exchange cases, monitoring for 1 website and up to 20 PDFs.
- Exchange: $19 per month. No automated remediation allowance, files up to 50 MB, 3 seats, 250 active Exchange cases, monitoring for 1 website and up to 100 PDFs.
- Pro: $29 per month. 50 documents per month, files up to 50 MB, 1 seat, 10 active Exchange cases, monitoring for 3 websites and up to 250 PDFs.
- Team: $49 per month. 200 documents per month, files up to 50 MB, 5 seats, 50 active Exchange cases, monitoring for 10 websites and up to 2,000 PDFs.
- Organization: $199 per month. 500 documents per month, files up to 100 MB, 25 seats, 250 active Exchange cases, monitoring for 25 websites and up to 5,000 PDFs.
- Billing runs month to month and can be cancelled from the billing portal at any time.
- Reaching a monthly document limit pauses new uploads until reset or upgrade. There are no automatic overage charges.
- The Free plan requires no credit card.
Standards and output:
- Automated checks are mapped to WCAG 2.2 Level AA. Generated PDFs are aligned to PDF/UA.
- Automated checking and generated output do not certify WCAG, PDF/UA, ADA, or Section 508 conformance.
- Hosted accessible HTML is responsive and published from the platform. The rebuilt tagged PDF reproduces the same content for offline use and may change layout or pagination.
- Preserving the exact source-PDF appearance requires the manual remediation path above.
- Scanned and OCR-derived pages are detected and routed to reviewed OCR or specialist remediation rather than automatic tagging.
Regulatory dates referenced on this site:
- ADA Title II: public entities with a population of 50,000 or more must comply by April 26, 2027.
- ADA Title II: public entities under 50,000 population, and special district governments, have until April 26, 2028.
Free tools requiring no account: website PDF scanner, PDF-to-HTML converter, PDF accessibility checker, PDF tag viewer, PDF auto-tagger, and scanned-PDF text recovery.
## Common questions
Canonical answer page: https://docaccessible.com/answers
### Pricing and cost
**How much does PDF accessibility remediation cost?**
DocAccessible charges $5 USD per accepted source page for manual PDF remediation, and the rate is flat regardless of how complex a page is. The agency team takes bulk projects above 500 pages, so the smallest eligible project is 501 pages at $2,505 before applicable tax. Automated remediation is priced separately as a monthly software subscription rather than per page.
Source: https://docaccessible.com/services/pdf-accessibility-remediation (canonical answer page: https://docaccessible.com/answers#manual-pdf-remediation-cost)
**How much does DocAccessible cost per month?**
DocAccessible software plans are Free at $0, Exchange at $19 per month, Pro at $29 per month, Team at $49 per month, and Organization at $199 per month. Each paid plan raises the monthly document allowance, upload size, seat count, active Exchange cases, and website PDF monitoring limits. Subscriptions run month to month and can be cancelled from the billing portal at any time.
Source: https://docaccessible.com/pricing (canonical answer page: https://docaccessible.com/answers#software-plan-pricing)
**Do you charge per page or per document?**
The two paths are priced differently. Software plans are billed per month with a document allowance, so a 90-page report and a two-page memo each count as one document. Manual agency remediation is billed per source page at $5 USD, with no complexity multiplier.
Source: https://docaccessible.com/pricing (canonical answer page: https://docaccessible.com/answers#per-page-or-per-document)
**What if my PDF project is 500 pages or fewer?**
The DocAccessible agency team focuses on bulk projects above 500 pages, so smaller jobs are not accepted at the per-page rate. For a smaller project, use the software plans to generate and review accessible output yourself, or use Exchange to coordinate an independent remediation vendor through the same workflow.
Source: https://docaccessible.com/services/pdf-accessibility-remediation (canonical answer page: https://docaccessible.com/answers#smallest-remediation-project)
**Is there a free plan, and is a credit card required?**
Yes, there is a Free plan and no card is required. It covers three documents per month, files up to 10 MB, automated checks, hosted accessible HTML, a rebuilt tagged PDF, public and unlisted share links, and monitoring of one website with up to 20 PDFs.
Source: https://docaccessible.com/pricing (canonical answer page: https://docaccessible.com/answers#free-plan-and-credit-card)
**What happens when I reach my monthly document limit?**
New uploads pause until the next monthly reset or until the plan is upgraded. Existing documents, hosted pages, downloads, and edits stay available, and no automatic overage charges are applied.
Source: https://docaccessible.com/pricing (canonical answer page: https://docaccessible.com/answers#monthly-limit-behaviour)
### Output formats
**What is the difference between hosted accessible HTML and a tagged PDF?**
Hosted HTML is responsive, fast to publish, easy to edit, and generally gives assistive technology a more reliable reading experience. The automated tagged PDF rebuilds the same content for offline use and may change the original layout or pagination. Keeping the exact source-PDF appearance is a separate manual remediation path.
Source: https://docaccessible.com/remediation-options (canonical answer page: https://docaccessible.com/answers#hosted-html-vs-tagged-pdf)
**Will remediation preserve my PDF's exact layout?**
Only the manual path is designed to. Automated rebuilding can reflow a document, so pagination and visual placement may change. Manual exact-layout remediation repairs the accessibility structure without intentionally rebuilding the design, although a defect in the source file can still require a discussed visual adjustment.
Source: https://docaccessible.com/remediation-options (canonical answer page: https://docaccessible.com/answers#preserve-exact-layout)
**Can a scanned PDF be tagged automatically?**
No. A scanned page is an image with no text layer, so automatic tagging has no structure to work with. DocAccessible detects scanned and OCR-derived pages and routes them to reviewed OCR text recovery or to specialist remediation instead of producing a tag structure that would be wrong.
Source: https://docaccessible.com/tools/make-scanned-pdf-accessible (canonical answer page: https://docaccessible.com/answers#scanned-pdf-handling)
**Can my team edit the remediated result?**
Yes. The browser editor adjusts headings, alternative text, reading order, captions, and table structure. Saving runs the accessibility checks again, so the change in findings is visible immediately, and every saved version is retained as release evidence.
Source: https://docaccessible.com/features/document-accessibility-review (canonical answer page: https://docaccessible.com/answers#editing-the-result)
### Creating accessible PDFs
**Does Google Docs export a tagged, accessible PDF?**
Yes. Google announced on December 6, 2024 that PDFs downloaded from Google Docs include structural and accessibility tags for paragraphs, headings, hyperlinks, image alt text, and lists, with rollout complete by mid-January 2025 for Workspace and personal accounts, and added tags for tables, equations, and checkboxes in March 2025. The export tags only what the document declares, so headings must use heading styles and images need alt text, and the result should be checked with a tag viewer and checker.
Source: https://docaccessible.com/guides/google-docs-to-accessible-pdf (canonical answer page: https://docaccessible.com/answers#google-docs-tagged-pdf)
**Why does printing to PDF remove accessibility tags?**
A PDF printer receives drawing instructions for each page and has no concept of headings, lists, tables, or image descriptions, so the file it writes has no tag structure at all. In Word, Excel, and PowerPoint on Windows, use File, Save As, PDF, Options with "Document structure tags for accessibility" selected; on macOS use the "Best for electronic distribution and accessibility" export. Microsoft Print to PDF and third-party PDF printers should not be used for documents that must be accessible.
Source: https://docaccessible.com/guides/word-save-as-pdf-vs-print-to-pdf (canonical answer page: https://docaccessible.com/answers#print-to-pdf-loses-tags)
**Can Canva export an accessible PDF?**
Canva embeds accessibility tags when a design is downloaded as PDF Standard with the Flatten PDF checkbox unchecked; Canva states that flattening removes the tags. Heading levels follow the text styles (Title is H1, Subtitle H2, and so on), alt text and a screen reader language can be set, and reading order is calculated from position or matched to layer order. Canva documents that browser PDF viewers and macOS Preview may skip content, and recommends checking exported files in Adobe Acrobat.
Source: https://docaccessible.com/guides/canva-pdf-accessibility (canonical answer page: https://docaccessible.com/answers#canva-accessible-pdf)
**Can LaTeX produce an accessible tagged PDF?**
Yes, on a current LaTeX release. Placing \DocumentMetadata{tagging=on} before \documentclass and compiling with LuaLaTeX produces tagged output; pdfstandard=ua-2 targets PDF/UA-2, lang sets the language, and alt= on \includegraphics adds image descriptions. The LaTeX Project recommends LuaLaTeX and a release of 2025-11-01 or later, tracks support per package on its tagging status pages, and provides MathML-based tagged math through tagging-setup.
Source: https://docaccessible.com/guides/latex-accessible-pdf (canonical answer page: https://docaccessible.com/answers#latex-tagged-pdf)
**Does Chrome or Puppeteer generate tagged PDFs?**
Chrome has generated a tagged PDF from the print dialog's Save as PDF option since Chrome 85 in August 2020, carrying headings, lists, tables, paragraphs, and image descriptions from the page. Puppeteer's page.pdf() exposes a tagged option that defaults to true and an outline option for bookmarks that defaults to false. The tags mirror the HTML's semantics, so the page needs real headings, alt attributes, table headers, lang, and a title, and the output should be validated with a PDF/UA checker.
Source: https://docaccessible.com/guides/tagged-pdf-from-html-chrome-puppeteer-prince (canonical answer page: https://docaccessible.com/answers#chrome-puppeteer-tagged-pdf)
**Which applications export tagged PDFs?**
Microsoft Word, Excel, and PowerPoint (through Save As with the structure tags option, or the accessibility export on macOS), Google Docs (since December 2024), Apple Pages, Numbers, and Keynote (since version 8.2 in 2019), Canva (PDF Standard, not flattened), Adobe InDesign (with Create Tagged PDF), LaTeX (with tagging enabled), and Chrome (since version 85). Print-to-PDF drivers and scanners write no tags. A tagged export still needs headings, alt text, table headers, a title, and a language in the source.
Source: https://docaccessible.com/guides/which-apps-export-tagged-pdfs (canonical answer page: https://docaccessible.com/answers#which-apps-tagged-pdf)
### Standards and compliance
**What accessibility standards does DocAccessible check against?**
Every document receives automated checks mapped to WCAG 2.2 Level AA, covering structure, images, headings, tables, landmarks, language, and link text. The generated PDF is aligned to PDF/UA. Layout-critical or high-stakes documents still require manual validation.
Source: https://docaccessible.com/guides/wcag-2-2-aa (canonical answer page: https://docaccessible.com/answers#standards-checked)
**Does automated remediation certify WCAG, PDF/UA, or ADA compliance?**
No. Automated checking, scores, and generated output assist accessibility work but do not certify conformance, and no provider or automated checker should promise a universal legal guarantee. Reading order, complex tables, charts, forms, and contextual alternative text can require qualified human review with representative assistive technology.
Source: https://docaccessible.com/editorial-policy (canonical answer page: https://docaccessible.com/answers#conformance-certification)
**What is the difference between PDF/UA and WCAG?**
PDF/UA is a machine-checkable specification for the technical structure of a PDF file, so a checker can verify it deterministically. WCAG is an outcome-oriented standard about whether a person can actually perceive, operate, and understand the content. A file can pass PDF/UA validation and still fail WCAG, which is why the two complement rather than replace one another.
Source: https://docaccessible.com/guides/pdf-ua-vs-wcag (canonical answer page: https://docaccessible.com/answers#pdf-ua-vs-wcag)
**What is PDF/UA-2?**
PDF/UA-2 is ISO 14289-2, published in 2024, the accessibility standard for PDF files based on PDF 2.0. It was built from the PDF Association's free WTPDF specification and adds comprehensive rules for structure element attributes and annotations, PDF 2.0 structure types, MathML for mathematics, structure destinations for internal links, and Associated Files. PDF/UA-1 remains the standard for PDF 1.7 files and is not replaced; no major accessibility regulation names PDF/UA-2 as a legal requirement.
Source: https://docaccessible.com/guides/pdf-ua-2-explained (canonical answer page: https://docaccessible.com/answers#what-is-pdf-ua-2)
**What is the Matterhorn Protocol?**
The Matterhorn Protocol is the PDF Association's conformance testing model for PDF/UA-1. Version 1.1, released April 22, 2021, defines 31 checkpoints containing 136 failure conditions, each tied to a clause of ISO 14289-1. 87 of the conditions can be determined by software, 47 usually require human judgement, and 2 have no specific test. Checkers such as PAC report against these numbered conditions, which is why a clean automated report still leaves the human-judgement checks open.
Source: https://docaccessible.com/guides/matterhorn-protocol-explained (canonical answer page: https://docaccessible.com/answers#what-is-matterhorn-protocol)
**Is a PDF/A file accessible?**
Not necessarily. PDF/A (ISO 19005) is an archival standard for long-term preservation. Its level a variants (PDF/A-1a, 2a, 3a) require tags and Unicode text but only their presence, not their correctness, and PDF/A-4 makes tags optional. Accessibility is the job of PDF/UA (ISO 14289), which requires semantically correct structure, alternatives, language, title, and security settings that allow assistive technology. One file can conform to both, for example PDF/A-2a together with PDF/UA-1.
Source: https://docaccessible.com/guides/pdf-a-vs-pdf-ua (canonical answer page: https://docaccessible.com/answers#is-pdf-a-accessible)
**Does a PDF need bookmarks to be accessible?**
Adobe Acrobat's accessibility checker fails a document of 21 or more pages that has no bookmarks paralleling its structure, and WCAG technique PDF2 recommends bookmarks for navigation. PDF/UA-1 has no bookmark rule: the Matterhorn Protocol's navigation checkpoint states that no specific test is required. Bookmarks remain good practice for any long document and can be generated from headings in Word's Save As options, in Acrobat, and through Puppeteer's outline option.
Source: https://docaccessible.com/guides/pdf-document-settings-checkers-flag (canonical answer page: https://docaccessible.com/answers#pdf-bookmarks-required)
**What is a VPAT and how is it different from an ACR?**
A VPAT (Voluntary Product Accessibility Template) is the blank template published by the Information Technology Industry Council; a VPAT completed for a specific product version is an Accessibility Conformance Report (ACR). The current template is VPAT 2.5Rev (April 2025) in four editions: 508, EU (EN 301 549), WCAG (2.0, 2.1, and 2.2), and INT. Each criterion is rated Supports, Partially Supports, Does Not Support, or Not Applicable with remarks. ITI does not review or certify completed reports.
Source: https://docaccessible.com/guides/vpat-acr-explained (canonical answer page: https://docaccessible.com/answers#what-is-a-vpat)
**Are old PDFs exempt from the ADA Title II web rule?**
Only if they were available before the public entity's compliance date and are not currently used to apply for, gain access to, or participate in the entity's services, programs, or activities (28 CFR 35.201(b)). Any form, application, or instruction still in use is in scope regardless of age. Content kept purely for reference in a clearly identified archive area and unchanged since archiving is separately excepted, and the DOJ states that labelling content archived does not create the exception.
Source: https://docaccessible.com/guides/ada-title-ii-document-exceptions (canonical answer page: https://docaccessible.com/answers#title-ii-old-pdfs-exempt)
**Which PDF viewer should I use to test with a screen reader?**
Adobe Acrobat Reader on Windows with NVDA or JAWS is the reference environment for tagged PDF semantics, and Firefox is a strong second because its viewer has exposed tagged PDF structure since Firefox 89 in July 2021. PowerMapper's December 2025 tests scored NVDA with Firefox at 88% and JAWS with Firefox at 75% on tagged PDF features, against 25% for either screen reader with Chrome or Edge, whose shared viewer does not expose the same headings and table headers.
Source: https://docaccessible.com/guides/test-pdf-with-screen-reader (canonical answer page: https://docaccessible.com/answers#best-viewer-screen-reader-pdf-test)
### Deadlines
**When is the ADA Title II web accessibility deadline?**
State and local government entities with a population of 50,000 or more must comply by April 26, 2027. Public entities with a population under 50,000, and special district governments, have until April 26, 2028. The substantive technical requirement is WCAG 2.1 Level AA, and it applies to public-facing documents such as PDFs, not only to web pages.
Source: https://docaccessible.com/guides/ada-title-ii-2026 (canonical answer page: https://docaccessible.com/answers#ada-title-ii-deadline)
**When is the HHS Section 504 web accessibility deadline for health providers?**
May 11, 2027 for recipients of HHS financial assistance with fifteen or more employees, and May 10, 2028 for recipients with fewer than fifteen. HHS extended both dates by one year through an interim final rule effective May 7, 2026; they were originally May 11, 2026 and May 10, 2027. The technical standard is WCAG 2.1 Level AA for web content and mobile apps, including PDFs and other documents, and the rule's provisions mirror the ADA Title II web rule.
Source: https://docaccessible.com/guides/hhs-section-504-web-document-accessibility (canonical answer page: https://docaccessible.com/answers#hhs-section-504-deadline)
**When must Canadian federal organizations make documents accessible?**
Under the Regulations Amending the Accessible Canada Regulations registered December 5, 2025, the federal public sector must ensure new or updated web pages conform to CAN/ASC-EN 301 549:2024 from December 5, 2027, and new or updated non-web documents and mobile applications from December 5, 2028. Federally regulated businesses with 500 or more employees have December 5, 2028 for web pages, apps, and documents; those with 100 to 499 employees have that date for web pages only; smaller businesses are exempt.
Source: https://docaccessible.com/guides/canada-document-accessibility-aca-aoda (canonical answer page: https://docaccessible.com/answers#canada-document-accessibility-deadline)
**What does the European Accessibility Act require for documents?**
The European Accessibility Act (Directive 2019/882) has applied since June 28, 2025 to listed products and services including e-readers, e-books, consumer banking, and e-commerce. Its requirements are functional and set out in Annex I; it excludes office file formats published before June 28, 2025 from its website content requirements and exempts microenterprises providing services. EN 301 549, whose clause 10 applies WCAG-derived requirements to downloadable documents, is being revised to serve as the harmonised standard under the Act.
Source: https://docaccessible.com/guides/en-301-549-documents-eaa (canonical answer page: https://docaccessible.com/answers#eaa-documents)
**Do UK public sector PDFs published before September 2018 have to be accessible?**
Not unless users need them to use a service. GOV.UK lists PDFs and other documents published before 23 September 2018 among the content exempt from the Public Sector Bodies Accessibility Regulations 2018, except documents needed to use a service, such as a form. Documents published or updated since that date, or still needed for a service, must meet WCAG 2.2 AA, which the Government Digital Service has monitored against since October 2024.
Source: https://docaccessible.com/guides/uk-public-sector-pdf-accessibility (canonical answer page: https://docaccessible.com/answers#uk-old-pdfs)
**What is the deadline for Colorado HB21-1110?**
Colorado state and local government entities had to adopt an accessibility plan by July 1, 2022 and fully comply with the Office of Information Technology's accessibility standards, which set WCAG 2.1 Level AA, by July 1, 2024. HB24-1454 extended immunity from liability to July 1, 2025 for entities demonstrating good-faith efforts. That grace period has ended, and the statute provides a $3,500 statutory fine payable to each plaintiff for each violation. OIT states the law covers documents as well as websites and software.
Source: https://docaccessible.com/guides/colorado-hb21-1110-documents (canonical answer page: https://docaccessible.com/answers#colorado-hb21-1110-deadline)
### Free tools
**Is there a free PDF accessibility checker?**
Yes. DocAccessible publishes six free browser tools with no account required: a website PDF scanner, a PDF-to-HTML converter, an accessibility checker, a tag viewer, an auto-tagger, and a scanned-PDF text recovery tool. The checker runs machine-detectable structural and PDF/UA-oriented checks and keeps the findings that still need manual review.
Source: https://docaccessible.com/tools (canonical answer page: https://docaccessible.com/answers#free-pdf-accessibility-checker)
**How can I find every PDF published on a website?**
The free DocAccessible website PDF scanner takes a domain and lists the public PDFs the site links to, where each file is linked from, and automated checks on the most-linked files. It runs anonymously in the browser with no script to install and no account.
Source: https://docaccessible.com/tools/website-pdf-scanner (canonical answer page: https://docaccessible.com/answers#find-pdfs-on-a-website)
### Working with vendors
**Can our existing remediation vendor work through DocAccessible?**
Yes. Exchange is included in every software plan, so an existing vendor can be invited to a restricted, case-scoped portal. The workspace receives immutable revisions, records review decisions, and delivers one approved file through an expiring link. External vendors are restricted case participants rather than internal seats, and remediation labor is not included in any software plan.
Source: https://docaccessible.com/exchange (canonical answer page: https://docaccessible.com/answers#existing-vendor)
## Documentation index
### Start here
- [Get started with DocAccessible](https://docaccessible.com/docs/getting-started): Set up your workspace, choose the right workflow, and complete your first useful accessibility task.
- [Use the free PDF accessibility checker](https://docaccessible.com/docs/free-pdf-checker): Run a bounded structural inspection, interpret passed, failed, and manual-review findings, and decide the next remediation step.
- [Understand automation, conformance, and manual remediation](https://docaccessible.com/docs/accessibility-boundaries): Know what DocAccessible automates, what still requires human validation, and when exact-layout manual PDF remediation is the right path.
### Documents
- [Upload and remediate a document](https://docaccessible.com/docs/upload-and-remediate): Upload a PDF or DOCX, follow processing, and understand the outputs created by automated remediation.
- [Review findings and edit accessible content](https://docaccessible.com/docs/review-findings-and-edit): Interpret the automated score, resolve structure and alt-text issues, and save a new reviewed version.
- [Publish and share accessible output](https://docaccessible.com/docs/publish-and-share): Choose visibility, publish hosted HTML, and create controlled share links without exposing the private original.
- [Organize documents, folders, activity, and versions](https://docaccessible.com/docs/document-library-and-versions): Use the library to find documents, group work, inspect activity, and understand immutable version history.
- [Monitor processing jobs and retry failures](https://docaccessible.com/docs/processing-jobs-and-retries): Understand queued, running, completed, and failed remediation jobs and retry only when it is safe.
### Website monitoring
- [Connect a website and install PDF monitoring](https://docaccessible.com/docs/website-monitoring-setup): Verify a public domain, install the lightweight script, and begin building a bounded PDF inventory.
- [Install the website monitoring script](https://docaccessible.com/docs/install-website-script): Choose the right installation method, add the generated script once, and verify that DocAccessible can see it in your public page source.
- [Install the website script on WordPress](https://docaccessible.com/docs/install-script-wordpress): Add the DocAccessible script across a WordPress site using a managed code area or a child-theme hook, then clear caches and verify the public HTML.
- [Install the website script on Shopify](https://docaccessible.com/docs/install-script-shopify): Add the generated DocAccessible tag to Shopify theme.liquid, publish the correct theme, and verify it on the public storefront.
- [Install the website script on Webflow](https://docaccessible.com/docs/install-script-webflow): Use Webflow's site-level Footer code, publish to the connected custom domain, and confirm the site key in the live page source.
- [Install the website script on Wix](https://docaccessible.com/docs/install-script-wix): Add DocAccessible through Wix Custom Code on every page, place it at Body - end, and verify the published connected domain.
- [Install the website script on Squarespace](https://docaccessible.com/docs/install-script-squarespace): Add the generated tag through Squarespace Footer code injection, save it site-wide, and verify a public page outside the editor.
- [Install the website script on Drupal or Joomla](https://docaccessible.com/docs/install-script-drupal-joomla): Add DocAccessible through the active CMS theme or asset manager, preserve the site-key attribute, clear caches, and verify rendered source.
- [Install the website script on a custom-built site](https://docaccessible.com/docs/install-script-custom-sites): Add the generated tag to static HTML, shared server templates, React or Vite entry HTML, or a Next.js root layout without breaking verification.
- [Tag managers and client-only script installation](https://docaccessible.com/docs/script-installation-tag-managers): Understand why Google Tag Manager and runtime-only injection cannot complete secure website verification, and move the tag to a supported global template.
- [Review website PDF inventory and source changes](https://docaccessible.com/docs/website-pdf-inventory): Prioritize discovered PDFs, read scan history, handle plan limits, and respond when a public source changes.
- [Convert a discovered PDF and publish an accessible alternative](https://docaccessible.com/docs/publish-website-alternatives): Create a private remediation draft from a public PDF, review it, and explicitly map one completed version for website visitors.
### Exchange
- [Create and manage an Exchange case](https://docaccessible.com/docs/exchange-cases): Set acceptance criteria, invite a scoped vendor, and keep source files, deadlines, and activity in one controlled case.
- [Review, approve, and deliver Exchange work](https://docaccessible.com/docs/exchange-review-and-delivery): Compare immutable revisions, verify evidence, request changes, approve the right submission, and create controlled delivery access.
### Collaboration
- [Request review and approve an exact version](https://docaccessible.com/docs/review-and-approval): Assign a reviewer, track due work, request changes, and bind approval to the version that was actually reviewed.
- [Collect and resolve reader accessibility feedback](https://docaccessible.com/docs/accessibility-feedback): Use hosted-document feedback to reproduce barriers, assign ownership, record resolution, and close the loop with readers.
- [Run an accessibility program hub](https://docaccessible.com/docs/program-hub): Collect client requests, choose a defensible remediation path, coordinate work across workspaces, and record version-bound release evidence.
- [Set up an organization document portal](https://docaccessible.com/docs/organization-portals): Reserve a managed organization hostname, invite your team, configure the public directory, and publish reviewed document versions safely.
### Account and operations
- [Manage workspaces, members, invitations, and roles](https://docaccessible.com/docs/members-workspaces-and-roles): Keep work in the right workspace, invite teammates, assign least-privilege roles, and transfer ownership carefully.
- [Manage account access, security, export, and deletion](https://docaccessible.com/docs/account-security-and-data): Verify account access, recover or change a password, export your documents, and understand permanent account deletion.
- [Use API keys and signed webhooks](https://docaccessible.com/docs/api-keys-and-webhooks): Create scoped integration credentials, verify signed webhook deliveries, and operate integrations without exposing secrets.
- [Understand plans, billing, and usage limits](https://docaccessible.com/docs/plans-billing-and-usage): Read workspace allowances, choose a plan, start checkout, and understand which limits apply to each workflow.
- [Get support and report an accessibility barrier](https://docaccessible.com/docs/contact-support): Send enough context for a useful response without putting confidential documents or sensitive credentials into the contact form.
## Documentation articles
### Get started with DocAccessible
Canonical URL: https://docaccessible.com/docs/getting-started
Set up your workspace, choose the right workflow, and complete your first useful accessibility task.
- Category: Start here
- Audience: New workspace owners and contributors
- Estimated time: 10 minutes
#### Prerequisites
- A verified DocAccessible account
- A PDF or DOCX you are permitted to upload, or a public website you manage
#### Procedure
1. **Confirm the active workspace.** Use the workspace switcher in the app header before creating documents, sites, or Exchange cases. Every record belongs to the active workspace.
2. **Choose the workstream.** Use Documents for automated checking and editable output, Website monitoring for public PDF inventory, or Exchange for vendor-managed remediation.
3. **Start with one real task.** Upload one representative document, connect one verified website, or create one Exchange case. Small first runs make the review and publishing boundaries easier to understand.
4. **Review before publishing.** Treat automated findings and generated output as assistance. Resolve manual-review items and validate important content with people and assistive technology before release.
#### What the dashboard shows
The dashboard brings document usage, website inventory, Exchange capacity, priority findings, recent work, and the next recommended action into one view.
Plan limits are workspace-specific. A visible button does not override an API entitlement or role requirement.
#### Private by default
Uploaded originals and generated drafts remain private until an authorized user explicitly changes visibility or creates a share link. Website discoveries also remain workspace records until a completed version is deliberately mapped for publication.
#### Related documentation
- [Upload and remediate a document](https://docaccessible.com/docs/upload-and-remediate)
- [Connect a website and install PDF monitoring](https://docaccessible.com/docs/website-monitoring-setup)
- [Create and manage an Exchange case](https://docaccessible.com/docs/exchange-cases)
### Upload and remediate a document
Canonical URL: https://docaccessible.com/docs/upload-and-remediate
Upload a PDF or DOCX, follow processing, and understand the outputs created by automated remediation.
- Category: Documents
- Audience: Document owners and remediation contributors
- Estimated time: 5 minutes plus processing
#### Prerequisites
- An active plan with remaining remediation allowance
- A supported PDF or DOCX within the plan file-size limit
#### Procedure
1. **Open Start new work.** From the dashboard, go to the upload area. If you selected a folder first, new documents are placed in that folder.
2. **Select or drop files.** Choose one or more PDF or DOCX files. The browser shows each file's queued, uploading, completed, or failed state.
3. **Wait for a terminal result.** The private original is validated and queued for isolated processing. The document page updates when the job succeeds or fails.
4. **Review the generated version.** Open the document to inspect its score, machine-detectable findings, AI source comparison when available, unresolved manual checks, hosted HTML, rebuilt tagged PDF, and audit report.
#### Outputs and their purpose
Hosted HTML is responsive, editable, and usually the strongest reading experience. The rebuilt tagged PDF is intended for offline use and may reflow or simplify the original layout.
- The original file remains private storage input.
- Each completed run creates an immutable version.
- The audit report records automated evidence, not certification.
#### How AI source comparison works
For eligible PDFs, a constrained structure pass can propose only complete block order or heading and paragraph classification. A separate fidelity pass compares the final blocks with the original PDF and reports content, semantic, and reading-order confidence plus a conservative route.
The confidence values are review signals, not accessibility scores or permission to publish. Provider failure, configured limits, and editor changes leave an explicit manual source-comparison requirement instead of silently reusing confidence.
#### If an upload is rejected
Check the real file type, file size, remaining monthly allowance, and whether the current plan includes automated remediation. A renamed or damaged file can fail content validation even when its extension looks correct.
#### Related documentation
- [Review findings and edit accessible content](https://docaccessible.com/docs/review-findings-and-edit)
- [Monitor processing jobs and retry failures](https://docaccessible.com/docs/processing-jobs-and-retries)
- [Understand plans, billing, and usage limits](https://docaccessible.com/docs/plans-billing-and-usage)
### Review findings and edit accessible content
Canonical URL: https://docaccessible.com/docs/review-findings-and-edit
Interpret the automated score, resolve structure and alt-text issues, and save a new reviewed version.
- Category: Documents
- Audience: Remediation contributors and accessibility reviewers
- Estimated time: Varies by document
#### Prerequisites
- A document with a completed processed version
#### Procedure
1. **Open a completed document.** Select the document from the library and begin with critical and needs-review findings rather than the score alone.
2. **Inspect structure and context.** Check headings, reading sequence, lists, links, tables, image purpose, document language, and any item that software could not responsibly decide. When AI source comparison is available, review its exact concerns and route without treating confidence as conformance.
3. **Open Edit.** Use the findings rail to jump to affected blocks, then correct headings, text, alt text, captions, table structure, lists, callouts, and reading order. Switch to Preview to inspect the unsaved accessible output, draft score, heading outline, and reading sequence before creating a version. AI-generated image descriptions are drafts and need contextual review.
4. **Save and recheck.** Saving creates a new immutable version and reruns applicable deterministic checks. If blocks changed, the prior AI source comparison becomes stale because it was bound to the earlier output. Revisit unresolved manual items before publishing or requesting approval.
#### How to use the score
The score is a prioritization signal based on available automated evidence. It is not proof of WCAG, PDF/UA, ADA, or Section 508 conformance, and it should not be used as the only release gate.
#### Manual review still matters
Reading order, complex tables, charts, forms, language changes, meaningful image descriptions, and the assistive-technology experience can require a qualified person. Keep those decisions visible in your review record.
#### Related documentation
- [Upload and remediate a document](https://docaccessible.com/docs/upload-and-remediate)
- [Request review and approve an exact version](https://docaccessible.com/docs/review-and-approval)
- [Understand automation, conformance, and manual remediation](https://docaccessible.com/docs/accessibility-boundaries)
### Publish and share accessible output
Canonical URL: https://docaccessible.com/docs/publish-and-share
Choose visibility, publish hosted HTML, and create controlled share links without exposing the private original.
- Category: Documents
- Audience: Document owners and publishers
- Estimated time: 5 minutes
#### Prerequisites
- A completed document version that has been reviewed for release
#### Procedure
1. **Choose the delivery format.** Use hosted HTML for responsive online reading. Use the rebuilt tagged PDF when an offline file is required and layout changes are acceptable.
2. **Set document visibility.** Keep the canonical hosted page private, make it unlisted, or publish it publicly. A separate viewing link can provide revocable access to a private document without changing that visibility.
3. **Create a viewing link when needed.** Create a view-only link for someone outside the workspace, choose an expiry, and add a password on eligible plans. Viewing links never grant editing access; invite an authenticated workspace member when collaboration is required.
4. **Test the reader experience.** Open the published URL in a private browser window and check keyboard navigation, headings, links, zoom, mobile reflow, and representative assistive technology.
#### Publication and versions
A later edit creates a new version. Existing review decisions remain bound to the version that was reviewed, so confirm the current version before release.
#### Revoke access
Revoke a viewing link when that recipient no longer needs access. The token, protected document view, and token-bound file downloads stop working immediately. Separately return the canonical page to private when public or unlisted access should also end.
#### Related documentation
- [Request review and approve an exact version](https://docaccessible.com/docs/review-and-approval)
- [Organize documents, folders, activity, and versions](https://docaccessible.com/docs/document-library-and-versions)
- [Collect and resolve reader accessibility feedback](https://docaccessible.com/docs/accessibility-feedback)
### Organize documents, folders, activity, and versions
Canonical URL: https://docaccessible.com/docs/document-library-and-versions
Use the library to find documents, group work, inspect activity, and understand immutable version history.
- Category: Documents
- Audience: All workspace users
- Estimated time: 5 minutes
#### Prerequisites
- At least one uploaded document for version and activity examples
#### Procedure
1. **Filter the library.** Search by title, slug, or visibility. Use All documents, Uncategorized, or a named folder to narrow the list.
2. **Create folders.** Add a folder for a department, release, owner, or campaign. Deleting a folder does not delete its documents; they become uncategorized.
3. **Move a document.** Open the document and use its folder control to place it in another collection without changing the document URL or version.
4. **Review activity and versions.** Use the activity timeline for meaningful lifecycle events and version history for immutable output snapshots and scores.
#### Version rules
Edits and new remediation outputs create versions rather than overwriting review evidence. Approval, website publication, and other release decisions must refer to the exact intended version.
#### Related documentation
- [Review findings and edit accessible content](https://docaccessible.com/docs/review-findings-and-edit)
- [Request review and approve an exact version](https://docaccessible.com/docs/review-and-approval)
- [Monitor processing jobs and retry failures](https://docaccessible.com/docs/processing-jobs-and-retries)
### Request review and approve an exact version
Canonical URL: https://docaccessible.com/docs/review-and-approval
Assign a reviewer, track due work, request changes, and bind approval to the version that was actually reviewed.
- Category: Collaboration
- Audience: Owners, admins, contributors, and assigned reviewers
- Estimated time: 5 minutes to set up
#### Prerequisites
- A completed document version
- A plan and workspace role that permit review workflows
#### Procedure
1. **Open the document review panel.** From a completed document, create a review for the current version and choose an eligible workspace member.
2. **Add context and a due date.** Describe the release decision the reviewer is making and add a realistic due date when timing matters.
3. **Review the exact version.** The reviewer checks findings, content, output, and required manual evidence before approving or requesting changes.
4. **Treat superseded reviews correctly.** If a newer version is created, the earlier approval does not transfer. Start or complete a review for the new version.
#### Use the review queue
The Reviews page separates work assigned to you from requests you created. Status, due date, reviewer, version, and superseded state remain visible for follow-up.
#### What approval means
Approval records a workspace decision about an exact version. It does not certify accessibility and does not replace the manual validation required by the document's purpose and risk.
#### Related documentation
- [Review findings and edit accessible content](https://docaccessible.com/docs/review-findings-and-edit)
- [Publish and share accessible output](https://docaccessible.com/docs/publish-and-share)
- [Manage workspaces, members, invitations, and roles](https://docaccessible.com/docs/members-workspaces-and-roles)
### Monitor processing jobs and retry failures
Canonical URL: https://docaccessible.com/docs/processing-jobs-and-retries
Understand queued, running, completed, and failed remediation jobs and retry only when it is safe.
- Category: Documents
- Audience: Document owners and operators
- Estimated time: 3 minutes
#### Prerequisites
- At least one uploaded document
#### Procedure
1. **Open Processing jobs.** Use the app's More menu or a failed document's View history link to inspect recent work.
2. **Read the terminal state.** Queued and running jobs should progress automatically. Succeeded jobs have version outputs. Failed jobs display sanitized, user-safe context.
3. **Retry once after a transient failure.** Use Retry when the UI offers it. The system creates a new processing attempt without pretending the failed attempt succeeded.
4. **Escalate repeated failures.** If the same file fails again, contact support with the document title, approximate time, and visible error. Do not email confidential source files.
#### Common causes
Damaged files, unsupported structures, malware-scan failures, parser limits, provider failures, or worker resource limits can stop processing. Raw system errors and document content are intentionally not exposed in the browser.
#### Related documentation
- [Upload and remediate a document](https://docaccessible.com/docs/upload-and-remediate)
- [Get support and report an accessibility barrier](https://docaccessible.com/docs/contact-support)
- [Understand automation, conformance, and manual remediation](https://docaccessible.com/docs/accessibility-boundaries)
### Connect a website and install PDF monitoring
Canonical URL: https://docaccessible.com/docs/website-monitoring-setup
Verify a public domain, install the lightweight script, and begin building a bounded PDF inventory.
- Category: Website monitoring
- Audience: Website owners and workspace admins
- Estimated time: 10-20 minutes
#### Prerequisites
- Control of a public website
- Permission to add one script tag to the site's pages or template
#### Procedure
1. **Connect the public domain.** Enter the website origin in Website monitoring. The entered host becomes the crawl origin and consumes the applicable domain allowance.
2. **Copy the generated script tag.** Open the connected website, copy its exact installation code, then use the platform-specific guide to add it once to the global footer or shared server-rendered template.
3. **Load a page on the connected domain.** The first same-domain report starts verification. The server fetches that page and confirms the matching key is present on the script tag.
4. **Confirm verification and inventory.** Return to the site dashboard. After verification, discoveries and bounded scans appear asynchronously as visitors or scheduled checks encounter PDF links.
#### What the script observes
The script reports normalized PDF URLs and the same-domain page where each link appears. It does not collect visitor identity, cookies, form values, or page content.
#### Verification requirements
A browser Origin header is not ownership proof. The public page must load the matching script key, and outbound fetching stays inside the connected domain and its allowed subdomains.
#### Choose your website platform
Use the guide that matches the system responsible for the final public HTML. Every route ends with the same check: open a public page, view its source, and confirm the exact generated site key is present before waiting for verification.
- [WordPress](https://docaccessible.com/docs/install-script-wordpress): Use a site-wide code tool or a child-theme hook without editing the parent theme.
- [Shopify](https://docaccessible.com/docs/install-script-shopify): Add the generated tag to theme.liquid and keep the change with the active theme.
- [Webflow](https://docaccessible.com/docs/install-script-webflow): Use site-level Footer code, publish the site, and verify the custom domain.
- [Wix](https://docaccessible.com/docs/install-script-wix): Add custom code to every page at Body - end and confirm it survives publication.
- [Squarespace](https://docaccessible.com/docs/install-script-squarespace): Use site-wide Footer code injection on an eligible plan.
- [Drupal or Joomla](https://docaccessible.com/docs/install-script-drupal-joomla): Install through the active theme or the CMS asset manager and clear caches.
- [Custom HTML, React, Next.js, and server frameworks](https://docaccessible.com/docs/install-script-custom-sites): Place the script in the shared server-rendered layout so it appears in page source.
- [Google Tag Manager and client-only injection](https://docaccessible.com/docs/script-installation-tag-managers): Understand why runtime-only tags cannot complete verification and choose a supported route.
#### Related documentation
- [Install the website monitoring script](https://docaccessible.com/docs/install-website-script)
- [Review website PDF inventory and source changes](https://docaccessible.com/docs/website-pdf-inventory)
- [Convert a discovered PDF and publish an accessible alternative](https://docaccessible.com/docs/publish-website-alternatives)
### Install the website monitoring script
Canonical URL: https://docaccessible.com/docs/install-website-script
Choose the right installation method, add the generated script once, and verify that DocAccessible can see it in your public page source.
- Category: Website monitoring
- Audience: Website administrators, developers, and agency partners
- Estimated time: 10-30 minutes
#### Prerequisites
- A connected website in DocAccessible
- The exact installation code copied from that website's Installation tab
- Permission to publish site-wide code on the connected public domain
#### Procedure
1. **Open the connected website.** In Website monitoring, select the domain you are installing and open Installation. Do not reuse code from another connected website because every domain has a different public site key.
2. **Copy the complete generated tag.** Choose Copy installation code. Keep the script URL, async attribute, and data-site-key exactly as generated.
3. **Choose the global installation point.** Use your CMS's site-wide Footer or Body - end code area, the shared server-rendered layout, or the active theme's supported asset system. Add the tag once, not once per PDF.
4. **Publish the website change.** Save and publish the real production site. Clear application, CMS, host, and CDN caches when they can continue serving older HTML.
5. **Open a public page on the connected domain.** Visit a normal public page that includes the script. This first browser report starts verification and provides the exact page that DocAccessible will fetch.
6. **Confirm source and connection status.** Use View page source and search for your data-site-key. Then return to Installation and wait for Script connected. Only after verification can scheduled checking and approved visitor mappings operate normally.
#### What the generated code looks like
The example below shows the shape of the tag. YOUR_SITE_KEY is only a placeholder. Always paste the exact code from the connected website so the service origin and key match your workspace record.
**Example only - use the code from your Installation tab**
~~~text
~~~
#### Choose your platform
Select the system that produces the public website. If an agency, managed host, or custom theme controls the final HTML, send them the custom-site guide together with the generated tag.
- [WordPress](https://docaccessible.com/docs/install-script-wordpress): Use a site-wide code tool or a child-theme hook without editing the parent theme.
- [Shopify](https://docaccessible.com/docs/install-script-shopify): Add the generated tag to theme.liquid and keep the change with the active theme.
- [Webflow](https://docaccessible.com/docs/install-script-webflow): Use site-level Footer code, publish the site, and verify the custom domain.
- [Wix](https://docaccessible.com/docs/install-script-wix): Add custom code to every page at Body - end and confirm it survives publication.
- [Squarespace](https://docaccessible.com/docs/install-script-squarespace): Use site-wide Footer code injection on an eligible plan.
- [Drupal or Joomla](https://docaccessible.com/docs/install-script-drupal-joomla): Install through the active theme or the CMS asset manager and clear caches.
- [Custom HTML, React, Next.js, and server frameworks](https://docaccessible.com/docs/install-script-custom-sites): Place the script in the shared server-rendered layout so it appears in page source.
- [Google Tag Manager and client-only injection](https://docaccessible.com/docs/script-installation-tag-managers): Understand why runtime-only tags cannot complete verification and choose a supported route.
#### The page-source check that matters
DocAccessible does not treat a browser request alone as proof that you control the domain. Its worker fetches the reported public page and looks for the official script URL with the exact site key in the returned HTML.
- Use View page source, not only the browser Elements panel.
- Search for data-site-key and compare the complete value with the Installation tab.
- Confirm the page URL uses the same connected host and HTTPS origin.
- Do not install only through a tag manager, useEffect, or another client-only loader.
#### Content Security Policy
A restrictive Content Security Policy must allow the exact DocAccessible origin shown in your generated tag. Merge the origin into the existing directives; do not replace the website's complete policy with this example.
- script-src permits the browser to load /site/v1.js.
- connect-src permits inventory reports and approved viewer requests.
- img-src permits images in an approved accessible viewer.
**CSP directive example**
~~~text
script-src 'self' https://docaccessible.com;
connect-src 'self' https://docaccessible.com;
img-src 'self' data: https://docaccessible.com;
~~~
#### If verification does not complete
Start with the source check because it separates publishing problems from network or policy problems. After each correction, open a fresh public page and return to the Installation tab.
- Wrong key: remove old or duplicate tags and paste the current connected website's code.
- Missing from source: move the tag from a client-only component into the CMS global code area or server-rendered layout.
- Old source: purge page, host, reverse-proxy, and CDN caches, then reload in a private window.
- Blocked request: inspect the browser console for Content Security Policy, extension, consent, or network errors.
- Wrong host: install and open a page on the exact connected domain, including the intended www or non-www host.
- Private page: choose a publicly reachable page without authentication, maintenance mode, or an IP allowlist.
#### Move or remove the installation safely
Keep only one copy of the script per rendered page. When changing themes or platforms, install and verify the tag in the replacement before removing the old implementation.
Disconnecting the website removes its inventory and viewer mappings. Removing only the script stops new browser discoveries but does not automatically delete workspace records.
#### Related documentation
- [Connect a website and install PDF monitoring](https://docaccessible.com/docs/website-monitoring-setup)
- [Install the website script on a custom-built site](https://docaccessible.com/docs/install-script-custom-sites)
- [Tag managers and client-only script installation](https://docaccessible.com/docs/script-installation-tag-managers)
### Install the website script on WordPress
Canonical URL: https://docaccessible.com/docs/install-script-wordpress
Add the DocAccessible script across a WordPress site using a managed code area or a child-theme hook, then clear caches and verify the public HTML.
- Category: Website monitoring
- Audience: WordPress administrators, developers, and managed-host teams
- Estimated time: 10-25 minutes
#### Prerequisites
- Administrator or deployment access to the WordPress site
- The generated installation code for this exact domain
- A current backup or staging environment before editing theme code
#### Procedure
1. **Copy the generated installation code.** Open the connected website in DocAccessible, choose Installation, and copy the complete tag. Keep the site key unchanged.
2. **Use the site's supported global-code method.** If your managed host or active theme provides a site-wide footer or body-end code area, use that supported tool. Configure it for the public front end and every page.
3. **Use a child theme when code is required.** Ask a WordPress developer to add the tag through a child theme or a small site-owned plugin. Do not edit the parent theme because an update can erase the change.
4. **Publish and clear every cache layer.** Save the change, deploy it, and purge WordPress page caches, optimization plugins, managed-host caches, and the CDN when present.
5. **Check a logged-out public page.** Open a normal page in a private window, use View page source, and search for the exact data-site-key. Admin previews can differ from cached visitor HTML.
6. **Confirm Script connected.** Reload the public page once, then return to the website Installation tab. If verification fails, compare the page-source key before changing anything else.
#### Choose the safest WordPress method
WordPress core does not provide one universal site-wide script field. Managed hosts, commercial themes, and governance plugins expose different labels, so prefer the installation mechanism already approved for that site.
- Best for site admins: an existing site-wide Footer or Body - end code area.
- Best for development teams: a child theme or small site-owned plugin under version control.
- Avoid: editing footer.php or functions.php in the parent theme.
- Avoid: adding a Custom HTML block to one page, because monitoring should cover the shared template.
#### Optional child-theme hook
A developer can add the exact generated tag from the child theme's functions.php. Replace the placeholder tag below with the installation code copied from DocAccessible, then review it through the normal deployment process.
**Child theme functions.php example**
~~~text
function docaccessible_add_site_script() {
?>
. Do not put it inside a product, collection, or section template that renders only on some pages.
5. **Save, preview, and publish the intended theme.** Save the file. If you edited a duplicate theme, preview it first and publish that theme only after confirming the storefront still works normally.
6. **Verify the live storefront source.** Open a public storefront page without the theme preview parameter, view page source, search for data-site-key, then return to DocAccessible and confirm Script connected.
#### Placement in theme.liquid
The installation belongs at the end of the shared storefront layout. Use the tag from DocAccessible in place of the placeholder example.
**Layout/theme.liquid placement**
~~~text