Skip to main content
Visual Arts & DesignUX Design Patterns29 lines

Accessible Calendar Date Picker

Design and test a date input and calendar dialog with keyboard navigation, local date validation, availability rules and predictable focus restoration.

Quick Summary9 lines
Choose the simplest interaction that fits the task. A native date input or editable field can be enough for a simple date. Use a custom calendar grid when users need to see availability, compare nearby dates or select a range. Keep direct entry or another accessible equivalent where it helps; state the expected format and preserve a typed value that fails validation so the user can correct it.

## Key Points

- [W3C Date Picker Dialog Example](https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/datepicker-dialog/)
- [W3C dialog pattern](https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/)
- [WCAG 2.2](https://www.w3.org/TR/WCAG22/?KBOpenTab=undefined)
skilldb get ux-design-patterns-skills/accessible-date-pickerFull skill: 29 lines
Paste into your CLAUDE.md or agent config

Accessible Calendar Date Picker

Choose the simplest interaction that fits the task. A native date input or editable field can be enough for a simple date. Use a custom calendar grid when users need to see availability, compare nearby dates or select a range. Keep direct entry or another accessible equivalent where it helps; state the expected format and preserve a typed value that fails validation so the user can correct it.

Keep date and navigation states separate

Store a civil date in a date-only format when the business task is independent of time of day. Do not route a booking date through UTC midnight if that can shift the displayed day. Define locale, week start, business timezone, minimum and maximum dates and unavailable date rules. Show why a date cannot be picked where users need to know. Revalidate the date at submission because availability can change while the calendar is open.

Separate the selected date, visible month and focused day. On open, place focus on the valid selected date or a meaningful fallback. Give day cells useful full-date names, present month/year changes appropriately, and keep one keyboard entry point to the calendar grid using the established roving focus pattern. Implement directional movement and calendar navigation coherently. A disabled or unavailable day must not be committed even if the navigation design lets focus reach it. Preserve a clear indication of today, selected and unavailable states without relying on color alone.

Test the dialog and the actual booking

Use the WAI-ARIA dialog and calendar example as a reference and verify the implementation on your target browser and assistive technology. Escape closes without changing the previous selection. Confirming a valid day updates the input and returns focus to the opener or a documented successor. Dialog focus must not escape when it is modal. Support pointer and keyboard use, and ensure the field works when the calendar control is unavailable.

Test leap day, month and year boundaries, differing locale order, the last allowed date and a date that becomes unavailable after opening. Reproduce a saved booking from its stored date-only value across two timezones. Record the exact roles, labels, focus steps and validation result. A visual click path does not verify keyboard navigation or screen-reader announcements.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add ux-design-patterns-skills

Get CLI access →