Re: Popup SC need comments

+1

Let's get it to the wider group.

Laura

On 7/26/17, Jim Allan <jimallan@tsbvi.edu> wrote:
> I can go either way. To me, obscure means to cover up, which would make the
> part covered invisible.
> I thinks its ready to send to AG and let them beat on it...then the
> smithing will begin in earnest.
>
> Any other thoughts?
> Discuss tomorrow and send to AG for survey for discussion on Tuesday.
>
> Jim
>
> On Wed, Jul 26, 2017 at 12:01 PM, Repsher, Stephen J <
> stephen.j.repsher@boeing.com> wrote:
>
>> I agree with Jim that visible is already used several times in WCAG 2.0,
>> so giving a definition here would complicate the whole document.
>>
>>
>>
>> Using obscure is okay, but is it needed if only used once?  Does it raise
>> more questions than it answers (e.g. what if part of the trigger is not
>> in
>> the screen space, or what is meant by perceive)?  I’m just playing
>> devil’s
>> advocate.  Unless we’re talking about popups with non-zero opacity,
>> invisible is probably fine if visible is fine.
>>
>>
>>
>> Steve
>>
>>
>>
>> *From:* Jim Allan [mailto:jimallan@tsbvi.edu]
>> *Sent:* Tuesday, July 25, 2017 2:48 PM
>> *To:* Laura Carlson <laura.lee.carlson@gmail.com>
>> *Cc:* Repsher, Stephen J <stephen.j.repsher@boeing.com>;
>> public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
>> *Subject:* Re: Popup SC need comments
>>
>>
>>
>> ​
>>
>> On Tue, Jul 25, 2017 at 1:10 PM, Laura Carlson <laura.lee.carlson@
>> gmail.com> wrote:
>>
>> Hi Jim, Stephen, and all,
>>
>> With this rendition do we need definitions for "visible" and "invisible"?
>>
>> At one point we used the word "obscure". UAAG's definition 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."
>> https://www.w3.org/TR/UAAG20/#def-obscure
>>
>>
>>
>> I like obscure. After fiddling/editing a bit, seems "obscure" works only
>> for TRIGGER. Only edit Trigger bullet.  I looked in WCAG20, where
>> 'visible'
>> is used 5 times. It is never defined. Don't think we need to define it.
>>
>>
>>
>> edited version
>>
>> *Popup Interference:* Except where popup presentation is controlled by
>> the user agent, all of the following are true when popup content is
>> visible:
>>
>> ·       *Trigger*: Popup content does not obscure any part of its
>> triggering content.
>>
>> ·       *Hover:* If a popup is triggered via pointer hover, then the
>> pointer may be moved onto the popup content without loss of visibility.
>>
>> ·       *Focus:* Popup content remains visible while any of its
>> components, including the trigger, have focus.
>>
>> Where we define popup as " becomes visible only on pointer hover or
>> focus”.
>>
>> ORIGINAL
>>
>> *Popup Interference:* Except where popup presentation is controlled by
>> the user agent, all of the following are true when popup content is
>> visible:
>>
>> ·       *Trigger*: Popup content does not render any part of its
>> triggering content invisible.
>>
>> ·       *Hover:* If a popup is triggered via pointer hover, then the
>> pointer may be moved onto the popup content without loss of visibility.
>>
>> ·       *Focus:* Popup content remains visible while any of its
>> components, including the trigger, have focus.
>>
>> Where we define popup as " becomes visible only on pointer hover or
>> focus”.
>>
>>
>>
>> ​​
>>
>> On Tue, Jul 25, 2017 at 1:10 PM, Laura Carlson <
>> laura.lee.carlson@gmail.com> wrote:
>>
>> Hi Jim, Stephen, and all,
>>
>> With this rendition do we need definitions for "visible" and "invisible"?
>>
>> At one point we used the word "obscure". UAAG's definition 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."
>> https://www.w3.org/TR/UAAG20/#def-obscure
>>
>> It would be nice to get the readability level down a bit more but we
>> could work on that later.
>>
>> Kindest Regards,
>> Laura
>>
>>
>> On 7/25/17, Jim Allan <jimallan@tsbvi.edu> wrote:
>> > All,
>> > Steve, Laura, and others have been working on this SC. Below is the
>> result.
>> > If we could have comments soon. I would like to see if we can get this
>> > on
>> > the queue for the Thursday AG meeting.
>> >
>> > *Popup Interference:* Except where popup presentation is controlled by
>> the
>> > user agent, all of the following are true when popup content is
>> > visible:
>> >
>> > ·       *Trigger*: Popup content does not render any part of its
>> triggering
>> > content invisible.
>> >
>> > ·       *Hover:* If a popup is triggered via pointer hover, then the
>> > pointer may be moved onto the popup content without loss of visibility.
>> >
>> > ·       *Focus:* Popup content remains visible while any of its
>> components,
>>
>> > including the trigger, have focus.
>> >
>> > Where we define popup as " becomes visible only on pointer hover or
>> focus”.
>> >
>> > What does everyone think?  Any inaccessible gaps?
>> >
>> >
>> >
>> >
>> >
>> > --
>> > 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
>>
>>
>>
>>
>>
>> --
>>
>> Jim Allan, Accessibility Coordinator
>>
>> Texas School for the Blind and Visually Impaired
>> 1100 W. 45th St., Austin, Texas 78756
>> voice 512.206.9315 <(512)%20206-9315>    fax: 512.206.9264
>> <(512)%20206-9264>  http://www.tsbvi.edu/
>>
>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>
>
>
>
> --
> 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.9452 http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>


-- 
Laura L. Carlson

Received on Wednesday, 26 July 2017 18:12:36 UTC