Comment 36 for bug 1187993

Thanks for your testing, Galen. I've rebased and pushed several commits:
* A commit avoiding the use of the .mjs extension.
* Seeing no objections on the mailing list, and since node 16.x reached end of life last month anyway, a commit to use Node 18.
* A commit to fix some cases where clicking on an autocomplete option did not work

I can confirm the scan mode issue that Galen identified with Narrator in both Windows 10 and 11. Noting that this issue also affects gov.uk's accessible autocomplete, which was one of my inspirations while creating this patch.

If folks have any ideas about how to fix the Narrator issue, I'd gladly do so. If not, though, I'd propose not blocking this pullrequest over the Narrator issue. NVDA and VoiceOver are both working as expected for me, and both are used much more widely than Narrator per WebAIM's most recent survey (https://webaim.org/projects/screenreadersurvey9/).