influencing html markup in issues lists

[RichCaloggero]

Select Topic Area

Product Feedback

Body

As a screen reader user, I've often wanted a way to efficiently browse long lists of github issues. Is there a way of influencing the HTML markup generated for a github issues list?

It would be great if there were a way for me to influence the HTML generated by github for issues in my repos. For instance, I could format the issues list as an html data table with columns like title, author, labels, etc. I could wrap the title in a heading tag for more efficient navigation via screen reader. The possibilities are endless...
FOr instance, would be nice if the issues list were marked up as an HTML table so screen reader users could more easily scan the

The current format is incredibly tedious to navigate, especially for repos with large numbers of issues.

[ghostinhershell]

Hi @RichCaloggero, thanks so much for reaching out in our community. I'll go ahead and log this feedback with the Accessibility team on your behalf.

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

[zersiax]

hello @RichCaloggero , that is a really interesting concept you suggest there! :)
Now on the GitHub side, this is pretty difficult to make happen: what you are suggesting is something users usually do through a mechanism called user scripts, which is a way to use JavaScript to modify the way a page looks or functions for a specific user. I would love to hear any other modifications you'd make if you had this ability though. Would you mind following up on this issue?

Thank you so much!

[RichCaloggero]

I have no suggestions for other pages at the moment.

However, consider instead of full user script ( js ) level injection, perhaps a way of allowing user templates. Sticking with the issues list, you could have tags for issueTitle, issueCommentCount, etc, and a way of attaching templates to each repo. You could supply a default template, which the repo owner could then modify as they see fit.

Alternatively, or in addition, these templates could be attached to a user's github account. This might be more useful for screen reader accessibility since the templates would then reflect a user's preferences rather than a repo owner's preferences.

[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! 💬