Date pickers enable a customer to select a single date or a date range, such as a payment date or a statement period requiring start and end dates. Date pickers are used to display past, present, or future dates. Use date pickers when you are asking the user for a date, a date range, or for scheduling tasks.
On this page
| Variations | Description |
|---|---|
| Date Picker | Allows users to select a single date using either the text input or calendar popover. Best for one off selections like setting a payment date, birthdate or filtering by a specific transaction date. |
| Date Range Picker | Let’s users choose a start and end date in a single interaction, using an input field paired with the Calendar Popover. It’s ideal for tasks like filtering statements, reviewing spending overtime, or setting a travel period. |
Removing the label from the Date Picker violates WCAG 1.3.1 - Info and Relationships and WCAG 4.1.2 - Name, Role, Value, resulting in inaccessible experiences for assistive tech users. Never rely on visual design or color alone to convey purpose or progress.
If a label is removed, screen readers announce a progress bar but with no context. They will not know what is progressing: Is it a form, a task?
Align labels according to the reading direction (left for LTR, right for RTL) to support readability and screen reader consistency
Center texts in fields, it hurts readability and breaks visual scanning patterns
Make fields wide enough for full date input and calendar icon
Truncate the date or crowd the calendar icon - avoid input fields that are too narrow to display the full value clearly
Align labels according to the reading direction (left for LTR, right for RTL) to support readability and screen reader consistency
Center texts in fields, it hurts readability and breaks visual scanning patterns
All non-text content (for example the calendar icon) must have a text alternative. Please utilize the Icon Button Tertiary Component Properties to provide Alt Text.
Removing or not providing text alternatives violates WCAG 1.1.1 - Non-text Content, resulting in inaccessible experiences for screen reader users.
If no accessible name is provided, screen readers may ignore the icon entirely as they will not know it exists, the control may be announced generically with no indication of purpose, users may be unable to interact with the date picker or understand how to open it. Provide descriptive text to convey intent.
Connect with the DLS Team on Slack or by email.
Check out additional resources.