Inkable Docs

How does Inkable Docs evaluate document accessibility?

Inkable Docs evaluates documents against WCAG, Section 508, and ISO 14289-1 (PDF/UA) expectations. We perform structural and semantic checks including heading hierarchy, table validity, link purpose, reading order, and image alt text.

Does Inkable only work with Google Workspace?

No. Google Workspace remains an important surface, but Inkable Docs is expanding document accessibility workflows across Microsoft 365, LMS environments such as Canvas, D2L Brightspace, Blackboard Ultra, and Moodle, and PDF review workflows.

What accessibility evidence does Inkable Docs produce?

Inkable Docs generates accessibility reports, issue summaries, and remediation evidence. These records can be shared with disability services, instructional design, IT, and procurement teams to document progress against institutional 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?

Inkable requests the access needed to review the documents or files you ask it to check, surface accessibility issues, and provide remediation guidance. We do not sell or train models on your content. Want the full breakdown? See our permissions explainer.