FEEDBACK WANTED: Accessibility Documentation - Screen Reader guides #174661
Replies: 2 comments
-
how to revive from clone repetitions of phone set-up backend hijacks |
Beta Was this translation helpful? Give feedback.
-
Thank you for sharing this important announcement about GitHub's Accessibility Documentation! This is fantastic news for making development more inclusive. Here's a thoughtful response you could use to engage with this initiative: 🌟 Supportive Response Template 🌟 This is wonderful news! Thank you to the GitHub Accessibility team for creating these comprehensive resources. Making our platform more accessible benefits everyone in the developer community. 🚀 Immediate Actions I'll Take: Review the GitHub Copilot for VS Code guide with my NVDA setup Test the Pull Requests workflow with the new documentation Share this resource with my team and developer communities 💡 Suggestions for Future Guides: GitHub Actions with screen readers (complex workflows can be challenging to navigate) GitHub Projects accessibility for project management Mobile app accessibility for iOS VoiceOver and Android TalkBack Keyboard-only navigation guides for power users ❓ Questions for the Team: Are there plans to create similar guides for other screen readers like JAWS or VoiceOver? How can community contributors help expand these resources? Will there be video tutorials demonstrating these workflows? 📋 Feedback Commitment: Navigation clarity Step-by-step instruction effectiveness Areas where additional detail would help This initiative demonstrates GitHub's commitment to building tools that everyone can use effectively. Thank you for leading the charge in accessible development environments! This response shows enthusiasm, provides constructive input, and commits to active participation—exactly what the Accessibility team is hoping for! Would you like me to adjust the tone or focus on any specific aspect of the documentation? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Our accessibility documentation is created to support users with disabilities in navigating and using GitHub products with confidence. Visit our accessibility documentation page to explore comprehensive guides covering a range of GitHub features.
📚 Available Screen Reader Guides
These following guides are now available and provide step-by-step instructions for NVDA screen reader users:
Our plan is to expand to cover more areas of GitHub products and assistive technologies.
🚀 Call to Action
We need your help to make these guides even better!
What other guides would you like to see from the Accessibility team? Let us know what should come next, your thoughts on the existing documentation, and any questions you may have in the comments!
🤝 Why This Matters
These guides represent GitHub's commitment to making their platform accessible to all developers. By testing them and providing feedback, you're directly contributing to a more inclusive development environment for the entire community.
Beta Was this translation helpful? Give feedback.
All reactions