W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

08 Feb 2018

Attendees

Present
Erich, Jim, JohnRochford, Laura, ScottM, Shawn, Glenda
Regrets
Chair
Jim
Scribe
erich

Contents


<scott> I’m on the dreaded speakerphone this morning so I’m staying muted most of the time

<scribe> Scribe: erich

Magnified caption Files https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Feb/0009.html

<scott> this stuff is all covered in CVAA

JA: Caption attributes can be changed in YouTube. Wonder whether authors need to be testing with screen magnification

<jallan> Erich: for YouTube, if user can adjust then author testing with magnification is redundant

<scott> yes the text becomes pixelated

JR: How does the magnification of the captioning get checked for quality, such as pixelation? If authors do test with magnification, what can they then do about it?

SM: Most captioning systems will encode even the text, so that it will pixelate with magnification

JR: Closed Captioning and Embedded Captioning right in the video, not sure if there is any functional difference betwen the two when using magnification

JA: On YouTube, with separate caption track, there are settings for the caption so that I can dynamically change while the video is playing
... Consensus seems to be that they shouldn't do the statement that author needs to test

+1

<jallan> action jim to write to johnf about author not testing with screenmag for captions, refer to CVAA

<trackbot> Created ACTION-104 - Write to johnf about author not testing with screenmag for captions, refer to cvaa [on Jim Allan - due 2018-02-15].

<jallan> add name and date here - https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<jallan> specific needs for understanding (update here also)- https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Tracking_Implementation_Issues_(Understanding_Docs_updates)

JA: Would like people to sign up to review Understanding Docs. Even if no comments, just to review and state that.
... Target is to get these out the door by the end of February, next three weeks or so

GS: Glenda has reviewed non-text content

JR: Will do On Hover

Erich will do Reflow

JA: If we can have them done before next week, and message to the list, "here are my comments" or "I have no comments"
... Understanding Docs from first link from Jim above, also important to check second link above for any issues

<jallan> open item 2

<laura> My email on Non-text contrast understanding: https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Jan/0024.html

GS: Still trying to identify a good implementation example

JA: When you find a URL that passes, let's put it in here

<jallan> add urls for pass https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Implementations

<jallan> list of proposed techniques - https://www.w3.org/WAI/GL/wiki/Proposed_WCAG_2.1_SC_Techniques

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

JA: Texas School for the Blind website is a good reflow example

<laura> Makoto’s pages: https://github.com/w3c/wcag21/issues/677#issuecomment-358043678

JA: Still need On Hover and Non-Text Content implementation examples
... Will check with Steve about asking AG for help with On Hover and Non-Text Content implementation examples
... The other part of this is that we also need techniques

GS: Penn State has a possible example page with charts and graphs

<jallan> jim to work on Reflow Techniques

<JohnRochford> I have to go folks...

JA: Text Spacing, we are good on

<laura> Understanding Non-text Contrast is at: http://rawgit.com/alastc/wcag21/graphics-contrast-rename/understanding/21/non-text-contrast.html

JA: Non-Text Contrast link to understanding doc needs to be fixed

<alastairc> I'll put my version onto the main repo when the branches are sorted out.

<laura> bye

<jallan> trackbot, end meeting

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/02/08 16:55:46 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/Non-Text Content/Non-Text Contrast/
Default Present: Jim, Shawn, JohnR, ScottM, Laura, Erich, JohnRochford, Glenda
Present: Erich Jim JohnRochford Laura ScottM Shawn Glenda
Found Scribe: erich
Inferring ScribeNick: erich
Found Date: 08 Feb 2018
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]