Agenda: Low Vision Task Force Telecon 2 Dec 2015

Please join the call before 10:30. We will start at 10:30

Agenda+ scribe

Agenda+ Framework for requirements document
   Current Requirements document has 7 sections. Overview document has 4
categories. Need to merge the two documents.  Modify the Requirements to
have 4 categories, or change the Overview to have 7, or find some happy
medium.

Agenda+ Laura's sectional summaries
     https://github.com/w3c/low-vision-a11y-tf/issues/2

Agenda+ gather example images or online simulators for requirements as
necessary.

Agenda+ Review questions posed in Yellow Notes sections. They need to be
addressed.

Agenda+ Ontology update (wayne)

----

Teleconference Day and Time:
Wednesdays at 10:30AM, Eastern US time (GMT -4 14:30).

IRC channel: irc.w3.org:6665/  #lvtf

Attendance Survey:  https://www.w3.org/2002/09/wbs/81151/LVTF-telecons/

WebEx call you Meeting Link:
https://mit.webex.com/mit/j.php?MTID=m2486867b0c5117ca58dffc7aee66ca29
Mobile Auto Dial:+1-617-324-0000,,,644115262#

Call-in: WebEx bridge at: +1-617-324-0000 US Toll Number
SIP: zakim@voip.w3.org
Code:  644 111 262

Requirements document -
http://w3c.github.io/low-vision-a11y-tf/requirements.html
Requirements (editable) - https://github.com/w3c/low-vision-a11y-tf
------

1. Overview needs work. There is a rough version in the Wiki -
http://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Overview_of_Low_Vision
 - point to ontology (wayne)

2, Merge the requirements into the framework in the Overview

3. Sectional overviews (7 of them) - need 1-2 sentences for each section.
The sectional overviews may be combined in larger overveiw later (or not),
but it is important to capture terse statements for each section.

4. Review questions posed in Yellow Notes sections. They need to be
addressed. Propose answers to the list for discussion.

5. Critical review of requirements. Have we covered all aspects of a
requirement. For example, 'luminance overall' description talks about
brightness being too high. For some, brightness can be too low. This needs
to be mentioned either in the requirement or the description above it.

6. Need a mapping of requirements to visual conditions and the reverse.
Could also modify the column 'Educational Considerations' to be 'Web
considerations' or 'Accessibility Consideration' or something and focus
only on web/'electronic information' related accessibility considerations
http://www.tsbvi.edu/eye-conditions

7. link or cross reference requirements to Mobile & Cognitive taskforce docs
 Mobile - http://w3c.github.io/Mobile-A11y-TF-Note/
 Cognitive - https://rawgit.com/w3c/coga/master/techniques/index.html (there
may be a better document, I couldn't find it)

8. link requirements to WCAG http://www.w3.org/tr/wcag20

9. Some requirements would benefit from image ( such as the ones in 2.3.3)
or some simulator to illustrate the point. Please gather them and send to
list.





-- 
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.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964