TINYDOC-3607: Link the Trust Center from the security guide and clarify the Accessibility Checker scope. - #4346
Merged
Merged
Conversation
…fy the Accessibility Checker scope.
kemister85
requested review from
a team,
TheSpyder,
metricjs,
soritaheng and
tiny-ben-tran
and removed request for
a team
September 7, 2026 06:06
kemister85
marked this pull request as ready for review
September 7, 2026 06:06
metricjs
approved these changes
Sep 7, 2026
metricjs
left a comment
Contributor
There was a problem hiding this comment.
LGTM for a quick win. Nitpick: might be worth calling it out more obviously? E.g. at top of page. Can be something for another day though if we like.
tiny-ben-tran
approved these changes
Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket: TINYDOC-3607
Site: Staging branch
Changes:
A reader evaluating {productname} had no route from the documentation to any compliance evidence, and the only conformance language in the documentation described the wrong subject.
modules/ROOT/pages/security.adocmodules/ROOT/pages/a11ychecker.adoc:description:metadata, which read "Checks the contents of the editor for WCAG & Section 508 accessibility problems." This is the text rendered in search results and on index cards, and an evaluator skimming it can read it as a conformance claim for the editor. It is not one — the plugin evaluates content authored in the editor.Pre-checks:
Review: