busola
busola copied to clipboard
ACC-264.1 (Level A) _ Modify Modules _ Button _ Information not announced
1.1 Internal Message Details Internal Message: Test Plan: ACC SAP Kyma runtime 2024 Message Priority: Medium Affected UI Button Affected Check Point: ACC-264.1 Short text: ACC-264.1 (Level A) _ Modify Modules _ Button _ Information not announced
1.2 Application Details Application Name Kyma-dashboard Technology: SAP UI5 Component: URL: https://dashboard.stage.kyma.cloud.sap/cluster/garden-kyma-stage--c-7074971-external/kymamodules Username/Password: NA 1.3 Test Environment Details Web browser: Google Chrome Version 127.0.6533.89 Operating System: Microsoft Windows 11 x64 Screen Reader: JAWS 2024 Version 2024.2406.121 ILM
1.4 JIRA/SNOW Details Issue: Bug Labels: Accessibility
2 Screen Flow • Launch the application using given URL. • Select the ‘Link to Kyma dashboard’ from the Kyma Environment section on your SAP BTP subaccount page. Now Select ‘Modify Modules’ button which opens ‘Modules’ page. • Activate ‘Edit’ tab from main region. • Navigate to ‘Modules Channel’ expand/collapse button and activate the button.
- Issue Type: Manual Observed Behavior: On accessing the expand/collapse buttons across the application e.g. ‘Labels’ , ‘Annotations’ and so on expand/collapse button, their respective labels e.g. ‘Labels’ , ‘Annotations’ is not read and extra info ‘Expand’ is announced when the region is already expanded. Also on activating the button the change in state of Ui i.e. ‘Expanded/Collapsed’ is not announced by the screen reader. Screenshot:
Case 2:
Case 3:
Case 4:
Expected Behavior: On accessing the expand/collapse buttons across the application e.g. ‘Labels’ , ‘Annotations’ and so on expand/collapse button, their respective labels e.g. ‘Labels’ , ‘Annotations’ must be read and extra info ‘Expand’ must be removed from speech output. Also on activating the button the change in state of Ui i.e. ‘Expanded/Collapsed’ must be announced by the screen reader along with other necessary information. Note: This issue exists across the application and thus fix should be provided for all the occurrences.
Kindly refer to attached error and issue processing document for more details. Regards, Shubha