Silver Community Group Teleconference

06 Sep 2019


jeanne, janina, Chuck, AngelaAccessForAll, shari, CharlesHall, pkorn, KimD


TPAC F2F questions or details?

<scribe> scribe: janina

jeanne: Remote participation via Webex is confirmed

<jeanne> details page https://www.w3.org/WAI/GL/task-forces/silver/wiki/2019_September_16-20_in_Fukuoka,_Japan

jeanne: Note these include EDT as well as JST times
... Also linked to TimeAndDate.com
... Working on joint meetings, but nothing yet confirmed

Instructions for Github issues from Leonie Watson

jeanne: Notes Leonie's cheat sheet for using github via email
... This is as an alternative to using a browser to interface with github
... Would anyone like to review these now?


jeanne: These instructions are now linked in the "How to participate" section of our wiki

<jeanne> HOw do I? folder https://drive.google.com/drive/folders/1zZUo3rsGlffzAOPTzJ3x587odLpC0pbi

jeanne: Offering to help anyone who needs help getting up to speed using github

Writing functional needs - language pattern for Style Guide

<AngelaAccessForAll> Yes!

<AngelaAccessForAll> Still unable to speak :)

jeanne: Angela headed the group working on plain language prototype
... Developed a style guide
... Question is whether to agree on a pattern for functional needs
... I and Angela looked at how different people drafted these, and have a suggestion ...

<jeanne> https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.fd17rscqblnm -> heading on styles for functional needs

jeanne: Avoiding using names of disabilities except as an example
... Avoiding naming solutions or approaches
... However, I am uncomfortable not mentioning a disability at all

<jeanne> Usage [with/without/who can/cannot] [action or function] due to: human factors (like [example]); technical factors (like [example]); or contextual factors (like [example])

jeanne: Cons are that who's impacted isn't necessarily mentioned, nor is it plain language
... Also there's concern to have complete sentences

<AngelaAccessForAll> Oops--I cut and pasted one too many times. :)

jeanne: We liked starting with "People" rather than with "Usage ..."
... So, any discussion of the proposal??

<jeanne> People [with/without/who can/cannot] [action or function] due to: human factors (like [example of disability]); technical factors (like [example]); or contextual factors (like [example])

chuck: I don't know what my comments are until I try using this with some of my items

kim: Expresses approval for looking at this

<KimD> +1 to being systematic

<KimD> +1 to keeping real people examples

janina: Suggests talking about pwds has been powerful, and we should preserve the user story

jeanne: Agree with revisiting after we've expirimented with this approach

charles: What is "people" replacing? Just the "usage?" Or also the "pwd example"
... so how does this work for multiple disabilities?
... Is there a quantifiable limit to the number of examples? Or open ended so long as relevant?

jeanne: Understand that a longer list of examples seems to identify who's not on the list

charles: I'm OK if we're in agreement thqt examples are only exemplary, and not intended to be comprehensive
... e.g. we would not include pain?

jeanne: Don't see why we don't include those.

<AngelaAccessForAll> I believe we should include issues like pain; it's like age.

jeanne: It was transofmative for me to learn that older people lose color discrimination

janina: I learned in writing the CAPTCHA doc that many seniors lose the ability to use fingerprint sensors
... their fingerprints just don't register

Instructions for Github issues from Leonie Watson

Continue Functional Needs discussion

jeanne: Anyone with something to report today?


<jeanne> https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.8ioplsj35s7t

jeanne: That sr users aren't interupted by other sounds
... add users can not be distracted

janina: Suggests we have a best practice of identifying which function/app is using what sonicon to mean what notification

jeanne: Confirms that ADD use case is that audio disrupts visual comprehension

<pkorn> My audio seems to have gone away (microphone)

<pkorn> I can still hear...

<pkorn> Rats, I have a comment. Will drop and re-join

[discussion of what is and is not in scope for Silver,. emerging tech is in]

<jeanne> Jeanne: We want to keep the guidelines (and functional user needs) technology neutral so it can be applied byyond web, the way that WCAG2ICT document does. We agreed to restrict emerging technologies to web in our charter.

<CharlesHall> sorry. i have to drop off the call early.

<AngelaAccessForAll> Sounds good

jeanne: Asks Agngela's help getting plain language people to help with our language

SC 1.4.7 Low or No Background Audio

jeanne: Why this isn't audio control and interruption? Anyone recall?

<jeanne> https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.tpczdeehu714

<Chuck> People who are hard of hearing often have great difficulty separating speech from background sound.

jeanne: Makes sense, but still wondering whether we can combine
... Also ADD need

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/09/06 19:00:24 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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/zakim, take uo item 1//
Succeeded: s/to/with/
Present: jeanne janina Chuck AngelaAccessForAll shari CharlesHall pkorn KimD
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 06 Sep 2019
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]