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

[Role Parity] What do we do about input (type=color)? #930

Closed
joanmarie opened this issue Apr 9, 2019 · 5 comments
Closed

[Role Parity] What do we do about input (type=color)? #930

joanmarie opened this issue Apr 9, 2019 · 5 comments
Labels
Milestone

Comments

@joanmarie
Copy link
Contributor

No description provided.

@joanmarie joanmarie added this to the ARIA 1.2 milestone Apr 9, 2019
@carmacleod
Copy link
Contributor

role="color" or role="colorinput"?

We already have "time" role for <time> element,
so do we go with "timeinput" role for <input type="time">?
If so, then "colorinput" would be consistent with "timeinput", but more verbose than "color"...

Both Chrome and FF on Win7 render <input type="color"> as a "color well button that pops up a color picker dialog".
So if someone was implementing this today, they might use a read-only combobox with aria-haspopup="dialog".

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).

@carmacleod
Copy link
Contributor

Regarding naming:

role="color" or role="colorinput"?
We already have "time" role for <time> element,
so do we go with "timeinput" role for <input type="time">?
If so, then "colorinput" would be consistent with "timeinput", but more verbose than "color"...

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")
😄

@carmacleod carmacleod self-assigned this Apr 11, 2019
@carmacleod
Copy link
Contributor

See also the discussion starting at comment 8 in Firefox bug 559767 about platform mapping of color input (button, dialog).

@jnurthen jnurthen modified the milestones: ARIA 1.2, ARIA 1.3 Sep 26, 2019
@jnurthen
Copy link
Member

@jnurthen jnurthen modified the milestones: ARIA 1.3, ARIA 1.4 Mar 4, 2021
@jnurthen
Copy link
Member

jnurthen commented Sep 9, 2023

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.

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

No branches or pull requests

3 participants