-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 8.4.0, 9.2.0
-
Component/s: Accessibility
-
- 4.1.3
- Level-AA
- WCAG21
- ax-at-user
- ax-bug
- ax-confluence-2024-vpat-create/editpage
- ax-confluence-dc-2023-vpat
- ax-confluence-dc-2024-vpat
- ax-confluence-dc-2024-vpat-reuse
- ax-confluence-dc-vpat
- ax-confluence-dc-vpat-createanewpage-editor
- ax-confluence-dc-vpat-createeditpage
- ax-confluence-dc-vpat-pg07
- ax-confluence-dc-vpat-reuse
- ax-medium-priority
- ax-qa
- ax-qa-not-fixed
- ax-qa-verified
-
Severity 3 - Minor
Issue Summary
On the “Create page | Set page location” page, the dynamically updating search results are not programmatically determined.
Steps to Reproduce
- Navigate onto the above mentioned page.
- Navigate onto the “New parent page:” input field and enter a character.
- Observe that the results get dynamically updated below.
- Observe that this update is not programmatically communicated.
- Observe that the focus is not moved or a new page is not loaded.
Screen Recording
Screen Recording 2023-08-17 at 5.43.29 PM.mov![]()
Actual Results
When any character is entered in the “New parent page:” input field, a list of suggestions get updated below. This update is not programmatically indicated to the users of a screen reader. That the dynamically updating search results are not announced may confuse or mislead them.
Expected Results
Status messages must be programmatically communicated.
To achieve this, use a polite live region, such as role=“status”, and aria-atomic=”true” to make sure that the entire text node is always announced.
If this is not possible, you can move focus or prompt a page load. In such cases, you do not need to programmatically determine the status message as the change of context, such as focus moving to the added content or a new page being loaded, provides an acceptable clue to the users of assistive technologies.
Another solution could be to provide a hidden instruction, notifying the users about the search results in advance. This instruction can then be associated with the <input> element with "aria-describedby" attribute.
code snippet:
<span role="status">3 suggestions available</span> <span role="status">No suggestions found</span> <label for="i1">New parent page:</label> <input type="text" id="i1" aria-describedby="h1" ...> <span class="hiddenText" id="h1">Typing any character in this field will update a list of suggestions below.</span>
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2021)
macOS Monterey Version 12.4
Chrome - Version 103.0.5060.134 (Official Build) (arm64)
Firefox- Version 93.0 (32-bit)
Safari- Version 15.5 (17613.2.7.1.8)
JAWS- Version 2023
NVDA- Version 2023.3
Voiceover - Version Latest
- is resolved by
-
A11Y-440 Loading...