Minutes: Low Vision Task Force 14 Feb 2019

https://www.w3.org/2019/02/14-lvtf-minutes.html

Low Vision Accessibility Task Force Teleconference14 Feb 2019Attendees
PresentJim, Wayne, Shawn, JoAnne, SteveRepsherRegretsJason, LauraChairjim
ScribeJim
Contents

   - Topics <https://www.w3.org/2019/02/14-lvtf-minutes.html#agenda>
      1. "Supplemental Guidance"
      <https://www.w3.org/2019/02/14-lvtf-minutes.html#item01>
   - Summary of Action Items
   <https://www.w3.org/2019/02/14-lvtf-minutes.html#ActionSummary>
   - Summary of Resolutions
   <https://www.w3.org/2019/02/14-lvtf-minutes.html#ResolutionSummary>

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

<shawn> http://www.uiaccess.com/embracing-carrots.html

<scribe> scribe: Jim

<shawn> Welcome to JoAnne!

jj: working on Low Vision with SalesForce, previous work in higher ed

<shawn> others: https://www.w3.org/2000/09/dbwg/details?group=81151&public=1

Open item 1

close item 1
"Supplemental Guidance"

shawn: WCAG 2.1 is out, but taskforces wanted additional information
"supplemental guidance"
... things you should do.

jim: best practices

shawn: perhaps LVTF should have something that looks like understanding and
techniques, clearly marked as supplemental (or whatever we call it).
... with information about what is required and what else is necessary

wd: is this like a spreadsheet

shawn: it would include things that were not in WCAG2.1.

+1 to 'supplemental guidance'

shawn: not separate guidance documents for all taskforces, but an
integrated package of techniques and guidance
... E&O to do design, taskforces to provide content.

jim: AG getting very busy with 2.2

shawn: what is LV thinking about 2.2
... ideally, better to clearly document what people should do

wayne: if we get best practices published, support people with low vision
in a techniquey way

open item 2

shawn: use Understanding and techniques format. add additional stuff that
folks should do.

<shawn> Jim: ... Note...

shawn: what is perception of TR space vs other space

<shawn> Shawn: Thoughts about the additional guidance integrated with
Understanding and Techniques package vs. nNote.

https://wai-wcag-quickref.netlify.com/

<shawn> Jim: Integrating them would be great

+1 best practices integration with techniques

shawn: want to make things easy to find and use
... AG will approve everything. and its not normative. it is infomative!!

<shawn> Shawn: can use simplier wording! not need to be convoluted for
testability, exceptions, etc

jj: best practices would be really useful, use in specific ways,
incorporate into corporate best practices

<shawn> JoAnne: We could use for our internal guidance

sr: agree with best practices

possible SC: proximity of realated info, full justification, visual
affordance - , page refresh

<shawn> Jim: Put effort on these? Or put effort in techniques and best
practices?

sr: LVTF would cover the interactive forms proposal - if make a form, make
it interactive rather than printable (mostly PDF issue)

jim: seems like a technique. but there is no SC to attach it to

shawn: seems a best practice.

<steverep> Found it...
https://www.w3.org/WAI/GL/wiki/Potential_Accessibility_Guidelines

shawn: justification is good and important. is it better at as a best
practice.
... perhaps add whether something is easy/hard

wd: problem with justification is not usually done well. journal usually do
it quite well. most folks just left justify. still some bad web based full
justification

jj: have guidelines, and component library to build products. best
practices would be very helpful. try to build practices and guidelines in
to components

<shawn> ... broader guidance that we can incorporate specifically

jj: engineers concerned with what, how, and why

shawn: so which proposed SCs do we want to do? or put in supplemental
guiance

wayne: like supplemental guidance. fit into silver better. got lots of
essential stuff into 2.1.

<shawn> WD: Also will help with Silver. We got some good things in 2.1.
Let's focus on what we need for Silver. e.g., personalization

jim: collaborate with other TF on SC (proximity & affordance)

shawn: or just create 'best practice' on these items as examples to follow.
... create an understanding document, one for each best practice, then show
to AG and see if it makes sense to develop into an SC or a SG/BP
(supplemental guidance / best practice)

wayne: want a better format, so users of materials can get to content
easily. make it user friendly

jj: add examples.

jim: put preliminary documents in wiki

<shawn>
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page#Meeting_Schedule

trackbot, end meeting

Note: no meeting 28 Feb 2019
Summary of Action ItemsSummary 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