E-mail List Archives
Thread: Actions revealed upon hover-over
Number of posts in this thread: 3 (In chronological order)
From: Damon van Vessem
Date: Tue, Nov 07 2023 10:21AM
Subject: Actions revealed upon hover-over
No previous message | Next message →
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
From: Jonathan Cohn
Date: Wed, Nov 08 2023 7:40AM
Subject: Re: Actions revealed upon hover-over
← Previous message | Next message →
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 ADDRESS 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
> > > >
From: Jeremy Echols
Date: Wed, Nov 08 2023 8:11AM
Subject: Re: Actions revealed upon hover-over
← Previous message | No next message
It's also just awful for mobile users - there's no hover *or* focus for them. This is usability, not just accessibility, but sometimes it's more convincing to pose the usability argument with an example that is easy for "normal" people to see. Then you can translate that to other areas. E.g., "remember how hard it was to see that feature on your phone? That frustration is exactly what a blind person feels every time they try to do X."
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Jonathan Cohn
Sent: Wednesday, November 8, 2023 06:41
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Actions revealed upon hover-over
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 ADDRESS 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
> > > https://urldefense.com/v3/__http://list.webaim.org/__;!!C5qS4YX3!CEU2U
> FnEDyErtJ1zTaQCZPGEOOTD_3t-iLrIkSIocrnG3A7cA1UycshSbvjO-3GtoyOAi-969D5
> 6_E4uDlNujw$ List archives at
> https://urldefense.com/v3/__http://webaim.org/discussion/archives__;!!
> C5qS4YX3!CEU2UFnEDyErtJ1zTaQCZPGEOOTD_3t-iLrIkSIocrnG3A7cA1UycshSbvjO-
> 3GtoyOAi-969D56_E6D3hMLBw$ > = EMAIL ADDRESS REMOVED =