ui5-webcomponents icon indicating copy to clipboard operation
ui5-webcomponents copied to clipboard

Accessibility issue combobox

Open Bilal3120 opened this issue 2 years ago • 3 comments

Describe the bug Options not read out correctly when focussing.

Isolated Example CodeSandbox

To Reproduce Steps to reproduce the behavior:

  1. Go to CodeSandbox
  2. Open list of options in the combo box
  3. Cycle through the options using UP and DOWN keys.

Expected behavior Options should be read out like Entry 1 Text 1, Entry 2 Text 2..

Screenshots MicrosoftTeams-image (6)

UI5 Web Components for React Information @ui5/webcomponents 1.4.0: @ui5/webcomponents-react 0.25.6: Operating System: Mac OS Browser: Chrome

Bilal3120 avatar Jul 01 '22 10:07 Bilal3120

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

MarcusNotheis avatar Jul 01 '22 10:07 MarcusNotheis

Hello @SAP/ui5-webcomponents-topic-rl,

Could you please check the issue? Items text is not announced with JAWS 2022.

Regards, Nayden

nnaydenow avatar Jul 01 '22 13:07 nnaydenow

Accessibility expert analysis:

The issue is reproducible in the playground samples as well.

Currently we use the invisible messaging to announce the selected item. We call the announceSelectedItem in the combobox. For some reason (I think that this lead to double announcement) we do not include the item text nor the subtext in the announcement, which is incorrect. IMO we should include them as well, but we should test carefully before submitting anything. Some related PR:

https://github.com/SAP/ui5-webcomponents/pull/3358/files https://github.com/SAP/ui5-webcomponents/pull/5478/files

elenastoyanovaa avatar Jul 26 '22 13:07 elenastoyanovaa

Hello @Bilal3120,

The issue about not announcing the additional text of an item is fixed with the following change: https://github.com/SAP/ui5-webcomponents/pull/5943 On the other hand, the issue about not always announcing the value of the combobox is a known screen reader issue and we do not have influence over it. Here is an isolated example with native HTML elements where the issue is also reproducible: https://jsbin.com/buzakereye/edit?html,output.

Kind Regards, Niya

niyap avatar Oct 19 '22 05:10 niyap