Minutes: Low Vision Task Force 31 Jan 2019

source: https://www.w3.org/2019/01/31-lvtf-minutes.html
<https://www.w3.org/2019/01/31-lvtf-minutes.html>

Low Vision Accessibility Task Force Teleconference31 Jan 2019Attendees
PresentJim, Wayne, SteveRepsherRegretslauara, shawn, jasonChair
SV_MEETING_CHAIRScribeAllanJ
Contents

   - Topics <https://www.w3.org/2019/01/31-lvtf-minutes.html#agenda>
   - Summary of Action Items
   <https://www.w3.org/2019/01/31-lvtf-minutes.html#ActionSummary>
   - Summary of Resolutions
   <https://www.w3.org/2019/01/31-lvtf-minutes.html#ResolutionSummary>

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

open item 3

jim: conflation of touch separatiohn is different from visual separation

wd: buttons with good borders have no spacing separation but have visual
separation and you know they are two different buttons.

sr: its complicated.

mobile question: How many pixels in between 2 active elements on a screen
meets user need on the low-vision side? Mobile TF have it at two pixels.

wd: tends to agree, because pinch zoom make space bigger

sr: agree with wayne. depends on visual affordances on the buttons
themselves - borders, boundaries, contrast. etc
... should base it only on touch.

wd: button with wide bevels are easy to see, or inset/outset are easy to see

sr: shadows make a big difference.

jim: seems wrong to specify 2 px of background color between active
elements.

sr: very complicated visually - color, contrast, borders, boundaries,
bevels, inset/outset and combintations

s/copmbintations/combinations

wd: need something about inactive area, "effective separation"

<scribe> *ACTION:* jim to write mobile about "effective separation" -
explain combinatorics for separation

<trackbot> Created ACTION-107 - Write mobile about "effective separation" -
explain combinatorics for separation [on Jim Allan - due 2019-02-07].

close item 3

open item 2

jim: need people and time

wd: have biggest cell phone and still listen alot.

Jim will talk with mobile about working together.

wd: Needs help with <pre> text. what format actually needs to be visually
formatted with <pre>. Calls out 'code'. its just easier.
... e e cumming Falling Leaf, Buffalo bill.
... there are neccessary and unnecessary uses of <pre> ... needs example to
classify.

jim: elementary math, chemistry, ascii art.
... send a request to IG list or WebAIM for <pre> examples

close item 2

open item 1

https://docs.google.com/spreadsheets/d/1gwp30K0OJ46mtjKCwo__cCIHn6mgTl-fvn2A_ADzwEc/edit#gid=0

jim: overview.

sr: page refresh should be a failure technique for 2.2.4
... proximity of related information - can't think what it is a failure for.

wd: color is very difficult. spacing works ok.

sr: menu, arrow is only actionable item to expand a menu item is an issue

<wayne> https://github.com/w3c/wcag/upload/master

<wayne> div { background-color: black !important; color: white !important; }

<steverep> Regarding tiny triangles for accordions or "required" off in
noman's land, see my proposal for target size -
https://github.com/w3c/wcag21/issues/60#issuecomment-302480005

jim: these seem more "functional affordance" rather than "visual affordance"

trackbot, end meeting
Summary of Action Items*[NEW]* *ACTION:* jim to write mobile about
"effective separation" - explain combinatorics for separation

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