Skip to content

docs: add links to ACR #9975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maribethb merged 2 commits into from
Jun 11, 2026
+15 −10
Merged

docs: add links to ACR #9975

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c180741
chore(docs): add ACR links to compliance page
rachel-fenichel Jun 11, 2026
8892191
chore(docs): use published versions of ACRs
rachel-fenichel Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 15 additions & 10 deletions packages/docs/docs/guides/app-integration/accessibility/compliance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,16 +27,21 @@ blocks and fields) is instantiated on a web page with other contents.

## Creating an ACR

Blockly provides an accessibility compliance report (ACR) in the VPAT format,
which you can use to write an ACR for your full application. No part of
Blockly's ACR provides information about page contents outside of the Blockly
region. The ACR covers use as both web content and authoring tool.

If a Blockly integration exists as a standalone portion of a larger web page
we recommend creating one ACR for only the Blockly portions of the page, then
integrating that into a larger ACR assessing the full page. For instance, a
page with a Blockly-based editor and a simulated output window should assess the
accessibility of the two regions separately.
Blockly provides two accessibility compliance reports (ACR) in the VPAT format,
which you can use to write an ACR for your full application:
- The [core Blockly ACR](https://docs.google.com/document/d/e/2PACX-1vRR6Tb_n3zzrsI-p2uTLZIPj6AaKxJuLKbXLsRnjfyN0OA8RMhsA51Fn5ujGC8LLR0_REFzYJ4mzpR5/pub)
applies to the use of the core library, fields, and blocks. This applies to use
of Blockly as web content.
- The [extended Blockly ACR](https://docs.google.com/document/d/e/2PACX-1vTkwFqJRUm7kkHpJ8IAn3iwjJv7OxIhpMnQxeURLmK-4NN5EF7TZ6CoC7TmTvUFsyMw16FTiM54ZTIE/pub)
applies to the use of Blockly with custom fields and blocks. This applies to use
of Blockly as an authoring tool.

No part of Blockly's ACR provides information about page contents outside of the
Blockly region. If a Blockly integration exists as a standalone portion of a
larger web page we recommend creating one ACR for only the Blockly portions of
the page, then integrating that into a larger ACR assessing the full page. For
instance, a page with a Blockly-based editor and a simulated output window
should assess the accessibility of the two regions separately.

Developers building with Blockly can assess the accessibility of their Blockly
integration by checking customizations against the criteria marked “Developer
Expand Down
Loading