[
https://issues.apache.org/jira/browse/WICKET-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Del Bene updated WICKET-7131:
------------------------------------
Fix Version/s: 10.3.0
> Improve accessibility and screen reader support for auto-complete component
> ---------------------------------------------------------------------------
>
> Key: WICKET-7131
> URL: https://issues.apache.org/jira/browse/WICKET-7131
> Project: Wicket
> Issue Type: Improvement
> Reporter: Erik Strid
> Assignee: Martin Tzvetanov Grigorov
> Priority: Minor
> Fix For: 10.3.0, 9.19.0
>
>
> There are several accessibility issues with the auto-complete component that
> should be addressed to improve support for screen readers.
> See
> https://www.w3.org/WAI/ARIA/apg/patterns/combobox/examples/combobox-autocomplete-both/
> for examples and more details.
> To summarize, the following improvements are needed:
> * The up and down arrow keys in the auto-complete dropdown should not move
> the cursor to the start or end of the text field
> * aria-expanded should be set on the input element to indicate whether the
> dropdown is expanded or collapsed
> * aria-selected should be set on the element that is currently selected in
> the dropdown
> * aria-activedescendant attribute should be used on the input field,
> pointing to the currently selected item in the dropdown. This allows screen
> readers to track the active selection in the list.
> * aria-live should not be set on the dropdown as it will cause a screen
> reader to read out everything in the dropdown, which disrupts the navigaition
> workflow
> Some of these issues were addressed in WICKET-7120. But the current
> implementation relies on the dropdown being an unordered list, which may not
> work for all situations. And that issue where only merged to the main branch,
> which we cannot use due to Jakarta EE namespace changes in Wicket 10.
> I will provide a pull request with these changes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
