Improve accessibility of labels in issues and pull request

[nvdaes]

Select Topic Area

Question

GitHub Feature Area

Actions

Body

Hello:
I'm a totally blind user of NVDA screen reader. I'd like to suggest the following improvements so that labels in issues and pull requests are more accessible:

• Labels should be located in an ARIA region, probably with aria-live set to polite, so that changes are notified to screen readers, and navigate to lbels can be easier.
• When issues or pull requests have new labels,added or removed, it should be possible to receive email notifications, since they convey important information about the meaning of issues and pull requests.
  I created an issue in the NVDA project, requesting a way to be notified about labels, which may be done via GitHub Actions, adding a comment in the corresponding issue. But it would be helpful if this feature was added on GitHub itself.

For more details, please see:

nvaccess/nvda#16979

Thanks

[XLTechie]

The ability to receive email notifications for label changes would be most helpful!
As would having them accessible by heading navigation, as label changes can be as important as comments.

Many times I have submitted an issue for which I have a fix. Then I wait months to hear whether I can work on it, only to check the issue again and find that it was labeled with a work priority a few days after I submitted it, but with no further comment. If I had some notification of that label, I could have worked on it long ago.

That is not just an accessibility problem, it is a general one, but as @nvdaes points out, label changes are not easy to find with screen readers. Yes, the current set of labels is always near the bottom, but there is no way to quickly navigate to it. And finding out that one has been added by notification (passive) instead of manually checking (active), is not possible for anyone.

[queenofcorgis]

@XLTechie
Please note, contacting any member of GitHub Staff via unsolicited mentions or pings is strongly discouraged and may be considered a violation of our prohibition against harassment. Please review our Code of Conduct for more information.

Let's work together to keep GitHub Community a place where people feel safe to participate by being respectful of them and their time.

[XLTechie]

My apologies!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[queenofcorgis]

@Hepheoluwah

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬