17 Jan 20245 minutes to read

The web accessibility makes web applications and its content more accessible to people with disabilities without any barriers. It especially it tracks the dynamic value changes and DOM changes.

The TimePicker component followed the accessibility guidelines and standards, including ADA, Section 508, WCAG 2.2 standards, and WCAG roles that are commonly used to evaluate accessibility.

The accessibility compliance for the TimePicker component is outlined below.

Accessibility Criteria Compatibility
WCAG 2.2 Support Yes
Section 508 Support Yes
Screen Reader Support Yes
Right-To-Left Support Yes
Color Contrast Yes
Mobile Device Support Yes
Keyboard Navigation Support Yes
Accessibility Checker Validation Yes
Axe-core Accessibility Validation Yes
Yes - All features of the component meet the requirement.
Intermediate - Some features of the component do not meet the requirement.
No - The component does not meet the requirement.

WAI-ARIA attributes

The TimePicker control has covered the WAI-ARIA specifications with the following list of WAI-ARIA attributes: aria-haspopup, aria-selected, aria-disabled, aria-activedescendant, aria-expanded, aria-owns, and aria-autocomplete.

Here in TimePicker, the combobox plays the role of input element, and the listbox plays the role of popup element.

  • Aria-haspopup: Provides the information about whether this element display a pop-up window or not.

  • Aria-selected: Indicates the current selected value of the TimePicker control.

  • Aria-disabled: Indicates disabled state of the TimePicker control.

  • Aria-expanded: Indicates the expanded state of the popup.

  • Aria-autocomplete: Indicates whether user input completion suggestions are provided or not.

  • Aria-owns: Attribute that creates a parent/child relationship between two DOM element in the accessibility layer.

  • Aria-activedescendent: Attribute that helps in managing the current active child of the TimePicker control.

  • Role: Attribute that gives assistive technology information for handling each element in a widget.

Keyboard Interaction

Keyboard accessibility is one of the most important aspects of web accessibility. Disabled people like blind and those who have motor disabilities or birth defects use keyboard shortcuts more than the mouse.

The TimePicker control has built-in keyboard accessibility support by following the WAI-ARIA practices.


It supports the following list of shortcut keys to interact with the TimePicker control.

Press To do this
Upper Arrow Navigate and select the previous item.
Down Arrow Navigate and select the next item.
Left Arrow Move the cursor towards arrow key pressed direction.
Right Arrow Move the cursor towards arrow key pressed direction.
Home Navigate and select the first item.
End Navigate and select the last item.
Enter Select the currently focused item and close the popup.
Alt + Upper Arrow Close the popup.
Alt + Down Arrow Open the popup.
Esc Close the popup.

In the below sample use the alt+t keys to focus the TimePicker control.

    document.onkeyup = function (e) {
	var timepicker = document.getElementById('timepicker').ej2_instances[0];
    if (e.altKey && e.keyCode === 84 /* t */) {
        // press alt+t to focus the control by calling public method.
@Html.EJS().TimePicker("timepicker").Placeholder("Select a time").Render()

Ensuring accessibility

The TimePicker component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.

The accessibility compliance of the TimePicker component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the TimePicker component with accessibility tools.

See also