[
https://issues.apache.org/jira/browse/WICKET-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899375#comment-17899375
]
ASF GitHub Bot commented on WICKET-7131:
----------------------------------------
martin-g commented on PR #1034:
URL: https://github.com/apache/wicket/pull/1034#issuecomment-2484918266
```
../../wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/autocomplete/wicket-autocomplete.js
[INFO] 472 | var input = Wicket.$(ajaxAttributes.c);
[INFO] ^ 'input' is already defined.
[INFO] 626 | element.firstChild.role = "listbox"
[INFO] ^ Missing
semicolon.
[INFO] 677 | node.setAttribute("aria-posinset", i + 1)
[INFO]
^ Missing semicolon.
[INFO] 678 | node.setAttribute("aria-setsize",
elementCount)
[INFO]
^ Missing semicolon.
```
> 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
> Priority: Minor
>
> 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)
