The Date Component that opens when using Projects Does Not Select The Date When you Hit Enter or Space

[frastlin]

Select Topic Area

Bug

GitHub Feature Area

Projects

Body

The date component on the projects fields does not allow date selection with the keyboard. When you open the date field it lands your focus on previous month (which is also a small bug, it should land you in the date selection field because keyboard users don't need the next month and previous month buttons), but when you hit enter or space on a date, the component closes and you're back on the cell in the table that now has an empty date. If you click the component with a mouse, the date is correctly selected.

Steps to reproduce:

1. Open a project.
2. Activate "settings"
3. Add a new field.
4. Call it what you like and select "date" from the type, and hit save.
5. Return to the project homepage
6. Go to the new column in the table on a row that's associated with an issue.
7. Hit enter to select a date.
8. Tab twice into the date area and using your arrow keys, find any date in the future.
9. Press either enter or space on this date.
10. Observe no date was selected.

Expected behavior is that a date is selected.

[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]

Thanks for sharing your question in the GitHub Community, @frastlin! We're glad to have you here. To help you get the best response, it's important to post in the most relevant category. The Accessibility category is a better fit for this topic, so I've moved your post there. Additionally, we'll share this with our internal accessibility team for further review. Thanks!