Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
This repository was archived by the owner on Sep 5, 2024. It is now read-only.

FAB Speed Dial: keyboard navigation with tab key gives unexpected results #12043

Closed

Description

@sharonlevyex

Bug Report

When navigating through md-fab-actions with both tab and keyboard the focus is not in order.

Example

If I use tab to navigate and I reach the third action:
image
and then I use keyborad (left) to navigate back to the previous action, the focus goes to the first action:
image

Actual behavior

The focus starts from the first element when using keyboard, even after navigating with tab.

Expected behavior

For keyboard to continue navigation from current button focused.

Demo and steps to reproduce the issue

It reproduces in the Material demo.

Demo URL (required)*: https://material.angularjs.org/1.2.1/demo/fabSpeedDial

Detailed Reproduction Steps

  1. Use tab to navigate through the actions.
  2. Continue to navigate with keyboard.

Activity

  1. self-assigned this
    on Nov 9, 2020
  2. added
    a11yThis issue is related to accessibility
    P3: importantImportant issues that really should be fixed when possible.
    and removed
    needs triageIssues that need initial triage
    on Nov 9, 2020
  3. added this to the 1.2.2 milestone on Nov 9, 2020
  4. Splaktar commented on Nov 9, 2020

    @Splaktar
    Contributor

    It looks like tab navigation is broken for this component. It just seems to go to the last option and hitting tab again closes the speed dial instead of going to the next option. Thank you for this report.

  5. changed the title [-]FAB Speed Dial: issue when using keyboard and tab together to navigate[/-] [+]FAB Speed Dial: keyboard navigation with tab key gives unexpected results[/+] on Nov 9, 2020
  6. added 2 commits that reference this issue on Dec 17, 2020
    fda4a81
    0a9371b
  7. added a commit that references this issue on Dec 17, 2020
    a6175d2
  8. added a commit that references this issue on Dec 17, 2020
    41c71ed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P3: importantImportant issues that really should be fixed when possible.a11yThis issue is related to accessibilityhas: Pull RequestA PR has been created to address this issueresolution: fixedtype: bug

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions