Copilot Autofocus on Homepage breaks expected focus order #146630
-
Select Topic AreaQuestion GitHub Feature AreaCopilot BodyWhen you navigate to the GitHub home page, the GitHub Copilot input has This is a really poor practice as it breaks the expected focus order for the page, its annoying as a keyboard user to have to tab off of the input to scroll the page with arrow keys, and for screen reader users can be really confusing to have focus automatically shifted to an input with no interaction on the page. https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Hello @KonnorRogers - thank you for taking the time to submit your feedback! I shared your feedback with the GitHub accessibility team and they worked to get a fix in place. Can you re-test this on your end to confirm that the issue has been resolved? If you are still experiencing the issue you reported, please provide any additional details you think might be helpful for the team. Thanks so much! |
Beta Was this translation helpful? Give feedback.
Hello @KonnorRogers - thank you for taking the time to submit your feedback! I shared your feedback with the GitHub accessibility team and they worked to get a fix in place. Can you re-test this on your end to confirm that the issue has been resolved? If you are still experiencing the issue you reported, please provide any additional details you think might be helpful for the team. Thanks so much!