You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After using keyboard navigation to select an end date to complete a date range, focus unexpectedly moves to the start date of the range instead of remaining on the end date that was just selected. This breaks expected focus management behavior and disorients keyboard and screen reader users.
Navigate to "Date Range in a Single Datepicker" example using keyboard
Navigate to a start date using arrow keys and confirm with Enter or Space
Navigate to an end date using arrow keys and confirm with Enter or Space
Observe that focus moves to the start date instead of staying on the end date
Expected behavior
After confirming the end date, focus should remain on the end date.
Screenshots
Screen.Recording.2026-06-23.at.21.42.42.mov
Desktop (please complete the following information):
OS: macOS
Browser: Chrome
Additional context
Moving focus away from the last interacted element without user expectation
may violate WCAG 2.4.3 Focus Order
(Level A), which requires that focus order preserves meaning and operability,
as well as WCAG 3.2.2 On Input
(Level A), which requires that user input does not trigger unexpected changes of context,
including changes of focus.
Describe the bug
After using keyboard navigation to select an end date to complete a date range, focus unexpectedly moves to the start date of the range instead of remaining on the end date that was just selected. This breaks expected focus management behavior and disorients keyboard and screen reader users.
To Reproduce
Steps to reproduce the behavior:
EnterorSpaceEnterorSpaceExpected behavior
After confirming the end date, focus should remain on the end date.
Screenshots
Screen.Recording.2026-06-23.at.21.42.42.mov
Desktop (please complete the following information):
Additional context
Moving focus away from the last interacted element without user expectation
may violate WCAG 2.4.3 Focus Order
(Level A), which requires that focus order preserves meaning and operability,
as well as WCAG 3.2.2 On Input
(Level A), which requires that user input does not trigger unexpected changes of context,
including changes of focus.