Skip to content

HTML-AAM: determine right mappings for popup ui for input type=color #48

Closed

Description

@jasonkiss

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

Activity

  1. jasonkiss commented on Oct 12, 2016

    @jasonkiss
    ContributorAuthor

    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?

  2. assigned and unassigned on Oct 19, 2016
  3. added this to the milestone on Jun 17, 2017
  4. jasonkiss commented on Jan 8, 2018

    @jasonkiss
    ContributorAuthor

    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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions