Issue with Keyboard Navigation in Code Blocks

[Shylejasatheesan]

Select Topic Area

Bug

GitHub Feature Area

Actions

Body

I've encountered an issue with keyboard navigation within code blocks on GitHub. When using the Tab key to navigate through code blocks, the focus sometimes jumps to unexpected elements, such as the next code block or the page header.

Steps to Reproduce:

Navigate to a repository with multiple code blocks.
Use the Tab key to move focus into a code block.
Continue pressing the Tab key to navigate within the code block.
Expected Behavior:
The focus should move sequentially through the code elements, such as lines of code, keywords, and comments.

Actual Behavior:
The focus jumps to unexpected elements, making it difficult to navigate the code using the keyboard.

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

[cehfisher]

Hello @Shylejasatheesan - thank you for providing this feedback. We will file this with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates. Thanks again!