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

fix(material/tabs): switch pagination to not use native buttons #29605

Merged
merged 1 commit into from
Aug 20, 2024

Conversation

crisbeto
Copy link
Member

These changes undo #14640 and #24338 since they are causing Chrome to log accessibility warnings. We don't want to use native button elements here, because they're always focusable (unless disabled) and these buttons should be completely invisible to assistive technology. AT users can navigate the tabs directly without having to use the pagination.

@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Aug 19, 2024
@crisbeto crisbeto requested a review from a team as a code owner August 19, 2024 07:21
@crisbeto crisbeto requested review from amysorto and andrewseguin and removed request for a team August 19, 2024 07:21
These changes undo angular#14640 and angular#24338 since they are causing Chrome to log accessibility warnings. We don't want to use native `button` elements here, because they're always focusable (unless disabled) and these buttons should be completely invisible to assistive technology. AT users can navigate the tabs directly without having to use the pagination.
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Aug 20, 2024
@crisbeto crisbeto removed the request for review from amysorto August 20, 2024 14:28
@crisbeto crisbeto merged commit 357f6f2 into angular:main Aug 20, 2024
22 of 24 checks passed
crisbeto added a commit that referenced this pull request Aug 20, 2024
These changes undo #14640 and #24338 since they are causing Chrome to log accessibility warnings. We don't want to use native `button` elements here, because they're always focusable (unless disabled) and these buttons should be completely invisible to assistive technology. AT users can navigate the tabs directly without having to use the pagination.

(cherry picked from commit 357f6f2)
@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 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants