W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

07 Feb 2019

Attendees

Present
Jim, Jason, Shawn, Laura, JonAvila, jon_avila
Regrets
Chair
jim
Scribe
Jim

Contents


close lvtf-ACTION-107

<trackbot> Closed lvtf-ACTION-107.

<scribe> scribe: Jim

open item 1

https://www.w3.org/TR/2019/CR-css-scroll-snap-1-20190131/

there are issues, but don't have any solutions

shawn: step one, make them aware of the issues

https://webdesign.tutsplus.com/tutorials/how-to-scroll-snap-using-css--cms-30333

<laura> File an issue: https://github.com/w3c/csswg-drafts/labels/css-scroll-snap-1

laura: file an issue on github

shawn: let them know asap, then fill in the details and explanation

<shawn> "This document will remain a Candidate Recommendation at least until 1 May 2019 in order to ensure the opportunity for wide review." gives some breathing room, yet still good to get it on their radar sooner rather than later

<scribe> ACTION: jim will work with jon to create problem statement for snap scroll

<trackbot> Created ACTION-108 - Will work with jon to create problem statement for snap scroll [on Jim Allan - due 2019-02-14].

<scribe> ACTION: jim to file an issue on snap scroll github

<trackbot> Created ACTION-109 - File an issue on snap scroll github [on Jim Allan - due 2019-02-14].

review new WG process https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process

WG is preceding with 2.2

<laura> [css-scroll-snap] More work needs to be done to address what happens when users with low vision zoom #3602: https://github.com/w3c/csswg-drafts/issues/3602

JonA: filed an issue on snap-scroll. Group said it was already covered.
... if zoomed in, you can scroll to bottom, then it will snap.
... would be good to have an accessibility note about issues

<laura> title attribute warning in html5: https://www.w3.org/TR/html/dom.html#the-title-attribute

jonA: the whole screen changes, loose context, and orientation

jim: can control the snapping with scroll bar but must hold the mouse button down on slider

jonA: possible style sheet override.

jim: need to test

laura: perhaps use 'prefers-reduced-motion' media query to stop snap scroll

jason: OS level control, to stop animation. perhaps have this apply in browser to stop snapping

laura: James Craig led the media query effort

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

back to new WG process

WG want the complete package - SC, Understanding, Testing before it goes in document

silver is 2-3 years out. perhaps work on silver and 2.2 simultaneously

proposed SC https://docs.google.com/spreadsheets/d/11IKqjRFvkRd2dAfUiyc5whhB3yIYXvSiirWct7KQIB0/edit#gid=0

Laura: what are our priorities for SCs

listing of LV SC

- visual affordance of focus and controls

- focus control (page refresh)

- Proximity of related information

no preference from group

jonA: proximity could be technique 3.3.2 (advisory), not sure if actual technique or place holder

perhaps affordance could be technique for 1.4.11

jim: thinks focus control is a SC candidate

time and effort - SC vs techniques/best practices

jonA: best practices are more approachable
... focus is difficult, because of the browser exemption.
... it is critical.
... put justification as techique for 1.4.8
... focus on mouse vs keyboard, turn off selectively. What is our stance on focus variability. This is from web incubator.

jim: related to hover focus issues.

jonA; another browser behavior issue.

<jon_avila> WICG concurrent focus discussion https://github.com/WICG/focus-visible/issues/128

RESOLUTION: LVTF prioritizes focus and control affordance to be a critice SC

trackbot, end meeting

Summary of Action Items

[NEW] ACTION: jim to file an issue on snap scroll github
[NEW] ACTION: jim will work with jon to create problem statement for snap scroll
 

Summary of Resolutions

  1. LVTF prioritizes focus and control affordance to be a critice SC
[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/02/07 16:57:45 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/to text/to test/
Default Present: Jim, Jason, Shawn, Laura, JonAvila, jon_avila
Present: Jim Jason Shawn Laura JonAvila jon_avila
No ScribeNick specified.  Guessing ScribeNick: JimA
Found Scribe: Jim

WARNING: Dash separator lines found.  If you intended them to mark
the start of a new topic, you need the -dashTopics option.
For example:
        <Philippe> ---
        <Philippe> Review of Action Items

Found Date: 07 Feb 2019
People with action items: jim jon will with work

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]