Minutes: Low Vision Task Force 10 Aug 2017

source: https://www.w3.org/2017/08/10-lvtf-minutes.html

- DRAFT - Low Vision Accessibility Task Force Teleconference 10 Aug 2017

See also: IRC log <http://www.w3.org/2017/08/10-lvtf-irc>
Attendees
PresentJim, Shawn, Scott, Laura, GlendaRegretsJohnRChairJimScribeLaura
Contents

   - Topics <https://www.w3.org/2017/08/10-lvtf-minutes.html#agenda>
      1. Popup Interference (MetaData on Hover)
      <https://www.w3.org/2017/08/10-lvtf-minutes.html#item01>
   - Summary of Action Items
   <https://www.w3.org/2017/08/10-lvtf-minutes.html#ActionSummary>
   - Summary of Resolutions
   <https://www.w3.org/2017/08/10-lvtf-minutes.html#ResolutionSummary>

------------------------------

<AllanJ_> Partial Meeting Popup on the AG call

<AllanJ_>
https://rawgit.com/w3c/wcag21/popup-interference_ISSUE-75/guidelines/sc/21/popup-visibility.html

<scott> having trouble getting on the conference give me a moment

<scribe> Scribe: Laura

<shawn> Participation info:
https://www.w3.org/WAI/GL/low-vision-a11y-tf/#participation
Popup Interference (MetaData on Hover)

<AllanJ_>
https://rawgit.com/w3c/wcag21/popup-interference_ISSUE-75/guidelines/sc/21/popup-visibility.html

<AllanJ_> https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/

Jim: short meeting today.
... then we will join AG meeting.
... lots of discussion. New wording now.
... please fill out the survey.

wording is more verbose to avoid “popup”.

scribe: now called “additional content.”
... Popup SC almost as bad as Adapting Text to get consensus on

<scott> survey link works

other item is printing

scribe: printing will go on the next survey.
... explained to chairs about adding to 100%
... hopefully we will get it in.
... need to work on understanding docs next. LVTF can help.

shawn: probably use Github, and normal avenues

Glenda: 2.1 SCs are harder than 2.0 SCs. Takes longer for people to
understand.
... remember 5 stages of accessibility:
http://simplyaccessible.com/article/five-stages-of-accessibility/

<Glenda> I love Featherstone’s 5 stages of accessibility grief. Progress
includes denial, anger, bargaining and depression before there is
acceptance. See
http://simplyaccessible.com/article/five-stages-of-accessibility/

<AllanJ_> For content that becomes visible when triggered by a user
interface component receiving keyboard focus or pointer hover, the
following are true, except where the visual presentation of the content is
controlled by the user agent and is not modified by the author:

<AllanJ_> Visible trigger

<AllanJ_> Either the additional content does not obscure any essential
content within the triggering user interface component, or the additional
content can be closed or repositioned by the user.

<AllanJ_> Hover

<AllanJ_> The additional content remains visible when the pointer is moved
over it, if it was triggered via pointer hover

<AllanJ_> Focus

<AllanJ_> The additional content remains visible while the triggering user
interface component has keyboard focus, unless the user dismisses the
additional content.

jim: @alastc’s text looks good.

<scott> I lke it

https://github.com/w3c/wcag21/issues/75#issuecomment-321582748

all: unanimous agreement: we all love Alastair

<AllanJ_> survey version...
https://rawgit.com/w3c/wcag21/popup-interference_ISSUE-75/guidelines/sc/21/popup-visibility.html

Jim: everyone please vote.

<AllanJ_> Meeting adjourned 10:30 to attend AG call

<AllanJ_> trackbot, end meeting
Summary of Action Items Summary of Resolutions [End of minutes]

-- 
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

Received on Thursday, 10 August 2017 15:51:09 UTC