-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML-AAM: <datalist> used with non-textbox inputs shouldn't map to aria listbox role #26
Comments
From @klown on February 1, 2016 15:34
FWIW: If I load that markup into FF, Safari, or Chrome, it's a slider. Also, FF and Safari expose it as a slider in the a11y tree. The html-aam maps <input type="range" ...> to the ARIA slider role: The datalist/option is used by Chrome to create tick marks for the 0, -30, and 30 values, which are three of the option/values called out in the datalist. However, I don't see anything corresponding to these ticks in AAPIs,. I don't think any AAPI provides specific support for them. |
From @cyns on February 5, 2016 23:24 @klown |
From @cyns on February 9, 2016 22:49 @stevefaulkner are there other use cases for datalist besides an edit/combobox and a slider? |
I added 'no mapped if not linked with a proper input control' into comments section of datalist element mapping e9b1bfe |
From @cyns on January 30, 2016 1:45
This example from the HTML5 spec has the datalist providing values for the range control, but having no UI of its own. In this case, it would not be mapped to the aria listbox role. I think it would not be mapped at all, only providing value data to the range which is then mapped as a slider. Are there other examples of where datalist is not a listbox?
<input type="range" min="-100" max="100" value="0" step="10" name="power" list="powers">
<datalist id="powers">
<option value="0">
<option value="-30">
<option value="30">
<option value="++50">
</datalist>
https://www.w3.org/TR/html51/semantics.html#range-state-(type=range)
Copied from original issue: w3c/aria#233
The text was updated successfully, but these errors were encountered: