-
Bug
-
Resolution: Fixed
-
Highest
-
8.2.3
-
Severity 3 - Minor
-
Issue Summary
On the “Livesearch” field, the search results are not programmatically communicated to the users of a screen reader.
Steps to Reproduce
- Edit the page, and add "Livesearch" macro and update the page.
- Navigate to “Livesearch” field and perfrom search operation.
- Observe that this dynamic update is not communicated to the users of screen readers
Actual Result
When a user performs valid Search operation into “Livesearch” field, search results are getting updated below the table and for invalid search operation the message such as “No result found for". displayed on page which are not announced by screen reader software.
The programmatic means of identifying the presence of search result message and suggestions are not used, so the assistive technologies such as screen reader softwares are not able to alert users to the presence of the status message/search results. Although this interaction is easier to understand for sighted users, it is not intuitive for the visually impaired.
Expected Result
Ensure that the search results/status messages that becomes available when the user search for inputted data in “Livesearch” field should get announce by the screen reader software.
- Provide the aria-live region for the search result message such as “No result found for” which becomes available when the user performs an invalid search operation.
- Screen reader users should be notified when the suggestions get updated on page along with the count of suggestions. For eg: “ 3 suggestions available for typed text.” Live regions can be used to achieve this behaviour.
- If this is not feasible, a hidden instruction should be announced (when the search input receives focus), notifying the users of the dynamic change. For eg: Typing letters in the search input updates the search results, press up/ down arrow keys to view the list of suggestions.”
- A visible label such as “LiveSearch” should be provided for input fields using <label> element. Additionally “for“ and “id” attributes should be used to associate.
- Ensure that the search result should announce when user navigates using up/down arrow keys
For more information on implementation, refer the following link : ARIA live regions implementation
Screenshot
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- causes
-
CONFSERVER-91576 Adding a Placeholder on a Livesearch Macro doesn't show the text on search field
- Closed
- mentioned in
-
Page Loading...