-
Notifications
You must be signed in to change notification settings - Fork 77
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(a11y): timeline steps should have a list structure #1421
Merged
Conversation
This file contains 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
👋 @andyfeds,
Thank you, 🤖 Clarity Release Bot |
andyfeds
changed the title
fix(a11y): timeline -angular version of component does not allow <ul> <li>
fix(a11y): timeline steps should have a list structure
Jun 4, 2024
…/<li> to be added
venkateshr06
approved these changes
Jun 5, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Jun 5, 2024
## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tests for the changes have been added (for bug fixes / features) - [ ] Docs have been added / updated (for bug fixes / features) - [ ] If applicable, have a visual design approval ## PR Type What kind of change does this PR introduce? <!-- Please check the one that applies to this PR using "x". --> - [x] Bugfix - [ ] Feature - [ ] Code style update (formatting, local variables) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] CI related changes - [ ] Documentation content changes - [ ] Other... Please describe: ## What is the current behavior? Due to the absence of semantic tags `<ul>` and `<li>` in the angular version of the timeline component, screen readers do not announce the number of steps in the timeline. <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: [CDE-1181](https://jira.eng.vmware.com/browse/CDE-1181) ## What is the new behavior? Added aria roles: `role="list"` to the timeline container and `role="listitem"` to each timeline step so that screen readers consider the timeline as a list and announce the number of steps. ## Does this PR introduce a breaking change? - [ ] Yes - [x] No <!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information Co-authored-by: Andrea Fernandes <andreaf1@vmware.com> (cherry picked from commit 29d18fc)
13 tasks
andyfeds
added a commit
that referenced
this pull request
Jun 5, 2024
…6.x) (#1424) Backport 29d18fc from #1421. <br> ## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tests for the changes have been added (for bug fixes / features) - [ ] Docs have been added / updated (for bug fixes / features) - [ ] If applicable, have a visual design approval ## PR Type What kind of change does this PR introduce? <!-- Please check the one that applies to this PR using "x". --> - [x] Bugfix - [ ] Feature - [ ] Code style update (formatting, local variables) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] CI related changes - [ ] Documentation content changes - [ ] Other... Please describe: ## What is the current behavior? Due to the absence of semantic tags `<ul>` and `<li>` in the angular version of the timeline component, screen readers do not announce the number of steps in the timeline. <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: [CDE-1181](https://jira.eng.vmware.com/browse/CDE-1181) ## What is the new behavior? Added aria roles: `role="list"` to the timeline container and `role="listitem"` to each timeline step so that screen readers consider the timeline as a list and announce the number of steps. ## Does this PR introduce a breaking change? - [ ] Yes - [x] No <!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information Co-authored-by: Andrea A Fernandes <andy2890@gmail.com>
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Due to the absence of semantic tags
<ul>
and<li>
in the angular version of the timeline component, screen readers do not announce the number of steps in the timeline.Issue Number: CDE-1181
What is the new behavior?
Added aria roles:
role="list"
to the timeline container androle="listitem"
to each timeline step so that screen readers consider the timeline as a list and announce the number of steps.Does this PR introduce a breaking change?
Other information