HTML-AAM: determine right mappings for popup ui for input type=color · Issue #48 · w3c/html-aam · GitHub
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: determine right mappings for popup ui for input type=color #48

Closed
jasonkiss opened this issue Oct 12, 2016 · 2 comments
Closed
Assignees
Milestone

Comments

@jasonkiss
Copy link
Contributor

From @cyns on May 6, 2016 20:20

The color picker dialog that pops up from input type=color is not reliably mapped to accessibility APIs in browsers and does not reliably work with screen readers. We need to determine the right way to map the relationship between the launcher (button or edit) and popup UI, so that screen readers can find it.

Copied from original issue: w3c/aria#363

@jasonkiss
Copy link
Contributor Author

From @cyns on May 6, 2016 22:7

Here's what we're doing in UIA:
Control Type: Button
Localized Control Type: color picker
ControllerFor: points to the popup
The popup and its children must be present in the UIA tree, and mapped as button, slider, etc. as appropriate for the type of control.

Would it work to do something similar with ControllerFor/ControlledBy in IA2 and ATK?

@jasonkiss
Copy link
Contributor Author

I've updated the mappings accordingly with fd1e1c2, and added a comment regarding the mapping of associated UI controls when implemented as a color picker. Feel free to reopen if any concerns.

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

4 participants