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

Re: preferences on link explanations, etc?

From: Dean Birkett | AssistiveWare <d.birkett@assistiveware.com>
Date: Mon, 30 Jan 2017 10:27:19 +0100
Cc: Shivaji Kumar <kumar140ster@gmail.com>, Rich Morin <rdm@cfcl.com>, WAI Interest Group <w3c-wai-ig@w3.org>
Message-Id: <FBEF0820-0438-413F-88FD-225B43215850@assistiveware.com>
To: "Sean Murphy (seanmmur)" <seanmmur@cisco.com>
From a UX perspective I would first be looking at the content of the page, do you really need an explanation? If you are writing technical content that does need further explanation then perhaps a better implementation would be to introduce footnotes so that those who need more info can get it without lessening the experience for those who do not need more information.

Technical link[1]

[1] This is an explanation

> On 30 Jan 2017, at 04:59, Sean Murphy (seanmmur) <seanmmur@cisco.com> wrote:
> 
> 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 
> seanmmur@cisco.com
> Tel: +61 2 8446 7751	Cisco Systems, Inc.
> The Forum 201 Pacific Highway
> ST LEONARDS
> 2065
> Australia
> cisco.com	
> 
> 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.
> 
> Best
> 
> Shivaji
> 
> 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 09:27:49 UTC

This archive was generated by hypermail 2.3.1 : Monday, 30 January 2017 09:27:50 UTC