accessible-autocomplete: Value of input not being updated by Dragon NaturallySpeaking
When using Dragon NaturallySpeaking
, and the autocomplete dropdown is populated with an answer, the native select
form element value is not updated. This prevents the user from continuing to the next page given that answers are required on this particular page.
This is issue was recently found during an accessibility audit we had, and the same issue has been previously documented here by another testing team.
The above article was published in 2018, and the version of accessible-autocomplete
that we use is from 2020.
I cannot see anything in the releases after 2020 that relates to this problem. Is this a known issue that is being worked on? I couldn’t see anything directly related to this in the issue backlog.
My first approach would be to update to the latest, but as mentioned above, I couldn’t see anything relating to this issue in the commits since.
Any guidance on this would be appreciated.
About this issue
- Original URL
- State: open
- Created 8 months ago
- Comments: 18 (12 by maintainers)
@querkmachine we built the Accessible Autocomplete specifically to handle this - we had a fix that worked. I believe the solution was to regularly poll the value. It’s possible that Dragon has changed something to break this, but it could be a number of other issues.
@armoj Alright, thanks for clarifying 👍
@armoj there’s a number of things that can cause the select not to get updated - such as the value not exactly matching as I alluded to above. Can you share details of your implementation?
As a solution to get you going, you can also update your configuration to additionally send the value of the autocomplete input (not the hidden select) to the server. Eg you don’t need the select to get updated. Your server can then interpret this as valid or not and proceed. This will mean you can also get invalid input / typos and would need to handle these with validation.