LVTF Meeting Minutes - 10/26/17

Minutes pasted below and at link:
http://www.w3.org/2017/10/26-lvtf-minutes.html


Low Vision Accessibility Task Force Teleconference
26 Oct 2017


See also: IRC log


Attendees
Present
      Shawn, Jim, JohnRochford, ScottM, Erich, Laura, SteveRep, steve
Regrets
      Glenda, Alastair
Chair
      SV_MEETING_CHAIR
Scribe
      erich
Contents
      Topics
            techniques for 1.4.10, 1.4.13, 1.4.14
            Review Hover Understanding
            techniques for 1.4.10, 1.4.13, 1.4.14
      Summary of Action Items
      Summary of Resolutions



<allanj>
http://blog.freedomscientific.com/2017/10/25/important-information-for-users-of-mozilla-firefox/



<shawn> :-)


test


<scribe> Scribe: erich


techniques for 1.4.10, 1.4.13, 1.4.14


<laura> Proposed WCAG 2.1 SC Techniques:
https://www.w3.org/WAI/GL/wiki/Proposed_WCAG_2.1_SC_Techniques



<laura> Allowing for Spacing Override:
https://www.w3.org/WAI/GL/wiki/Allowing_for_Spacing_Override



<allanj> Jim will add review techniques to next week agenda


Review Hover Understanding


<laura> Understanding Content on Hover or Focus:
https://rawgit.com/w3c/wcag21/content-on-hover-or-focus/understanding/21/content-on-hover-or-focus.html



<laura> All of the understanding docs are linked from:
https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC



SR: I broke up the 3 different conditions. SC has morphed from original.
... Components portion was removed, seemingly for overlap with 2.1.1
... Would like to propose a change to make things clearer
... Second bullet about Hover can stay the same, but would propose changing
to make the new content Hoverable
... Also on last bullet, propose removing bit about focus and make it about
persistence to reduce overlap with 2.1.1


JA: Suggests adding pictures


SR: Plans to use tool-tip example and another example with larger target
and other with content over the top of it


<allanj>
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover



<allanj>
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover#Div_on_Hover_Obscuring_Content_Example



JA: any specific websites as bad examples?


SR: Suggests gmail as possible example of tooltips that are not hoverable


JA: Suggests taking offline following the AG call


<allanj> jim - review Understanding Hover next week


techniques for 1.4.10, 1.4.13, 1.4.14


<allanj> close item 1


<allanj> close item 2


<allanj> At least 5 conforming Web sites 1 are available, of which


<allanj> At least four conform at level AA,


<allanj> At least one conforms at level AAA


JA: For conformance testing, AG would like at least 5 conforming websites,
of which 4 are AA and at least 1 AAA
... Anyone know of any AAA conformant websites?


LC: Lainey Feingold's website


<shawn> AAA http://www.lflegal.com/



<allanj> At least two implementations 2 exist for each success criterion
added in WCAG 2.1 (Success Criteria from WCAG 2.0 do not need new
implementations);


<allanj> Accessibility support documentation for SC with platform/user
agent/assistive technology dependencies is available for at least two
technologies with at least four platforms (operating system/user
agent/assistive technology combinations


JA: Wonder if SVG counts, or considered part of HTML


<laura> CR Exit Criteria from Tuesday’s AG meeting:
https://www.w3.org/2017/10/24-ag-minutes.html#item05



<allanj> All sufficient techniques listed in Understanding WCAG 2.0 at the
end of the Candidate Recommendation period contain test procedures


<laura> https://www.w3.org/WAI/GL/wiki/Allowing_for_Spacing_Override



<laura> https://www.w3.org/WAI/GL/wiki/Allowing_for_Spacing_Override#Tests



<allanj> The Working Group has responded formally to all issues raised
against this document related to any implementation efforts during the
Candidate Recommendation period.


<laura> Open 2.1 GitHub Issues Labeled "LVTF”:
https://github.com/w3c/wcag21/labels/LVTF



JA: AG group has been voting on proposed responses, I will include some in
next week's agenda
... Who will be at TPAC?


<allanj> Shawn, Scott, Glenda, Alastair


SM: I may go, believe it's in San Francisco


JA: Glenda and Alastair will go


SR: Will join virtually as much as I can


LC: Same for me


<allanj> there will also be phone bridge available. Jim, Laura, Steve on
phone


<allanj> http://www.tsbvi.edu/understanding%20zoom.html



JA: Would like to emphasize the evils of horizontal scrolling in the intent


<allanj> make sure Wayne;s article is in the resources section


JA: I added another picture and may include some of Wayne's graphics in
there to help illustrate
... Are there other features others can think of to help illustrate for
Zoom Content?
... Unable to locate any comparison numbers on low-vision magnification vs.
screen-reader users


<shawn> Scrolling http://www.tader.info/scrolling.html To see Comments,
click the "Show" button


<shawn> "I am currently using Zoomtext at 4x magnification and moving the
screen back and forth to read a long sentence makes me nauseous/sea-sick."


<shawn> "Magnification disorients me and makes it worse. I use very large
print and zoom in with web browsers instead."


<shawn> How important is it to be able to change the following:... No
horizontal scrolling -- Very important 65%; Important 22%


<shawn> "People who use screen magnification I've user-tested sites with
have been very much hindered by having to horizontally scroll in magnified
views"


<allanj> caveat web aim demographics not representative to VI
population ... WHO data


JA: Ending to go to AG meeting. Will have Steve and Understanding Zoom on
agenda for next week


<laura> bye


Summary of Action Items
Summary of Resolutions
[End of minutes]
                                                                                        
                    Erich Manser                                                        
                    IBM                                                                 
                    Accessibility,                                                      
                    IBM Research                                                        
                    Littleton,                                                          
                    MA / tel:                                                           
                    978-696-1810                                                        
                    Search for                                                          
                    accessibility                                                       
                    answers                                                             
                                                                                        
                                                                                        
                                                                                        
                                                                                        
                                                                                        
                                                                                        
                                                                                        



You don't need eyesight to have vision.