screen reader doesn't announce auto complete suggestion
See original GitHub issueLooking forward for reporting a security issue:
Please report security issues by sending an email to security@freecodecamp.org
instead of raising a GitHub issue.
Describe the bug A clear and concise description of what the bug is. I’ve been learning programming from freecodecamp for a while. the autocomplete feature used to work well, but it seems that it has broken for a while. the issue is the screen reader (NVDA) doesn’t announce the available suggestion and doesn’t announce anything if suggestion is accepted using tab key. it used to work well. To Reproduce Steps to reproduce the behavior:
- enable screen reader and go to anyjava script challange on freecodecamp
- focus the editor window and press (alt+f1 and then ctrl+e to enable accessibility)
- type “console.” use up/down arrow to access suggestion (NVDA should announce suggestion but it doesn’t)
- press tab to accept the suggestion (NVDA should announce what suggestion has been accepted but it doesn’t) Expected behavior A clear and concise description of what you expected to happen. I expected screen reader to announce the auto complete suggestion and I also expect it to let me know what suggestion has been accepted. Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: windows 10
- Browser: chrome on windows, microsoft edge (chromium based on windows)
- Version: [chrome: 83.0.4103.116 ], [microsoft edge:83.0.478.54 ]
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
aria-autocomplete attribute (aria) - a11ysupport.io
Screen reader users need to be aware that a form control has inline autocomplete behavior before they start typing so that the behavior...
Read more >Autocomplete requires ARIA for screen-reader users - Drupal
1. Resolve the issue where screen reader users may unintentionally select an inappropriate item in an autocomplete field. 2. Improve the markup ...
Read more >Guidelines for the accessibility of an autocompletion component
Autocomplete components are increasingly common in user interfaces, yet they often remain inaccessible. We therefore decided to carry out an ...
Read more >Anatomy of an Accessible Auto Suggest - UX Mastery
We must tell screen reader users that the input field is an auto-suggest and that, depending on their input, there may be suggestions...
Read more >Anatomy of an accessible auto-suggest - Intopia
Screen readers are another area where these auto-suggests often fall short. Unless the number of available suggestions is announced to ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting.
IMHO, we should disable the autocompletion, but I can see it to be aid for a11y reasons. We should figure out how to get this working conditionally.
Hi,
We are closing old issues/pull-requests that we think are stale. If you need still need help with this or are fixing this, please open a fresh issue/pull-request.
Thanks for your understanding.
Happy contributing.