Link to Accessibility category for community discussions instead of ACR#13481
Merged
Conversation
The Accessibility Conformance Report (ACR) is only valuable in that it outlines how GitHub CLI measures up against the accessibility standards. However, it's confusing to link to that when the CTA in `gh a11y` is to "join the conversation" and share feedback. In this case, it's more appropriate to route users directly to the community discussions instead.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the gh accessibility (hidden a11y) command’s “Join the conversation” call-to-action to direct users to the GitHub Community Accessibility Discussions category rather than the CLI Accessibility Conformance Report (ACR).
Changes:
- Introduces distinct constants for the ACR URL and the Accessibility Discussions category URL.
- Keeps
--webopening the ACR page while updating the long help text CTA link to point at the Discussions category.
Show a summary per file
| File | Description |
|---|---|
| pkg/cmd/accessibility/accessibility.go | Splits ACR vs community feedback URLs and updates the help text CTA link to route users to the Accessibility Discussions category. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
Comment on lines
37
to
+42
| RunE: func(cmd *cobra.Command, args []string) error { | ||
| if opts.Web { | ||
| if opts.IO.IsStdoutTTY() { | ||
| fmt.Fprintf(opts.IO.ErrOut, "Opening %s in your browser.\n", text.DisplayURL(webURL)) | ||
| fmt.Fprintf(opts.IO.ErrOut, "Opening %s in your browser.\n", text.DisplayURL(acrURL)) | ||
| } | ||
| return opts.Browser.Browse(webURL) | ||
| return opts.Browser.Browse(acrURL) |
Member
Author
There was a problem hiding this comment.
This is fine. I intentionally left this in because the ACR page does provide more information about accessibility in gh, which aligns with how other commands with -w flags open up to their browser equivalent views. It would be misleading to link to the discussions URL instead.
BagToad
approved these changes
May 22, 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.
The Accessibility Conformance Report (ACR) is only valuable in that it
outlines how GitHub CLI measures up against the accessibility standards.
However, it's confusing to link to that when the CTA in
gh a11yis to"join the conversation" and share feedback. In this case, it's more
appropriate to route users directly to the community discussions instead.