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

md-input: keyboard selection for inputs with labels/hints with icons has unexpected behavior #604

Closed
iveysaur opened this issue Jun 1, 2016 · 2 comments
Assignees
Labels
Accessibility This issue is related to accessibility (a11y) P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@iveysaur
Copy link
Contributor

iveysaur commented Jun 1, 2016

Using keyboard selection on an input that has icons in its hints/labels causes the keyboard to select parts split by the icon.

Example:

"First half icon second half."

Selects:

  • "First half"
  • icon
  • "second half."

The icon splits the hint/label into separate items where it should all be one item selected.

Steps:

  1. Keyboard select to the input label or hint with icons -- it will select the first part of the hint/label split by the icon
  2. Move to the next item -- it will select the icon
  3. Move to the next item -- it will select the second half of the hint/label split by the icon

Found using the screenreader on OSX El Capitan in Chrome

@jelbourn jelbourn added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent Accessibility This issue is related to accessibility (a11y) labels Jun 1, 2016
@jelbourn jelbourn added this to the alpha.7 milestone Jun 1, 2016
@jelbourn jelbourn modified the milestone: alpha.7 Nov 1, 2016
@mmalerba mmalerba self-assigned this Dec 14, 2016
@mmalerba
Copy link
Contributor

mmalerba commented May 5, 2017

This seems to be fixed now, for an input with placeholder: "I [favorite icon] bold placeholder" voiceover reads "I favorite bold placeholder"

@mmalerba mmalerba closed this as completed May 5, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

4 participants