Accessibility best practices#3641
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new guide article describing accessibility best practices for open source projects, with practical recommendations spanning documentation, UI design, tooling, contribution workflows, and ongoing testing.
Changes:
- Introduces a new long-form accessibility best practices article under
_articles/. - Covers guidance on accessibility statements, accessible docs, accessible UI patterns, accessible tooling (CLI/logs), contribution workflows, and testing approaches.
Show a summary per file
| File | Description |
|---|---|
_articles/accessibility-best-practices-for-your-project.md |
New accessibility best-practices guide content and metadata for publication |
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: 6
ahpook
left a comment
ahpook
left a comment
There was a problem hiding this comment.
Left a couple of comments on the copilot suggestions and made a couple more but overall this looks great, thanks for the contribution!
|
Also checkout the test failures - most of these should be automatically fixable, it looks like the main culprits are "smart quotes" instead of straight ASCII, bullet points being |
ahpook
left a comment
ahpook
left a comment
There was a problem hiding this comment.
This looks great, thanks!
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.
The accessibility team would love to create a new guide for accessibility best practices. We believe an accessibility guide would fill an information gap and become a valuable resource for open source maintainers.