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

A11y keyboard focus control in the Chips Component #3706

Closed
DaveBest99 opened this issue Mar 21, 2017 · 3 comments
Closed

A11y keyboard focus control in the Chips Component #3706

DaveBest99 opened this issue Mar 21, 2017 · 3 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

@DaveBest99
Copy link

Bug, feature request, or proposal:

Bug: Unable to select a Chip item.

What is the expected behavior?

Pressing Spacebar or Enter key should select a List Item, and Tab or Shift+Tab should move focus away from the Listbox element.

What is the current behavior?

Currently a keyboard user cannot move focus from the Listbox element.

What are the steps to reproduce?

See below.

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U

What is the use-case or motivation for changing an existing behavior?

Create a good keyboard user experience.

Which versions of Angular, Material, OS, browsers are affected?

Using screen reader JAWS17 with browsers Firefox, Internet Explorer 11, and Google Chrome, on Windows10.

Is there anything else we should know?

Screen reader user experience follows:

  1. Press Tab key to the Chip demo component in the Tab Panel.
    JAWS says "list box none selected 1 of 4", and the braille display shows "lbx none 1 of 4".
    Although keyboard navigation keys perform as expected (Arrow keys rotate focus through the list of items; Home and End keys move focus to top and bottom of list), the Tab and Shift+Tab keys do not move focus away from the Listbox. Also, pressing Escape or Alt+UpArrow key to close the Listbox, does not allow the Tab and shift+Tab to move the focus. This is consider to be a WCAG Keyboard Trap.
    The md-chip-list has role=listbox with tabindex=0, and the md-chip module has role=option with tabindex=-1, which should be okay, so not sure what may be the problem.

  2. Press Spacebar or Enter key on a Listbox Item.
    JAWS announces "selected" (I.E. "Primary selected") as the user presses the Arrow keys, but moving the focus away from the Listbox and then back, the first item always "none" gets focus and is announced as "selected".

According to the "Overview" explanation:
Users can move through the chips using the arrow keys and select/deselect them with the space. Chips also gain focus when clicked, ensuring keyboard navigation
starts at the appropriate chip.

Note, a chip may contain a photo, short title, and brief information, but the demo does not illustrate this type of Chip, and does not allow for Deletion.

@jelbourn jelbourn added 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 labels Mar 21, 2017
@DaveBest99
Copy link
Author

DaveBest99 commented May 7, 2017 via email

@tinayuangao tinayuangao self-assigned this May 15, 2017
@tinayuangao
Copy link
Contributor

This is duplicate of #4593.
#4605 fixes this.

@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

3 participants