Conversation
**Issue** A link used to trigger an in-page action, left on the default "Link" role with no href, is not activated by some screen readers (e.g. JAWS in browse mode), because a link with no destination has nothing to navigate to. The docs did not surface the action use case, so developers could miss that accessibleRole="Button" is required for action-only links. **Solution** - Add a "Navigation vs. Action" section to the component overview: navigation -> set href; action -> set accessibleRole="Button". - Expand the accessibleRole property note to explain why the button role matters (screen-reader activation), not just when to use it. **Testing** Documentation-only change (JSDoc); no automated test applies. No runtime or API behavior changed. Fixes #14068
|
🚀 Deployed on https://pr-14088--ui5-webcomponents-preview.netlify.app |
LilyanaOviPe
approved these changes
Sep 24, 2026
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
A link used to trigger an in-page action, left on the default "Link" role with no href, is not activated by some screen readers (e.g. JAWS in browse mode), because a link with no destination has nothing to navigate to. The docs did not surface the action use case, so developers could miss that accessibleRole="Button" is required for action-only links.
Solution
Testing
Documentation-only change (JSDoc); no automated test applies. No runtime or API behavior changed.
Fixes #14068