I was trying to operate the main Kagi search with keyboard only in Google Chrome on Mac OS.
I found an issue in the Search Options tabbed palette toolbar that appears below the main search input field.
i notice that, while I can tab through to the search source popup (the one where the default setting is "Usenet/Web"), pressing ENTER does not pop up the menu.
Similarly, the menu labeled "More" does not pop up when pressing ENTER
These menus do popup with SPACE, which is good, but ENTER should also be supported. Other controls seem to respond to ENTER just fine.
The close box, which is not always present, and which appears after the More popup does not respond to ENTER or SPACE.
Full disclosure, I work with digital accessibility and WCAG professionally, so I am always curious how various sites conform to WCAG, and which solutions are used. If I find an accessibility flaw in a site that I like, I make an effort to report it. We are all responsible for making the web more accessible. It's likely that I will find some other issues. [Ominous music].
I think kagi is a superb search engine, and I am glad to finally have a viable alternative to google search, and happy to pay the subscription fee. I want kagi to be a good experience for all users, including those that rely on keyboard operation.
All operational elements and controls should respond to ENTER and SPACE as if they had been clicked. This is the standard idiom for web interaction with keyboard, and is the default behavior for all interactive elements. (Hyperlinks are a special case - responding only to ENTER).
Most browsers fire a synthetic click event when an operable element is in focus, and ENTER is pressed. Listening for a click is the easiest and most predictable way to conform to WCAG success criterion 2.1.1
