Google Workspace Accessibility Conformance Report: Where to Find the Official ACR
If you need an official Google Workspace accessibility conformance report, start with Google's own accessibility conformance report library. Then use document-level auditing to understand whether your own Workspace files are accessible in practice.

Accessibility conformance reports, often called ACRs or VPATs, help organizations evaluate how a product supports accessibility standards. For Google Workspace, the official source is Google. That distinction matters: an outside tool can help audit the accessibility of your files, but it should not pretend to be the official conformance report for Google's products.
Official Google source
Google publishes accessibility conformance reports through its official accessibility resources. For procurement or legal review, use the latest report directly from Google for the specific Workspace product you are evaluating.
Open Google compliance reportsWhat an official report can and cannot tell you
An official Google Workspace accessibility conformance report can help answer whether a Google product documents support for accessibility criteria. It is especially useful for vendor review, procurement files, internal risk registers, and compliance documentation.
It does not automatically prove that every document, slide deck, spreadsheet, or PDF your organization stores in Google Drive is accessible. Product conformance and content accessibility are related, but they are not the same thing.
Procurement review
Use Google's official ACRs to understand how Google Workspace products document support for WCAG, Section 508, and EN 301 549 criteria.
Risk documentation
Attach the relevant official report to vendor files, accessibility reviews, security questionnaires, and institutional compliance records.
Content governance
Pair product-level conformance documentation with audits of the Docs, Slides, Sheets, and PDFs your organization actually creates.
How to use the report in an accessibility workflow
Treat the official ACR as one part of a larger evidence package. It can document the platform's accessibility posture, while your internal audit should document the accessibility of the content people publish through that platform.
- Download the current official report: Use Google's report library and select the Workspace product or service under review.
- Match it to the use case: A report for one Google product may not answer questions about another product, add-on, exported PDF, or custom workflow.
- Keep a dated copy: Store the report with procurement, accessibility, or vendor documentation so reviewers know what version was evaluated.
- Audit your own files: Check Docs, Slides, Sheets, and PDFs for document-specific barriers such as missing alt text, skipped headings, unclear links, table issues, and low contrast.
Why content audits still matter
Google Workspace gives teams a powerful place to create and share content. But authors still control many accessibility-critical choices: whether headings are real headings, whether images have useful descriptions, whether links make sense out of context, whether tables have headers, and whether PDFs preserve accessible structure after export.
The official Google report helps evaluate the platform. A file accessibility audit helps evaluate the documents your institution actually shares.
A practical checklist for teams
The bottom line
For an official Google Workspace accessibility conformance report, go to Google. For confidence that your own Google Workspace files are accessible, audit the content itself. Institutions need both: product-level documentation for governance and file-level checks for the real materials people read, teach from, and rely on.
Audit the Files Behind the Report
Install Inkable Docs to scan Google Docs for accessibility issues and help authors fix barriers before files are shared or exported.
Install Google Workspace Extension