Frequently asked questions

Everything you need to know about how Inkable checks, fixes, and documents accessibility across authoring tools, LMS course materials, and PDF workflows. Need more help? Reach out to support@inkabledocs.com.

How does Inkable Docs evaluate document accessibility?

Inkable Docs runs checks aligned with WCAG, Section 508, and PDF/UA requirements. Coverage depends on the document type and workflow; reports identify the checks performed and remaining issues.

Does Inkable Docs rely on visual formatting to remediate documents?

No. It checks the document or tagged-output structure used by assistive technology. Automated changes depend on the format and issue; unsupported items remain for review.

Can one automated remediation step make a document fully compliant?

Automated remediation fixes supported issues, but final review is still required. Its results provide evidence for a publication decision, not blanket compliance certification.

Which document structures does Inkable Docs check?

Depending on the workflow, checks may include headings, lists, tables, links, reading order, language, contrast, and image or drawing alt text. Available checks vary by format.

How does Inkable Docs show whether remediation was successful?

Reports show the checks run, fixes applied, warnings, and remaining or deferred issues. Use that evidence to review the output rather than relying on a single status indicator.

What still requires human review after automated checks or fixes?

Review context-dependent decisions such as alt text, decorative images, complex tables, reading order, and content outside the supported checks.

Does Inkable only work with Google Workspace?

No. Workflows cover Google Workspace, Microsoft 365 files, PDFs, and LMS content including Canvas, D2L Brightspace, Blackboard Ultra, and Moodle. Capabilities vary by integration and file type.

What accessibility evidence does Inkable Docs produce?

Inkable produces accessibility reports, issue summaries, and—where remediation is supported—records of applied, remaining, or deferred checks. These support internal review but do not establish conformance by themselves.

What part of the accessibility process is automated?

Inkable automates accessibility checks and supported fixes. AI can assist with tasks such as headings, alt text, titles, tables, links, language, and document structure. Results are checked, and reports identify unresolved or deferred items for review.

How can university procurement teams review Inkable Docs output?

Teams can review reports, issue-level results, remediation records, and applicable PDF/UA checks. These provide evaluation evidence but do not replace review of the final document.

How does Inkable Docs reduce organizational risk?

By identifying barriers early, applying supported fixes, and recording what remains, Inkable helps teams reduce the risk of publishing inaccessible documents.

What permissions does Inkable need?

Inkable requests Google permissions to inspect and, where supported, update documents you choose to process. We act when you initiate a check or fix, and we do not sell or train models on your content. Want the full breakdown? See our permissions explainer.