- From: bryan rasmussen <rasmussen.bryan@gmail.com>
- Date: Fri, 8 Oct 2021 11:57:21 +0200
- To: WAI IG <w3c-wai-ig@w3.org>
- Message-ID: <CAHKsR6_d+rB6b0WQqr1cX4QDtjFaiuofT=M6YeuzP8pVfSmnbA@mail.gmail.com>
Hey, I've got a glossary - originally I started making it accessible with these rules The currently selected level is removed from the reading / navigation order - so for example if you have selected C you would hear glossary letter c selected, if you then decided to navigate through the list you would hear glossary letter A, glossary letter B, glossary letter D, glossary E.... however there is a filter on this glossary, which now I'm making accessible. So if you write in the starting phrase anti, then of course only words starting with a will be shown. so if I write anti and I tab from the filter field I hit the A button, and then tab again I go into the list of terms starting with anti. This means that the way for a keyboard user to be able to click on the letter B they should go back to the input field and remove the filter text. The reason I did this was to keep people from having to tab through all the glossary letters - but perhaps when the filter is done you should be focused in the beginning of the words matching the filter and not turn off the reaching of other glossary buttons? Thanks, Bryan Rasmussen
Received on Friday, 8 October 2021 09:58:44 UTC