Details
-
Bug
-
Resolution: Fixed
-
Medium
-
7.16.2
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
In 'Move page' dialog, the off-screen labels of form controls such as 'Search keywords', 'search in space',etc are not announced by screen reader.
Steps to reproduce
- Navigate to any space within Confluence.
- Navigate to any page within the space that needs to be moved.
- Navigate to the 'More options' link & activate it.
- Activate the 'Move' option from the menu.
- Navigate to 'Search' button from left navigation inside 'Move Page' dialog & activate it.
- Navigate to the form controls such as input text & dropdown elements.
Actual Results
While navigating with screen reader turned on in 'Move page' dialog, when user navigate to the form controls such as input text & dropdown elements, the off-screen labels are not announced by the screen reader. Following are the issues in the source code.
- The 'Move page' modal dialog container element has aria-hidden="true" provided incorrectly.
- The value of for & id attribute of dropdown elements don’t match. (for="move-page-search-spac" & id="move-page-search-space").
- The labels are visually hidden.
Expected Results
The screen reader should announce the labels of the form controls when they receive focus. Please perform following fixes.
- Remove the aria-hidden="true" attribute provided to the 'Move page' modal dialog container element.
- The value of for & id attribute of dropdown elements should match.
- The labels should be visible on the page.
Screenshots
Issue 725373: https://axeauditor.dequecloud.com/api/v1/file/ed57c3c8-51a8-11ec-bb2d-9753ecc594f0
BACKGROUND
People who are blind cannot use the visual presentation of a form to determine the label for a form element. In order for screen reader users to be certain of a form field's label, every form input and control needs a label, also known as an "accessible name." When form elements have a programmatically determinable accessible name, a screen reader user can put focus on a form element and the screen reader will automatically read the label and element type together. In addition, some coding methods will create a larger clickable area for the form element which benefits people with motor disabilities.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available