-
Notifications
You must be signed in to change notification settings - Fork 161
refactor(carousel): Tab order of carousel items #17456
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
Merged
+36
−30
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
717e9d9
refactor(carousel): Tab order of carousel items
rkaraivanov 5104a4a
Merge branch 'master' into rkaraivanov/carousel-focus-tab-order
kdinev 0ec9acd
Potential fix for pull request finding
kdinev 581dc8f
Merge branch 'master' into rkaraivanov/carousel-focus-tab-order
kdinev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added three specs to
carousel.component.spec.tsinsidedescribe('Base Tests: ...')to lock in the expected tab order:should render indicators before navigation buttons in the DOM to preserve tab order— usescompareDocumentPositionto assert the indicators container precedes both the prev and next buttons in DOM order (indicators → prev → next).should have active indicator as first keyboard-focusable element when navigation is disabled— verifies the active indicator hastabindex="0", inactive ones havetabindex="-1", and the indicators container precedes the active slide when navigation buttons are absent.should have navigation buttons precede active slide when indicators are hidden— verifies nav buttons appear before the active slide in the DOM when indicators are hidden.