Issue Bug Closed

#108934Date picker is only partially operable via keyboard

Jennifer Geiß 02/11/26, 06:25 updated 02/11/26, 07:44

Description

Description

The date picker component is not fully operable via keyboard, which makes it hardly usable for people who rely solely on keyboard navigation. Users currently cannot select a date using the keyboard (e.g. via Tab and arrow keys), nor can they enter a date directly in the input field.

Reproduction steps

  1. Navigate to the page containing the date picker.
  2. Use the keyboard only (Tab / Shift+Tab) to focus the date input field.
  3. Attempt to open and operate the date picker using the keyboard.
  4. Try to select a specific date using only the keyboard.
  5. Try to type a date directly into the input field.
  6. Observe that there is no clear instruction or hint about the required date format and that keyboard-only date selection is not possible.

Target group

  • Keyboard-only users
  • Users with motor impairments
  • All users who prefer keyboard input for efficiency

Severity

High
The issue significantly impacts the ability of keyboard-only users to select or enter a date, resulting in a major accessibility barrier for completing related tasks.

Frequency

Always – The behavior occurs every time the date picker is used.

Definition of Done

  • Users can fully operate the date picker using only the keyboard (focus management, opening/closing, navigating between days/months, and selecting a date).
  • Users can alternatively enter a date directly into the input field without using the date picker popup.
  • The input field displays a clear hint/placeholder or label text that indicates the required date format (e.g. DD.MM.YYYY or YYYY-MM-DD).
  • The solution is tested with:
  • Keyboard-only navigation (no mouse).
  • No WCAG 2.2 SC related to keyboard access or input instructions is violated.
  • All relevant automated and manual accessibility checks for this component pass.

Suggestion

  • Enable complete keyboard control for the date picker:
  • Focusable trigger element for opening/closing the calendar.
  • Support for navigating days, weeks, and months via arrow keys and other common shortcuts.
  • Clear visual focus indication on the currently focused element.
  • Allow direct manual date entry in the input field as an alternative to using the picker.
  • Provide a visible placeholder or helper text (and programmatic description for assistive technologies) that explains the expected date format.

Recommended solution

Keyboard operability
  • Ensure the date picker trigger (icon/button) is reachable via Tab and can be activated via Enter/Space.
  • Once the calendar is open, trap focus within the calendar until it is closed.
  • Implement common keyboard navigation patterns, e.g.:
    Arrow keys: move focus between days.
    PageUp/PageDown: move between months.
    Home/End: jump to start/end of week or month (depending on chosen pattern).
    Escape: close the calendar and return focus to the trigger/input.
    Ensure a clear visible focus state on all interactive elements in the date picker.
Direct text input
  • Allow users to type the date directly into the input field without using the popup.
  • Validate the typed date and provide accessible error messages if the format or value is invalid.
  • Ensure the input is announced correctly to screen readers (e.g. using appropriate type, aria-label, or aria-describedby attributes).
Date format hint
  • Add a placeholder or helper text such as YYYY-MM-DD
  • Associate helper text programmatically with the input (e.g. via aria-describedby) so screen readers can announce the expected format.
  • If localization is relevant, ensure the date format hint corresponds to the user’s locale or is clearly documented.
Accessibility review
  • Align implementation with WAI-ARIA Authoring Practices for date picker/calendar widgets.
  • Perform manual testing with keyboard only and with a screen reader.

References / WCAG 2.2 Reference

  • WCAG 2.2 – 2.1.1 Keyboard (Level A)
  • WCAG 2.2 – 2.1.2 No Keyboard Trap (Level A)
  • WCAG 2.2 – 2.4.3 Focus Order (Level A)
  • WCAG 2.2 – 3.2.2 On Input (Level A) – with regard to unexpected context changes on interaction
  • WCAG 2.2 – 3.3.2 Labels or Instructions (Level A) – for clear indication of required date format

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 4

  1. Garvin Hicking commented and changed status New Accepted <span data-processor="relativetime" data-value="2026-02-11T07:28:12+00:00" > 02/11/26, 07:28 </span>

    Reproduced in v14.2-dev main