RE: Content on Hover or Focus

Thinking about this a bit more, how about:

…, unless the additional content communicates an input error<http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#dfn-input-error> or the additional content neither obscures nor replaces other content;

Steve

From: Repsher, Stephen J
Sent: Wednesday, January 17, 2018 1:23 PM
To: David MacDonald <david100@sympatico.ca>
Cc: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: RE: Content on Hover or Focus

It means the former, not the latter, in your reply below.  I don’t think it’s a run-on sentence, but perhaps confusing conjunctions.  Are others confused?

This was not meant to cover tabbed interfaces.  That is covered by the change to the initial sentence of the SC.

Steve

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Wednesday, January 17, 2018 2:25 AM
To: Repsher, Stephen J <stephen.j.repsher@boeing.com<mailto:stephen.j.repsher@boeing.com>>
Cc: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Re: Content on Hover or Focus

> unless the additional content communicates an input error<http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#dfn-input-error> or does not obscure or replace other content;

This makes my head spin a bit...

Do you mean " ...does not obscure, or does not replace ..."
Or
"... does not obscure, or *does* replace ..."

I think you mean the latter because that is what a tabbed interface does.

If so then I think it would have to say something like:

...unless the additional content:
- communicates an input error<http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#dfn-input-error> or
- it replaces other content (rather than obscures it); or
- it does not obscure other content

So these would be sub bullets which is not ideal, but better than a run on sentence that oscillates between "does" and "does not"




Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>

On Wed, Jan 17, 2018 at 1:45 AM, Repsher, Stephen J <stephen.j.repsher@boeing.com<mailto:stephen.j.repsher@boeing.com>> wrote:
Hi everyone,

I’ve attempted to resolve all open issues and discussion regarding Content on Hover or Focus, and I’m proposing the following changes to the SC:

1.       Revision to Hoverable condition to use more plain language (issues #695 and #711)

2.       Revised initial sentence to scope to additional content which also disappears on hover or focus.  This is needed to scope out content that may appear on focus such as in a tab list, drop down box, etc. (issue #650)

3.       Adds an exception to the Dismissable condition when the additional content doesn't obscure or replace anything.  This addresses comments on mailing list regarding things like help content inserted inline when an input field has focus.

Please review the changes here: http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#content-on-hover-or-focus


Comment here or on the pull request at https://github.com/w3c/wcag21/pull/739


Thanks!

Steve Repsher
Twitter<https://twitter.com/steverep> | LinkedIn<https://www.linkedin.com/in/steverepsherjr/> | GitHub<https://github.com/steverep>