- Issue created by @cboyden
- π³πΏNew Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies β .
During recent testing of the core autocomplete function with two different screenreaders (JAWS and NVDA) on Windows, autocomplete was usable with NVDA but broken in JAWS.
If you repeat the steps with NVDA and Firefox, the autocomplete behaves as expected: you can arrow down and up through all the results, and you can select a result with the Enter key.
Versions used:
Windows 11
Firefox 136.0.2
JAWS 2025.2410.106
NVDA 2024.4.2
This may be a JAWS bug.
Additional testing. Screenshots and screen recordings.
N/A
N/A
N/A
N/A
TBD
Active
10.4 β¨
javascript
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies β .