[ui5-link][JAWS]: can't trigger onClick event by Enter/Space key when JAWS is on

[GongRichard]

Bug Description

can't trigger onClick event by Enter/Space key when JAWS is on

Affected Component

ui5-link

Expected Behaviour

should trigger onClick event by Enter/Space key when JAWS is on

Isolated Example

https://stackblitz.com/edit/github-fcq62g7y?file=src%2FApp.tsx

Steps to Reproduce

1. Open JAWS 2026
2. open page https://stackblitz.com/edit/github-fcq62g7y?file=src%2FApp.tsx
3. tab to test Link
4. click Enter/Space key and onClick event won't be triggered

Log Output, Stack Trace or Screenshots

No response

Priority

High

UI5 Web Components Version

2.25.x

Browser

Chrome

Operating System

No response

Additional Context

This issue is from customer, please take a look as soon as possible.

Organization

SAP SuccessFactors

Declaration

• I’m not disclosing any internal or sensitive information.

[niyap]

Hello @UI5/ui5-team-ctr-bal,

When JAWS is used with VPC on, the link is not activated with either Space or Enter, which appears to be the default JAWS behavior. The native HTML element behaves in the same way with Enter.

On the other hand, sap.m.Link can be activated with Space (but not Enter) even when VPC is on.

Could you please investigate further whether we should follow the default behavior or whether an additional enhancement is possible on our side?

Thank you in advance!

Kind Regards,
Niya

[unazko]

Hi @GongRichard , thanks for the report and the isolated example.

We investigated the behavior. When JAWS runs with the Virtual PC Cursor (browse mode) enabled, it activates an element with the link role by following its destination (the href), and it suppresses the keydown/keyup events the component would normally use to trigger activation. In the provided example the ui5-link has no href, so there is no destination for JAWS to follow, and the onClick handler is never reached. This is specific to browse mode and is consistent with how a native <a> element without an href behaves — in JAWS focus/forms mode the link activates as expected.

Before we decide whether a framework change is appropriate or whether this is best addressed at the application level, it would help us a lot to understand your actual scenario:

1. In your application, does the link's onClick navigate to another page/URL, or does it perform an in-page action (e.g. open a dialog, toggle a state)?
2. If it navigates, is the destination a fixed URL, or is it computed at click time?
3. If you are intentionally not using the accessibleRole="Button" API, is that a deliberate choice (you want the control announced as a link) or simply because the option wasn't known?

For context on why we're asking:

• For navigation, setting the href property lets JAWS activate the link natively, and it also restores standard browser affordances such as open-in-new-tab, middle-click, and link preview on hover.
• For a link that triggers an action rather than navigating, accessibleRole="Button" is the recommended setting and it activates correctly under JAWS.

Your answers will help us recommend the right approach and determine whether a documentation update or an enhancement is warranted.

Thank you,
Boyan

[GongRichard]

Hi @unazko ,
In our application, we perform an in-page action to show more texts. We acted as button and we missed setting accessibleRole="Button".
Thanks,
Richard