LVTF Meeting Minutes - April 20, 2017

Minutes are at following link, and pasted below:
http://www.w3.org/2017/04/20-lvtf-minutes.html


Low Vision Accessibility Task Force Teleconference
20 Apr 2017


See also: IRC log


Attendees
Present
      allanj, steverep, AlastairC, JohnR, Laura, Shawn, Marla, ScottM,
      Wayne, Glenda, erich
Regrets
Chair
      SV_MEETING_CHAIR
Scribe
      Jim, erich
Contents
      Topics
            reminder Joint LVTF & COGA call Mon 24 April. Topic:
            personalization
      Summary of Action Items
      Summary of Resolutions



<allanj> scribe: Jim


reminder Joint LVTF & COGA call Mon 24 April. Topic: personalization


<allanj> COGA call 12 EST, 11CST


<allanj> open item 3


<Wayne> http://nosetothepage.org/FontTst.html



<erich> +1


<allanj> jim: perhaps we leave fonts out, to get the


<Wayne> +1


<allanj> ... SC in the document.


<erich> Scribe: erich


<Zakim> steverep, you wanted to suggest we try to come together on
technology support wording


<shawn> +1 for not supporting giving a pass for technologies that don't
support it !


SR: Claim is if technology can support user styles than the SC is a pass,
and I have concerns with that


LC: We've had it both ways, that wording was insisted upon over the weekend


WD: I interpret it as if you are working with technology that has support
for some browsers, than every single browser for which it has support has
to work
... This does not deal with technologies for which there are no browsers
that support
... Earlier approach was that if it was not allowed on one agent, then we
couldn't require it on others


SR: Notes distinction between user agent support vs. technology support,
sees that as the issue


<Glenda> 4. Only Accessibility-Supported Ways of Using Technologies: Only
accessibility-supported ways of using technologies are relied upon to
satisfy the success criteria. Any information or functionality that is
provided in a way that is not accessibility supported is also available in
a way that is accessibility supported. (See Understanding accessibility
support.)


<allanj>
https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head



<Glenda> https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html



<laura> Hi Gregg:
https://lists.w3.org/Archives/Public/w3c-wai-gl/2017AprJun/0196.html



AC: He talks about major web technologies, to which we could add


SR: Big difference is we're giving a blanket pass with no stipulations
behind it


JA: We have 13 versions of wording nobody can agree on


<laura> Proposal L text:
https://www.w3.org/WAI/GL/wiki/Issue_78_Options#Proposal_L_text_reads:



JA: We want the want that talks about accessibility supported, and leaves
out the technology stuff
... No matter what we say about the Fonts, until we get some metric, it's
just going to spin


<Glenda> My vote: Go with “L” version. Dropping font for now (to get this
SC in).


AC: Do we need to worry about spacing issues caused by replacing fonts?


+1 to Glenda


<laura> Up the spacing?


AC: If people have to leave a certain spacing around text, does it matter
why?


<steverep> How about: No loss of content or functionality occurs when a
user agent.... (Proposal D but replace mechanism with user agent), then use
the bullets of J minus font for now


<JohnRochford> Dropping off now to attend a COGA call.


<JohnRochford> JohnRochford present+


WD: verbalizing potential metric formulation


<Glenda> I love this direction. Let’s leave font off…and see how far this
SC can take us! It will sure be a step forward.


+1 font off (for now)


<laura> WebAIM Feedback: “The variations introduced by font family
customization are, we believe, adequately covered by the manipulation of
line, letter, and word spacing.”


<laura> https://github.com/w3c/wcag21/issues/254



<allanj> adapting text just changed -
https://github.com/w3c/wcag21/pull/288/files



moving over to AG call


<Wayne> quit


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.