W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

09 Mar 2017

See also: IRC log

Attendees

Present
JohnRochford, Laura, shawn, Jim, Marla, Wayne, Scott, steverep
Regrets
Glenda
Chair
Jim
Scribe
Laura

Contents


<allanj> it is item 2

<scribe> Scribe: Laura

noto Sans font http://htmlpreview.github.io/?https://github.com/w3c/wai-website-design/blob/master/font-check.html

Jim: first public working draft is up.
... SC managers should expect lots of comments.

Shawn: wanted make sure people saw the email.
... low vision is at the top of criteria for new font for W3C site.

https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2017Mar/0004.html

<allanj> a related article - https://typography.guru/journal/letters-symbols-misrecognition/

plus ones from everyone.

Alexa/COGA - JohnR

john: https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2017Mar/0002.html
... thinking about interface for the bot.
... voice interface is a great interface for people with low vision.
... Alexa came up on the COGA call
... thought this group may be interested.

jim: is this just a voice interface?

JR: yes and no.
... interface must be usable by us.

scott: some variables in Alexa
... no sound feedback sometimes.
... different configurations.
... don't think there will be anything specific to us.

jim: john let us know if we can help you.

wayne: does it help you navigate a page?

JR: no.
... will let the group know how it goes.

User interface contrast - on hover or focus, is it covered?

<allanj> * the background color of the button changes so now the text on the button doesn't have sufficient contrast to be read any more

<allanj> * A symbol or image is on the button where mouse hover causes colors to change and once again there's not sufficient contrast to tell what the symbol is.

jim: comment from someone at IBM
... question on if this is covered by issue 10?

<allanj> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)

marla: think it covers all states.

wayne: that was my impression too.

Jim: will talk to glenda about it.

create LV tools page?

jim: we had a discussion on tools. may want to create a wiki page.

laura: sini created a page like that quite a while ago.

wayne: the should cover both tools and techniques.

Accessibility features for users with Low Vision: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Accessibility_features_for_users_with_Low_Vision

graphics contrast images

marla: collected a lot of images
... light gray close buttons. Back to top arrow. Gray pencil for editing. Do they apply?

Jim: yes

marla: social media icons is another example.

<allanj> the graying/dimming of the web

marla: would that apply?

Jim: i think so.

steve: agree

<shawn> s/low vision is at the top of criteria for new font for W3C site/low vision is in top criteria for new font for redesigned WAI site

<ScottM> they don’t want you to find it

jim: this brings up another instance: modal taking up whole screen.and a white X in far off location would be a good example.
... good to document these.

wayne: I’ve been collecting examples too.
... we should have a place to store them.
... a wiki section for our gallery.

jim: is there a better tool?

marla: google drive folder.
... drop box.
... drive may have a way to add a text description.

JR: flickr private group.

shawn: wiki

jim: I can facilitate adding them to the wiki.

wayne: I can help.

laura: I can help too.

<allanj> close item 6

linearization is up next on the WCAG WG survey.

"support" vs "a mechanism exists" or other wording

<allanj> https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JanMar/1142.html

Laura: I agree whole hardily with the concept. But the word "support" by itself is ambiguous. I don't think it would clarify.

Steve: 2 separate issues. The word “support” is ambigous.
... don’t agree with taking out the word "mechanism"

<Wayne> +1

<allanj> +1

jim: been updating the SC on the wiki but not everything.
... metadata on hover on in particular.
... it will be the foundation of the understanding document.
... take an action clean them up.
... anything else?

Shawn: start working on techniques.

<allanj> Topics: Techniques

<Wayne> Can we look at meta data next time?

<allanj> Jim will find technique template and send to list.

https://www.w3.org/WAI/GL/wiki/Technique_Template

https://www.w3.org/WAI/GL/wiki/Technique_Instructions

https://www.w3.org/WAI/GL/wiki/Writing_WCAG_Techniques_-_Notes

<ScottM> bye bye

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/03/09 16:58:08 $

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)

FAILED: s/low vision is at the top of criteria for new font for W3C site/low vision is in top criteria for new font for redesigned WAI site/
Succeeded: s/Greatings from northern virginia aka dc//
Succeeded: s/plus ones form everyone./plus ones from everyone./
Present: JohnRochford Laura shawn Jim Marla Wayne Scott steverep
Regrets: Glenda
Found Scribe: Laura
Inferring ScribeNick: laura
Found Date: 09 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/09-lvtf-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]