Skip to content
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 #233

Closed
cyns opened this issue Jan 30, 2016 · 5 comments

Comments

@cyns
Copy link
Contributor

cyns commented Jan 30, 2016

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)

@cyns cyns added the AAM label Jan 30, 2016
@klown
Copy link
Contributor

klown commented Feb 1, 2016

@cyns

This example from the HTML5 spec has the datalist providing values for the range control, but having no UI of its own ...

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:
http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-input-range

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.

@cyns
Copy link
Contributor Author

cyns commented Feb 5, 2016

@klown
How about text change to the mapping to aria to something like
When datalist is the target of a for attribute on an input of type text, email, [rest of the list], maps to the aria role listbox. When datalist is the target of the for attribute on an input of type range, not mapped. [other cases if there are any]

@klown
Copy link
Contributor

klown commented Feb 8, 2016

@cyns
That sounds okay.

But, other than exploring a datalist for a input type="range", I personally don't know all the combinations of input and datalist, and the resulting GUI. Others who know more, need to vet this.

@cyns
Copy link
Contributor Author

cyns commented Feb 9, 2016

@stevefaulkner are there other use cases for datalist besides an edit/combobox and a slider?

@jasonkiss
Copy link
Contributor

This issue was moved to w3c/html-aam#26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants