[ui5-daterange-picker]: "unavailable" still will be announced after ui5-daterange-picker changed from disabled to enabled

[GongRichard]

Bug Description

"unavailable" still will be announced after ui5-daterange-picker changed from disabled to enabled

Affected Component

ui5-daterange-picker

Expected Behaviour

"unavailable" should not be announced after ui5-daterange-picker became enabled

Isolated Example

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

Steps to Reproduce

1. open page https://stackblitz.com/edit/github-ztfbmbrx?file=src%2FApp.tsx
2. open JAWS 2026
3. check on Enable/Disable Date Range Picker
4. tab to Date Range Picker
5. check speech history of JAWS and you will see it will read out "unavailable"

This issue also can be reproduced in NVDA.

Log Output, Stack Trace or Screenshots

Priority

High

UI5 Web Components Version

2.25.x

Browser

Chrome

Operating System

No response

Additional Context

This issue is from customer, please fix it ASAP in 2.25.x

Organization

SAP SuccessFactors

Declaration

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

[unazko]

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

There is the following workaround in react: https://stackblitz.com/edit/github-ztfbmbrx-sdr4vgqt?file=src%2FApp.tsx
Add key={String(disabled)} to DateRangePicker. This tells React to create a completely new instance of the component each time disabled changes, so the browser's accessibility tree always starts clean. Downside: any selected date is cleared when toggling.

Probable root cause of the issue:
When the component is re-enabled, its outer shell updates immediately but the inner input field updates a fraction later (in the next animation frame). The browser reads the accessibility state during that brief gap and caches the old "disabled" status. By the time the inner input catches up, the accessibility tree is already frozen with the wrong state. This doesn't happen in plain browser usage because there's nothing else going on to trigger that early read — but React's rendering process is busy enough to hit the gap consistently.

I've started developing a fix at component's side: #14019

Best regards,
Boyan