You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We discussed the issue internally with the responsible accessibility expert and it turns out the missing readings you described are caused by the DOM structure utilising buttons, as the component is designed to slot toggle buttons.
While, on UI5 control (sap.m.SegmentedButton) side list of options ("li" elements, instead of buttons) has been used.
To fix the issue, we will need to perform bigger refactoring than expected, not just adding or replacing ARIA attributes, but changing the DOM elements, which might result in replacing the ui5-togglebutton with something else and API breaking change.
For that we will create a backlog for refactoring of the SegmentedButton, once created it will be linked here.
Then, we will close the current issue, but you will be able track the progress within the refactoring backlog (another GitHub issue at the end).
as mentioned in my previous message, fixing the announcements of the SegmentedButton would require significant refactoring. For that, we created a new issue: #3191
I will close the current one, it's is referenced in the new one for traceability.
You can see the details and follow the progress here: #3191
Describe the bug
The method of interaction for segmented button not clear for screen reader users
To reproduce
Open JAWS and focus on the segmented button. The the instruction text announced by JAWS is not clear enough.
Expected behavior
![image](https://user-images.githubusercontent.com/1995447/110690418-c41a4480-8198-11eb-882d-6b6015f5afd3.png)
The expected texts for screen reader should be same as what we have for sap.m.SegmentedButton
Context
UI5 Web Components version: 0.29.6
Affected components (if known)
ui5-segmentedbutton
Organization: (if applicable)
SAP SuccessFactors
Priority: (optional) (Low, Medium, High or Very High)
Medium
The text was updated successfully, but these errors were encountered: