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/paginator): visual order does not match reading order #28045

Closed
wants to merge 1 commit into from

Conversation

DBowen33
Copy link
Contributor

@DBowen33 DBowen33 commented Nov 2, 2023

OBSERVED RESULTS:

The reading order of the pagination controls does not match the visual order which can be disorienting to visual users who do use screen readers or keyboard only to navigate the page.

Screenshot/screencast: https://screenshot.googleplex.com/Bd6psV6wJZ4sgji.png
User provided screenshot

EXPECTED RESULTS:

If possible, try to match the reading/focus order of elements with the visual order. Typically it is left to right, top to bottom.
STEPS TO REPRODUCE:

Enable screen reader
Navigate to https://xap-gallery.corp.google.com/embed/a11y/mdc-paginator
Navigate to the pagination controls
Observe
RELEVANT GAR SHEET

RELEVANT GAR GUIDELINE

ENVIRONMENT DETAILS:

Google Pixel 5

Android version 13
Talkback
Canary 116.0.5813.0
iPhone 12

iOS 16.4.1
VoiceOver
Dev 116.0.5805.1
Bug filing time:

10min

@DBowen33 DBowen33 closed this Nov 2, 2023
@DBowen33 DBowen33 deleted the my-fix-branch branch November 2, 2023 16:34
@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 Dec 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant