fix(a11y): stepper-completed step does not have accessible notification after completion

[andyfeds]

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?

• 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?

In the Stepper, when the step is complete, keyboard focus moves to the next step but there's no indication that the previous step is completed by the screen reader.

Issue Number: CDE-699

What is the new behavior?

The screen reader will announce that the current step is complete (or failed) and move focus to the next step or stay in the same step in case of an error.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[github-actions]

👋 @andyfeds,

• 🙏 The Clarity team thanks you for opening a pull request
• 🎉 The build for this PR has succeeded
• 🔍 The PR is now ready for review
• 🍿 In the meantime, view a preview of this PR
• 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal Clarity Support space

Thank you,

🤖 Clarity Release Bot

[mivaylo]

Do we intend to backport this to v16? and to v15 if we do it before 28th of March (this is the end of support date for v15)?

[mivaylo]

Do we intend to backport this to v16? and to v15 if we do it before 28th of March (this is the end of support date for v15)?

although we are adding new API - so this seems more like a "feat" rather than a "fix" to me, but it still is not a breaking change, so it could be backported

[andyfeds]

Do we intend to backport this to v16? and to v15 if we do it before 28th of March (this is the end of support date for v15)?

although we are adding new API - so this seems more like a "feat" rather than a "fix" to me, but it still is not a breaking change, so it could be backported

Yeah, its not a breaking change, just changes the behaviour for screen readers.

[github-actions]

The backport to 16.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-16.x 16.x
# Navigate to the new working tree
cd .worktrees/backport-16.x
# Create a new branch
git switch --create backport-1334-to-16.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0c02a7a2478763f9bc711d526a9ef9f81ffc6bc8
# Push it to GitHub
git push --set-upstream origin backport-1334-to-16.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-16.x

Then, create a pull request where the base branch is 16.x and the compare/head branch is backport-1334-to-16.x.

[github-actions]

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.