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.

Sign up for GitHub

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

Jump to bottom

MatStepper tabpanel element should not have tabindex="0" #19574

Closed
Wloclawek opened this issue Jun 9, 2020 · 3 comments
Closed

MatStepper tabpanel element should not have tabindex="0" #19574

Wloclawek opened this issue Jun 9, 2020 · 3 comments
Labels
Accessibility This issue is related to accessibility (a11y) area: material/stepper P2 The issue is important to a large percentage of users, with a workaround

Comments

@Wloclawek
Copy link

Wloclawek commented Jun 9, 2020 •
edited

Reproduction

Steps to reproduce:

  1. Open: https://material.angular.io/components/stepper/api
  2. Use tab and go to first input.

Expected Behavior

Focus should always be visible (users using only the keyboard).

A11Y / WCAG / accessibility

Actual Behavior

Between the first step (tab) and the first field, the focus disappears.

Environment

  • Angular: 8.
  • Angular Material: 9.2.4
  • Browser(s): Firefox 77, Chrome 83
  • Operating System: Windows 10.
@Wloclawek Wloclawek added the needs triage This issue needs to be triaged by the team label Jun 9, 2020
@jelbourn jelbourn changed the title MatStepper: Lose focus MatStepper tabpanel element should not have tabindex="0" Jun 11, 2020
@jelbourn jelbourn added Accessibility This issue is related to accessibility (a11y) P2 The issue is important to a large percentage of users, with a workaround and removed needs triage This issue needs to be triaged by the team labels Jun 11, 2020
@jelbourn
Copy link
Member

Looked at this, the role="tabpanel" here has tabindex="0" which shouldn't be the case.

@crisbeto
Copy link
Member

We've got a PR for this already #16809. Also closing as a duplicate of #16692.

@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 Jul 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Accessibility This issue is related to accessibility (a11y) area: material/stepper P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jelbourn @crisbeto @Wloclawek @andrewseguin