-
Bug
-
Resolution: Fixed
-
Low
-
7.21.0
-
2
-
Severity 1 - Critical
-
14
-
Issue Summary
The button to open the settings menu for the diff view in the main content area does not have a label.
Steps to Reproduce
- Launch the URL
- Navigate to the button to open the settings menu in the main content area.
Screenshot
Actual Results
The button for opening the setting menu for Diff view section in the main content area , has no label associated to it . When screen readers reach this button with no label they announce “button”. Blind users will be unable to identify the purpose of this button.In the absence of label, it becomes difficult for users especially screen reader users to understand the purpose of the form control and input information.
Expected Results
Add descriptive label for the button via the aria-label attribute. For example, provide the label as “Diff view setting”.
This will help to make the purpose of form controls meaningful for screen reader users.
Workaround
Currently there is no workaround available
Bug Ref: 739123
Form Name |
---|
Project pull request : The menu button to open and close the different view settings is not labelled
-
Bug
-
Resolution: Fixed
-
Low
-
7.21.0
-
2
-
Severity 1 - Critical
-
14
-
Issue Summary
The button to open the settings menu for the diff view in the main content area does not have a label.
Steps to Reproduce
- Launch the URL
- Navigate to the button to open the settings menu in the main content area.
Screenshot
Actual Results
The button for opening the setting menu for Diff view section in the main content area , has no label associated to it . When screen readers reach this button with no label they announce “button”. Blind users will be unable to identify the purpose of this button.In the absence of label, it becomes difficult for users especially screen reader users to understand the purpose of the form control and input information.
Expected Results
Add descriptive label for the button via the aria-label attribute. For example, provide the label as “Diff view setting”.
This will help to make the purpose of form controls meaningful for screen reader users.
Workaround
Currently there is no workaround available
Bug Ref: 739123