-
Notifications
You must be signed in to change notification settings - Fork 530
Required ARIA children role not present: listbox textbox #42
Comments
Hi @pauljadam! Thanks for letting us know. I'm sure there are loads of ARIA resources/tools we should be using. Do you have any tips for us so that we don't regress wrt. a11y in the future? |
The ARIA 1.1 Authoring Practices give you instructions for how to provide ARIA roles, parent child relationships, and keyboard behavior. http://www.w3.org/TR/wai-aria-practices-1.1/#combobox Also that issue was discovered with aXe the automated accessibility engine. WAI-ARIA Roles, States, and Properties: As a combination of text field, which may be editable, a displayable list of items, and a drop button to toggle the display of that list; all wrapped in the form of a single widget with role of combobox. For the first combobox design pattern: The container element that wraps the combobox has a role of combobox. The first element for the combobox has a role of combobox and behaves like an input text field and is responsible for managing the keyboard focus between the combobox and the list as well as displaying the list. The text field is in the tab order. If you create a text field without using a standard HTML text field form control then ensure that it is in the tab order. The next element has a listbox role and represents the drop down list. It manages keyboard navigation among list items and navigating back to the text field if necessary. Each item in the listbox is an option. Options are not in the tab order. Provide a label for the combobox by referencing the text field in the combobox. You can use an aria-label to associate this label with the combobox or you may use the HTML element and its for attribute to reference the text field. For each combobox pattern the button need not be in the tab order if there is an appropriate keystroke associated with the input element such that when focus is on the input, the keystroke triggers display of the associated drop down list. In this case, a Tab to focus the button is unnecessary. This is the same behavior as the select element. |
|
Hi @CMTegner ! I'm currently working on a project that uses this package and needs to be WCAG compliant, so I'm planning to make a PR soon that resolves the issues in this ticket and uses the recommendations outlined here: |
…apshot, update README, update example apps
Checks all elements that contain a WAI-ARIA role to ensure that all required children roles are present
(More Info)
Target: #container > div > div > input
HTML:
Summary:
Fix any of the following:
The text was updated successfully, but these errors were encountered: