-
Notifications
You must be signed in to change notification settings - Fork 125
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
[Role Parity] What do we do about input (type=color)? #930
Comments
role="color" or role="colorinput"? We already have "time" role for Both Chrome and FF on Win7 render So I think "color/colorinput" should support aria-haspopup (with all of its tokens). I don't know if any platforms still implement this as a textbox that only takes hex color values, but presumably someone might want to do that. So they might use a combobox with aria-autocomplete. This would likely be similar to using the list="datalist-id" attribute. So I think "color/colorinput" should support aria-autocomplete (with all of its tokens). I don't know how useful the HTML autocomplete attribute is with input type="color", but it is supported. Perhaps one could create colors using autocomplete="postal-code"... 😄 In case it's helpful, here's a basic HTML element test page for trying out the various inputs (and other elements). |
Regarding naming:
Since we have always had "checkbox", "radio", and "button", I think it makes more sense to go with role="color". The time element is very different from input type="time", so we do need to resolve that conflict (in #936), but there's no conflict for "color". (perhaps input type="time" can be role="timebox" for consistency with role="textbox" for input type="text") |
See also the discussion starting at comment 8 in Firefox bug 559767 about platform mapping of color input (button, dialog). |
As detailed at https://github.com/w3c/aria/wiki/Plans-regarding-role-parity#no-consensus-yet-will-do-for-1-3 moving to 1.3 |
Honestly - I don't see any way this is going to happen until HTML color inputs are more standard. Propose closing this as a wontfix. |
No description provided.
The text was updated successfully, but these errors were encountered: