SAP / ui5-webcomponents

UI5 Web Components - the enterprise-flavored sugar on top of native APIs! Build SAP Fiori user interfaces with the technology of your choice.
https://sap.github.io/ui5-webcomponents/
Apache License 2.0
1.56k stars 267 forks source link

input: screen reader announces previous search data even when search field is cleared #9206

Closed achuth2912 closed 3 months ago

achuth2912 commented 5 months ago

Describe the bug

After deleting the search input text and access search field again, screen reader announces previous search data and its results.

Isolated Example

https://sap.github.io/ui5-webcomponents-react/?path=/story/inputs-input--with-suggestion-item

Reproduction steps

  1. Turn ON JAWS and navigate to search field and enter input.
  2. using down arrow key select the value from the dropdown list
  3. Then clear the value inside the search filed , then focus back on the search field where the screen reader announces the previous results ...

Expected Behaviour

Whenever search field is accessed, only its name, role and property should be read out as it is read when freshly accessed. But previous search related information should not be read.

Screenshots or Videos

https://github.com/SAP/ui5-webcomponents-react/assets/71249041/ada334b7-8554-4b1e-be7b-e9565e9ef9e8

UI5 Web Components for React Version

1.28.1

UI5 Web Components Version

1.24.0

Browser

Chrome

Operating System

Mac OS

Additional Context

No response

Relevant log output

No response

Organization

No response

Declaration

Lukas742 commented 5 months ago

Hi @achuth2912

thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.


Hi colleagues, I unfortunately can't test this behavior with JAWS as I don't have access to it, but with Apple VoiceOver it's working as expected for me. Could you kindly check if this is an issue with the component, or with JAWS?

achuth2912 commented 5 months ago

Even i am not able to reproduce this issue with Apple VoiceOver. But we are able to reproduce this issue with JAWS screen reader, also if we observe the DOM with span id "ui5wc_118-selectionText" does not get cleared when the search is cleared & then this would read by JAWS when we again focus back on the search field

kineticjs commented 4 months ago

Hi @achuth2912,

Thank you for reporting this finding. Would you please also give us the version of JAWS that you use when reproducing the issue?

Thanks

achuth2912 commented 4 months ago

Hi @kineticjs ,

I was using JAWS 2024 version for testing this one. One more thing to highlight here, if you observe the attached recording when we clear the search there is one div with id="ui5wc_1-selectionText" this div contains some value like "List Item 3 of 6" this is being announced when you again start the search.

GerganaKremenska commented 4 months ago

Hello @achuth2912,

I have tested the Input with suggestions and i am not able to reproduce the issue.
Please see the attached video and confirm that these are the correct steps.

https://github.com/SAP/ui5-webcomponents/assets/22882174/dfd257f6-acba-43c9-b55d-6e8c426c3cde

Also i have added the speech out put of the Intput so it is visible that there is no announcment of selected value after returning to the input.

Veersion of JAWS 2024.2312.53 Provide your subversion, maybe there is some Jaws issue.

If some steps are missed to reproduce the issue, please provide them.

"One more thing to highlight here, if you observe the attached recording when we clear the search there is one div with id="ui5wc_1-selectionText" this div contains some value like "List Item 3 of 6" this is being announced when you again start the search." - this is also not reproducable

Awaiting your feedback.

Best Regards, Gergana

github-actions[bot] commented 3 months ago

Hello, everyone! The issue has been inactive for 21 days. If there are still questions or comments, please feel free to continue the discussion. Inactive issues will be closed after 7 days!

github-actions[bot] commented 3 months ago

Hello, everyone! The issue has been inactive for 28 days, so I am closing the issue.