Lack of Accessibility Features in GitHub's User Interface. #113735
Replies: 2 comments
-
Hi @jimmy34323, Thanks so much for reaching out in the community! I was reviewing your feedback and this part caught my attention:
Do you have any specific feedback on any of the areas that you mentioned above that I can pass along to the Accessibility team? Feedback is always more actionable when specific areas of the product are highlighted as needing improvement and/or when reproduction steps are provided so that we can observe the issue on our end. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Show & Tell
Body
The GitHub community has been discussing the lack of accessibility features in GitHub's user interface, which poses challenges for users with disabilities. While GitHub has made strides in improving accessibility, there are still areas where enhancements can be made. Users have highlighted issues such as keyboard navigation, screen reader compatibility, and color contrast, which can make it difficult for users with disabilities to fully engage with the platform. By prioritizing accessibility improvements, GitHub can ensure that its platform is inclusive and accessible to all users.
Beta Was this translation helpful? Give feedback.
All reactions