W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

27 Oct 2016

See also: IRC log

Attendees

Present
Shawn, Wayne, Glenda, JohnR, Scott, AWK, JohnRochford
Regrets
Chair
Andrew
Scribe
Wayne

Contents


<shawn> scribe: Wayne

<AWK> +AWK

<AWK> Chair: AWK

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Tracking_Success_Criteria_Progress

Glenda: Has been working on contrast for interactive images.

Andrew: On hover, On Mouse over will it work on mobile. Have information but not technology specific.

Glenda: The word hover is mouse independent term. Phones have a gesture for hover, or close contact.

Andrew: We make sure to look into more.

<AWK> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover

<ScottM> +q

ScottM: The problem is that things like tooltips hides the content. The tooltip hides what you need.

Andrew: We have a short name metadata. That talks about the problem in reverse. You don't want previously visible content hidden by tooltips.

<AWK> Current SC text: Hidden content that is necessary for understanding is available using any available input method

JohnR: We want to rewrite the content so that it blocks obscuring.

Glenda: When you land on a tootip it obscures the target of the landing.

JohnR: Suggensts: Information when apparent via hover, does not obscure underlying content.

Glenda: Two cases the content obscures content

Andrew: The pointer icon seems to be an icon issue, and it is out of scope for 2.1

Wayne: Content that becomes visible on hover, does not obscure target content

<AWK> Content that is presented visually in response to pointer events may not obscure other information unless the user is able to [something]

<JohnRochford_> Just changed it to "Content that appears on hover should not obscure the triggering element."

Andrew: We need an escape clause. When the user can avoid it...

<Glenda> Here is a sample page from UMN on obscured tooltips http://www.d.umn.edu/~lcarlson/wcagwg/obscured_tooltip_on_hover/test.html

Andrew: We do not want prevent the hover events altogether we need specific cases that can be referenced.

ScottM: Focus tracking is a problem.

<AWK> In Safari on Mac it looks like the the browser tooltip is based on the a set distance from the pointer "point" and doesn't acknowledge the change in icon size

JohnR: Thinks that element is more approprriante.

<JohnRochford_> Statement now is "Content that appears on hover should not obscure the triggering element or other content."

Group: We will clip some examples of the problem.

<AWK> Wayne and others will find examples of tooltips and other hovering content interfering with operation of links/controls

RESOLUTION: Need more information and examples on https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover to hone the SC text.

Reflow test case

<AWK> Wayne: Goal is to get a list of the elements in the correct reading order so they can be put into a single column if desired

<JohnRochford_> Wayne: (About reflow) Can we get a listing of elements so we can change reading order?

<AWK> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Reflow_to_Single_Column

<AWK> AWK and Glenda seeing differences in Mac/Chrome

<AWK> Need to figure out if this fails 1.3.2 or if we need something new in WCAG 2.1

<AWK> Need to get some clarification from Alastair

<JohnRochford_> Gotta go, folks.

<AWK> related WCAG issue: https://github.com/w3c/wcag/issues/83 (was closed due to no one engaging on it)

Pre element

<AWK> reading code examples written with pre element is very hard

<AWK> pre causes problems with wrapping

<AWK> one solution is to have people use the code element

<AWK> AWK: perhaps this is a 1.3.1 issue and we need a technique?

<Glenda> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_%28Minimum%29

Interactive element contrast minimum

Glenda: We look at interactive element contrast minimum
...: How do I make this testable? Add to 1.4.3. It would be better add a new criterion.

<AWK> The visual presentation of important (non-text) information in an interactive image has a contrast ratio of at least 4.5:1.

<AWK> The visual presentation of form field borders, focus indicators, and selected indicators has a contrast ratio of at least 4.5:1, except for the following:

Glenda: Focus indicators etc. should have 4.5:1 or 3:1 as appropriate according to size.
... For exampe 3px is wider than 18pt stroke.

AWK: Input for no border. You need to have some border on controls. Complaint: when the fields are invisible.

present

RESOLUTION: Glenda to integrate a few more comments, e.g. a requirement for an apparent border

<AWK> Trackbot, end meeting

Summary of Action Items

Summary of Resolutions

  1. Need more information and examples on https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover to hone the SC text.
  2. Glenda to integrate a few more comments, e.g. a requirement for an apparent border
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/10/27 16:36:39 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Wayne
Inferring ScribeNick: Wayne
Default Present: Shawn, Wayne, Glenda, JohnR, Scott, AndrewAWK, AWK, JohnRochford
Present: Shawn Wayne Glenda JohnR Scott AWK JohnRochford
Found Date: 27 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/27-lvtf-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]