WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Actions revealed upon hover-over

for

From: Jonathan Cohn
Date: Nov 8, 2023 7:40AM

Hover is generally a bad feature for full accessibility. If you have this option list open on focus, then there is still a need to let the bind user know that an expansion of options has occurred. You also need to consider how the default action will be implemented for keyboard only users.

Best wishes,

Jonathan Cohn



> On Nov 7, 2023, at 12:21 PM, Damon van Vessem < <EMAIL REMOVED> > wrote:
>
> Let’s say I have cards or table rows. Each of those has a main action
> (navigate to the details screen), but also reveals additional actions (e.g.
> Add to favorites) upon hovering over the card or row. Should the reveal
> happen on both hover and focus, and is such parity good practice in general?
>
> (I’m seeing other implementations, too, which may be more robust. Some,
> like Zillow, always show the actions, i.e. like a touch UI. Others, like
> Netflix, show the actions upon hover but not focus, and use the details
> screen as a fallback where all actions can be shown.)
>
> Thanks in advance for your insights!
> Damon
> > > >