W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

RE: preferences on link explanations, etc?

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Mon, 30 Jan 2017 03:59:16 +0000
To: Shivaji Kumar <kumar140ster@gmail.com>, Rich Morin <rdm@cfcl.com>
CC: WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <b63a3fc7e405429ead92e2e78399e472@XCH-RCD-001.cisco.com>
Do hovers work reliable with screen readers? If so, how does a voice-over, NVDA, etc use this style of functionality on the desktop/laptop.

Sean Murphy
Accessibility Software engineer 
Tel: +61 2 8446 7751	Cisco Systems, Inc.
The Forum 201 Pacific Highway
 Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

-----Original Message-----
From: Shivaji Kumar [mailto:kumar140ster@gmail.com] 
Sent: Monday, 30 January 2017 2:09 PM
To: Rich Morin <rdm@cfcl.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Subject: Re: preferences on link explanations, etc?

Hi Rich,

Sorry for this delay, here's my take:

We can certainly implement hovers (an attractive and efficient way to make extra information available to users), but a major constraint with hovers is that they do not lend themselves easily to responsive computing. So if you think your users are going to be primarily desktop/laptop users, then it is fine. However, if your users are going to be mainly mobile/touchscreen/tab-based, then hovers appear not to offer good options. Mobile technologies have not yet reached a point where they can replicate hover-related actions on smaller screens.
And we are not talking about accessibility yet

I look forward to others' take on this.



On 1/28/17, Rich Morin <rdm@cfcl.com> wrote:
> There are some places where I'd like to give the user a way to get an 
> explanation of a link, the level of a heading, etc.  It shouldn't be 
> there all the time, lest it become annoying.  Is there a Best Practice 
> for this (e.g., :focus, :hover)?
> -r
> --
> http://www.cfcl.com/rdm           Rich Morin           rdm@cfcl.com
> http://www.cfcl.com/rdm/resume    San Bruno, CA, USA   +1 650-873-7841
> Software system design, development, and documentation

Received on Monday, 30 January 2017 04:00:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 30 January 2017 04:00:19 UTC