- From: Erich Manser <emanser@us.ibm.com>
- Date: Thu, 22 Jun 2017 11:45:50 -0400
- To: "LVTF - low-vision-a11y" <public-low-vision-a11y-tf@w3.org>
- Message-Id: <OF371A7885.A200B130-ON85258147.00567363-85258147.00569823@notes.na.collabserv.c>
Meeting minutes pasted below and at link:
http://www.w3.org/2017/06/22-lvtf-minutes.html
Low Vision Accessibility Task Force Teleconference
22 Jun 2017
See also: IRC log
Attendees
Present
Shawn, Erich, Jim, Laura, Scott, Wayne, SteveR, steverep
Regrets
Alastair, Glenda, John
Chair
jim
Scribe
erich
Contents
Topics
Recap of Discussion with Dr Arditi
remaining SCs
color
Summary of Action Items
Summary of Resolutions
<allanj> https://github.com/w3c/wcag21/issues/75#issuecomment-309306101
<allanj> Adapting Text (need CFC, need Color back in, and CFC)
<allanj> Reflow
<allanj> Popup Interference
<allanj> Printing
<scribe> Scribe: erich
<laura> Scribe list:
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Scribe_List
JA: Be sure to vote on the current CFC's if you haven't already
<laura>
https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2017Jun/0024.html
JA: Zoom Content, User Interface Contrast are included
<laura> Josh’s reply:
https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2017Jun/0029.html
<laura> So I asked Josh, Andrew, and Michael if we could have an Adapting
text CFC .
<laura> Josh replied: "This looks like it is good to go for a CFC" and
asked "Andrew - you think this is ok?"
<laura> Andrew has not replied. He is on vacation this week.
Recap of Discussion with Dr Arditi
<allanj> http://jov.arvojournals.org/article.aspx?articleid=2628138
JA: Dr. Arditi acknowledged great difficulties in low vision research
<allanj> http://www.ccsenet.org/journal/index.php/gjhs/article/view/67398
<allanj> close item 2
<allanj> close item 2
remaining SCs
<allanj> Adapting Text (need CFC, need Color back in, and CFC)
<allanj> Reflow
<allanj> Popup Interference
<allanj> Printing
<allanj> https://github.com/w3c/wcag21/issues/75#issuecomment-309306101
JA: Turning to Popup Interference next could work, as group suggests
<allanj> The inability to perceive content that appears on hover.
<allanj> Examples:
<allanj> (a) Tooltip obscured by enlarged pointer. Default position of
tooltip content created via the title attribute is below and right of the
trigger element. This positioning results in an enlarged mouse pointer
blocking all or part of the tooltip. Moving the mouse will cause the
tooltip to disappear. This issue is most impactful when the tooltip is the
only visual text label for a component.
<allanj> (b) Content disappears when mouse moves off trigger and moves on
to displayed content. This occurs for tooltips created using the title
attribute by default, but may also occur for larger containers of content
of text that are unintentionally triggered as a user navigates a page. This
issue can cause significant barriers for users who depend on screen
magnification where the zoom window is...
<allanj> ...dependent on mouse navigation. (The onmouseout event handler
can cause this issue).
<allanj> AND
<allanj> Content that appears on hover may block perception of triggered
content. (See screenshot).
<allanj> https://drive.google.com/open?id=0B6nh5-QGl_zLWUNvN1JJdXh1M28
<allanj> https://jsfiddle.net/obsqynyp/4/
<allanj> current SC wording
<allanj> For informational content that appears on hover or focus, one of
the following is true:
<allanj> Turn Off
<allanj> The informational content can be turned off
<allanj> Not obscure
<allanj> The informational content does not obsure the triggering content
<allanj> This does not apply to user agent rendering of the title
attribute.
<allanj> current issue https://github.com/w3c/wcag21/issues/75
<allanj> need more generic = info from title attribute
<allanj> perhaps "tooltip"
<allanj> from google - a message that appears when a cursor is positioned
over an icon, image, hyperlink, or other element in a graphical user
interface.
<allanj> erich - what about contrast of the tooltip
<allanj> jim: controllable by use
<allanj> jim: we need poistion, and not obscured by mouse pointer
<steverep> Regrets... I'm going to join the AG call since the speech input
(accessible name) SC has significant screen reader benefits
<laura> Informational content which appears on hover that is necessary for
understanding must:
<laura> * be fully visible,
<laura> * not obscured,
<laura> * be available on focus as well as hover, and
<laura> * be available via any input method.
<laura>
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/index.php?title=Metadata_On_Hover&oldid=2355
color
<allanj> color inversion
<allanj> high contrast
<allanj> low contrast - dim light
<allanj> black on white,
<allanj> white on black
<allanj> white or black on gray, or light gray on darker gray
Summary of Action Items
Summary of Resolutions
[End of minutes]
Erich Manser
IBM
Accessibility,
IBM Research
Littleton,
MA / tel:
978-696-1810
Search for
accessibility
answers
You don't need eyesight to have vision.
Attachments
- image/jpeg attachment: 5F499429.jpg
- image/jpeg attachment: 5F065590.jpg
- image/gif attachment: ecblank.gif
- image/gif attachment: 5F600198.gif
Received on Thursday, 22 June 2017 15:46:37 UTC