search

MelSumner / a11y-automation

Open-source project. Tracking the available automation for accessibility. What a11y failures can be linted & tested for in an automated fashion?
https://a11y-automation.dev
235 stars 34 forks source link

Consider: keyboard navigation on lists. #398

Open MelSumner opened 2 years ago

MelSumner commented 2 years ago

For now, I've removed the potential violation related to keyboard navigation for lists.

"Lists should be navigable with the UP and DOWN ARROW keys"

But is this accurate?

Lists are not eligible for interaction, and there are some linting rules that prevent this very thing. Conversely, there's the MDN article about adding keyboard navigation to lists. https://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgets

Determine if this removal (PR #397 ) was correct, or if this is not only permissible but valid and should be re-added.

scottaohara commented 1 year ago

what did "list" mean here? if a static list, e.g., one rendered by menu, ul, or ol elements in html, or ARIA role=list, then the removal of this seems a good thing, as it would have otherwise been promoting false assertions.

if "list" means a 'listbox', or is a more universal term that can be associated with treeviews or even data tables, then there is some validity to it.... but as is often the case, people use general umbrella terms rather than specify exactly what they mean, and thus uncertainty like this occurs.