Frequently asked questions

Everything you need to know about the Inkable Docs add-on and how it keeps your Google Docs accessible. Need more help? Reach out to support@inkabledocs.com.

How does Inkable Docs evaluate document accessibility?

Inkable Docs evaluates documents against the Matterhorn Protocol and ISO 14289-1 (PDF/UA) standards. We perform real-time structural and semantic checks, including heading hierarchy, table tag validity, and image alt text presence.

What accessibility evidence does Inkable Docs produce?

Inkable Docs generates detailed accessibility reports and conformance evidence. These reports can be shared with disability services and procurement teams to verify that your documents meet institutional inclusivity standards.

What part of the accessibility process is automated?

We automate structural validation and provide AI-driven suggestions for alt text. However, we maintain a human-in-the-loop workflow for critical decisions, such as marking an image as decorative or verifying the context of automated fixes.

How can university procurement teams review Inkable Docs output?

Procurement officers can review our automated accessibility reports and verified PDF/UA output. This provides objective evidence that documents created with Inkable Docs meet Section 508 and WCAG 2.1 requirements.

How does Inkable Docs reduce organizational risk?

By identifying and fixing accessibility barriers at the source, Inkable Docs reduces the risk of publishing non-compliant documents that could trigger legal challenges or fail institutional audits.

What permissions does Inkable need?

We request access to read the document you have open so we can surface headings, lists, and images and provide in-doc guidance. We do not sell or train models on your content. Want the full breakdown? See our permissions explainer.