Problem/Motivation
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.
Steps to reproduce
- Install Drupal core 10.4.5 with the standard profile.
- Create at least three administrator user accounts that start with the same sequence of letters.
- Log in as one of the administrators, using the JAWS screenreader and Firefox.
- Create a new content item.
- Expand the Authoring information section.
- In the Authored by field, start typing the sequence of letters.
- Note the screenreader announces the number of results, and says to use down arrow to select a result.
- Arrow down once.
- Note the first item is highlighted.
- Arrow down again.
- Note the screenreader is now on the field help text.
- Tab backward to the Authored by field.
- Clear the contents of the field.
- Type the sequence of characters again.
- Arrow down once.
- Note the first result is highlighted.
- Hit Enter to select the result.
- Note the Authored by field still contains just the sequence of characters.
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
Proposed resolution
This may be a JAWS bug.
Remaining tasks
Additional testing. Screenshots and screen recordings.
User interface changes
N/A
Introduced terminology
N/A
API changes
N/A
Data model changes
N/A
Release notes snippet
TBD