W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

05 Sep 2019

Attendees

Present
jim, wayne, Jon, Laura, Alastair
Regrets
Chair
SV_MEETING_CHAIR
Scribe
jim

Contents


https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2019Aug/0015.html

<laura> Waynes’ example: https://lists.w3.org/Archives/Public/w3c-wai-gl/2019JulSep/0177.html

<scribe> scribe: jim

focus visible - review on 2.2

https://www.tsbvi.edu/web/tests/focus-more-visible3.html

<alastairc> https://alastairc.uk/tests/wcag22-examples/focus-more-visible-2.html

<alastairc> Spreadsheet: https://docs.google.com/spreadsheets/d/1WBUakVVdJh2alhSpacgUekEQL8HFMK9oMeq6IswdZVw/edit#gid=0

ac: 3 ways to measure focus style. Things changing - borders, outlines,
... adjacent colors. SC main point is about pixels changing and the contrast between changes.
... Andy's email. a scale, can have a 1px border if very contrasty >7
... looking for a score of 1-10.

jon: thought 1.4.11 applied to focus. want to discuss.

<alastairc> Focus (more) visible draft: https://docs.google.com/document/d/1g9_WBgfhViWAaRFIWWt10CP5rBsEVIWm3vT1vWqrHvI/edit?ts=5d124fb5#

ac: current nontext contrast covered contrast in states - radio buttons. focus state indocator does not necessarily need to differentiate.

jon: thought focus state indicator had to have a 3:1,

ac: most think focus state has to have contrast.

jon: not original intent of 1.4.11

ac: 1.4.11 was morfed. the new SC should fix the dynamic state of focus.

jon: disappointed that what LVTF wanted didn't get addressed. 1.4.11 does very little for focus.

ac: we use 1.4.11 for input controls and iconography. focus is covered in best practices

jon: bigger challenge for users is finding focus.

<alastairc> Example 1:

scale of 1-10 - 10 very visible, 1 hardly visible

<alastairc> https://alastairc.uk/tests/wcag22-examples/focus-more-visible-2.html

jon: not talking about the 2 button issues. how to know which button has focus

ac: just looking at visibility of focus
... all examples have 4 buttons to check as focus moves

jon: comparison with adjacent controls

ac: example 3 has contrast with dark border, but not background.

jon: if it was thicker would not be so much of an issue, or both colors

example 5 - looks pressed not focused.

Jon: example 6 having a border overcomes usability issue

<jon_avila> looks like I got kicked off. But I have to run to another meeting. Thanks. 15d seems like it fails the SC due not being the longest side to me.

<alastairc> Ok, thanks Jon. 15d does have sufficient *area*

<alastairc> which is what the SC is asking for..

<laura> need to drop off now. Bye.

wayne: need research on visual perception, gestalt or preattentive vision, completion principle

<laura> Wonder if we can we correlate LVTF assessed values in the spreadsheet to letter grades?

<laura> https://en.wikipedia.org/wiki/Academic_grading_in_the_United_States

laura - or make it a smaller scale for forced choice.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/09/05 16:19:42 $

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/though 1/thought 1/
Succeeded: s/force/forced/
Present: jim wayne Jon Laura Alastair
No ScribeNick specified.  Guessing ScribeNick: JimA
Found Scribe: jim

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 05 Sep 2019
People with action items: 

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]