W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > April 2017

Re: Popup SC #75 remove

From: Marla Runyan <marlarunyan1@gmail.com>
Date: Wed, 5 Apr 2017 07:49:48 -0400
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Message-Id: <E7884819-61E4-4F37-BBE2-CCA94D42943E@gmail.com>
To: Wayne Dick <wayneedick@gmail.com>

I am in agreement with your proposal.

Agreed that it does not cover the original intent. 

I have identified multiple issues related to hover popups, whether a title attribute, custom tooltip or the like:

Issue #1: Title attribute content is obscured by enlarged pointer and is not readable. (Can be resolved by positioning tooltip above trigger).
Issue #2: Title attribute content and/or custom tooltip content extends beyond zoom window and disappears once pointer moves off the trigger (e.g. use of “onmouseout”)
Issue #3: Hover content is unintentionally triggered when navigating the page and obscures/covers other content. 

These are issues I have encountered that are specific to low vision users. Issue #2 and #3 Come into play when using screen magnification. But, I would also suggest that excessive use of content triggered by mouse hover on a webpage is distracting for many fully sighted users.  

I am not listing keyboard access here as a 4th issue, as I would assume that is covered in 2.1.1.

Questions for discussion:

1. Determine if the issues listed above are SC worthy.
2. If so, determine if these issues belong in the same SC or should be addressed separately. 
3. If not, determine if the issues could be addressed within other SCs along with techniques. 

I have a couple of short videos that capture these issues. I will upload them into Google Drive and share with the group. 


> On Mar 31, 2017, at 10:07 AM, Wayne Dick <wayneedick@gmail.com> wrote:
> I am wondering if the Popup SC should be removed from 2.1. 
> Pros to drop: 
> It is completely different from the original intent
> It will take decision time from other SCs.
> It requires a rewrite to be presentable.
> It could be dealt with in new techniques for SC 1.3.2. 
> Pros to Keep
> It is relatively easy to implement for developers
> Wayne
Received on Wednesday, 5 April 2017 11:50:22 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:34 UTC