All links to open a new issue from template are called "Get started", which creates links with the same name that go to different destinations

[daniel-montalvo]

Select Topic Area

Bug

Body

To reproduce:

• Select a repo with some of issue templates
• Move to "issues" > "New issue".

Expected result: The links to open new issues have each the template name, or at least a unique accessible name that helps understand their purpose.

Current behavior: All relevant links to start a new issue are called "Get started", which makes it impossible to quickly distinguish them from one another without the surrounding text context.

[queenofcorgis]

Thank you for this feedback. It has been logged internally. Our team will evaluate the feedback, but we cannot guarantee a resolution or a timeline.

Any additional members who have the same request, please comment to share use cases or upvote it.

We appreciate you contributing and continuing to support other users in the GitHub Community Discussions.

[ericwbailey]

Hi @daniel-montalvo. I'm a member of the GitHub accessibility team, and am working on this issue.

First off, thank you for reporting it. It's definitely something that could be improved. I've updated the template to append the issue template's title to the link's accessible name as visually hidden text.

Previously, as you noted it was:

Get started

Now it is:

Get started: Bug report

As you noted, this will help to disambiguate link content.

The changes should be live now—you may also need to refresh the tab for the changes to take effect.

[daniel-montalvo]

Thanks @ericwbailey

That's working better now.

Ideally we would flip these two pieces of information around: the unique information (template title) first, and then the generic "get started" portion. This change will improve efficiency for screen reader users, as they'll hear the most relevant piece of info first.

[ericwbailey]

I hear you, and would generally agree. However, for this specific instance I am trying to balance the UX of screen reader support with the UX of voice control software. The "get started" prefix is short enough that I feel it is tolerable to traverse with a screen reader, and also helps to ensure people who use voice control software don't have to resort to less straightforward, more laborious commands. It's a tricky balance 😅

[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. ⭐