View source for CSUN 2017 LVTF Update Presentation

== W3C Low Vision Task Force CSUN 2017 Update ==

===Low Vision Folks===
* Jim Allan - LVTF Chair (TSBVI)
* Wayne Dick - Knowbility
* Shawn Henry - W3C & TAdER.info
* Glenda Sims - Deque

===Why did you volunteer to work on the Low Vision Task Force (LVTF)?===

===What are the goals of the Low Vision Task Force (LVTF)?===

    * Document accessibility requirements/needs for people with low vision
    * Identify gaps between user needs and existing requirements in WCAG, UAAG, ATAG
    * Document sufficient techniques, advisory techniques, and failures for WCAG 2.0 related to low vision
    * Develop an extension to WCAG 2.0 to address low vision
    * Refine user agent use cases for low vision, as needed
    * Develop support materials to explain the issues and implementation of the above resources effectively

===How can people learn more about the needs of low vision users?===

* [https://www.w3.org/TR/low-vision-needs/ Accessibility Requirements for People with Low vision]
* [http://www.tader.info Text Adaptability is Essential for Reading]

===What are the proposed new low vision success criteria for WCAG 2.1 in the First Public Working Draft?===
====Low Vision SC for WCAG 2.1====

1.4.10 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Reflow_to_Single_Column Linearization]

1.4.11 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements Resize content]  

1.4.12 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Graphics_Contrast Graphics Contrast] 

1.4.13 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Printing_Customized_Text Printing Customized Text]

1.4.14 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User%20Interface%20Component%20Contrast%20(Minimum) User Interface Component Contrast]

1.4.15 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Spacing Adapting Text]

1.4.16 [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover Popup Interference]

[https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html WCAG 2.1 First Public Working Draft]

===Why do we need linearization?===
Because every person with low vision has tunnel vision on the web.

===How does resizing help?===

===What is the problem with horizontal scrolling?===

89 Scrolls to Read this page! 
Scrolls Needed to Read 48 Lines of Text in Full Screen View

Data From: [http://nosetothepage.org/Fitz/2dScroll.html Operational Overhead of Horizontal Scrolling] by Dr. Wayne Dick 

===How does personalization factor into solving even more low vision barriers?===

===What low vision tools and/or techniques do you suggest to help people today?===

===Why should YOU care about low vision?===
Visual Impairments & Blindness Worldwide
* 285 million people  visually impaired
* 39 million people blind
* 246 million people low vision
* 14% blind
* 86% low vision
Source: [http://www.who.int/mediacentre/factsheets/fs282/en/ World Health Org Fact Sheet]
===What can YOU do to help remove low vision accessibility barriers?===

Low Vision Now!

* Attend TRX: Custom Text for You
** Today at 4:20pm in Balboa AB
* [https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html Review/comment & support new WCAG 2.1 SC]
* [https://www.w3.org/TR/low-vision-needs/ Read/understand Accessibility Requirements for People with Low Vision]
* Volunteer to help with the LVTF
* Participate in Low Vision Research

Get Your Typographic Prescription (TRx)
* What is YOUR custom profile for low vision reading?
* Get your TRx & help us with research
* The TRx Profile will help you choose your ideal
** Font Family
** Foreground / Background Color
** Size
** Letter Spacing
** Word Spacing
** Line Spacing
The time to solve low vision accessibility barriers is
NOW!

Questions ?