- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Fri, 7 Jul 2017 07:38:00 -0500
- To: Jim Allan <jimallan@tsbvi.edu>, Wayne Dick <wayneedick@gmail.com>, Marla Runyan <marlarunyan1@gmail.com>
- Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Hi Jim, Wayne, Marla, and all, We will likely need a definition for the word "obscure". Maybe use or tweak UAAG's definition? [1] It is: "To render a visual element in the same screen space as a second visual element in a way that prevents the second visual element from being visually perceived." Do we want to expand that to include use cases other than just the "same screen space"? The term "important information" is already listed in the 2.1 terms [2] so we can just link to that. Questions that will likely be raised and for which we should be prepared to answer: * What is the technique to turn off the informational content? Do authors need to provide a mechanism? * What are the other means of accessing the informational content? * Others? I would suggest removing the note as authors can indeed solve the title attribute issue in 2.1 with Marla's techniques [3]. Kindest Regards, Laura [1] https://www.w3.org/TR/UAAG20/#def-obscure [2] https://github.com/w3c/wcag21/blob/master/guidelines/terms/21/ [3] https://jsfiddle.net/obsqynyp/4/ On 7/6/17, Jim Allan <jimallan@tsbvi.edu> wrote: > I just updated the wiki > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover#Proposed > : > with something similar. > > LVTF should resolve on list and get a final resolution on next thursdays > (7/13) call. and go to survey the following tuesday AG call (7/18) > > On Thu, Jul 6, 2017 at 2:41 PM, WayneEDick <notifications@github.com> > wrote: > >> Meta Data on Hover / Popup Interference >> Informational content which appears on hover that is necessary for >> understanding must: >> • be fully visible, >> • be available on focus as well as hover >> • be available via any input method. >> • not be obscured, and >> • not obscure important content that is related to the triggering event. >> I looked at “Popup Interference” and the original Meta Data on Hover and >> realized that there was only one thing in Popup Interference that was not >> in the original wording. That is the last point: >> Marla’s giant title contents example, “Div on Hover Obscuring Content >> Example”, falls into the “is obscured” category. The hover content is not >> obscured. >> Question on clarity? Is it clear that all the information required on >> focus must also satisfy the other points. That is: Popups from focus >> different from hover popups and thus exempted from obscuring other >> content? >> >> Wayne >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> <https://github.com/w3c/wcag21/issues/75#issuecomment-313498562>, or mute >> the thread >> <https://github.com/notifications/unsubscribe-auth/AG_WL5JPBGSE2j4CJhrPW95lbgXFxz-6ks5sLThrgaJpZM4LB0zx> >> . >> > > > > -- > Jim Allan, Accessibility Coordinator > Texas School for the Blind and Visually Impaired > 1100 W. 45th St., Austin, Texas 78756 > voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ > "We shape our tools and thereafter our tools shape us." McLuhan, 1964 > -- Laura L. Carlson
Received on Friday, 7 July 2017 12:38:33 UTC