W3C

- DRAFT -

Silver Community Group Teleconference

27 Aug 2019

Attendees

Present
jeanne, Chuck, janina, KimD, CharlesHall, Makoto, johnkirkwood
Regrets
Shawn
Chair
jeanne
Scribe
jeanne

Contents


Update from people working on functional user needs updates

Chuck: We are meeting tomorrow. It is in progress

Charles: No update

Janina: Silver is invited to APA at TPAC, probably Friday morning will be dedicated to XR. I will know by Friday.

Bruce: I have a link to the EN document that maps all the SC to Functional Needs. I extracted the relevant parts from the doc.

<CharlesHall> here is a list of just the relevant functional statements http://mandate376.standards.eu/standard/functional-statements

Jeanne: I think it will be helpful.
... we have to remember there are functional needs that aren't in the EN301 list, like vestibular disabilities

<KimD> That's my question too - whether we have a list of our own functional needs

<CharlesHall> seems chicken and egg

Jeanne: we also need to be careful about the cognitive disability in EN301 because they are all lumped together. They don't have the granularity of the physical disabilities.

<bruce_bailey> The web version that CharlesHall listed is excellent but...

https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.fjszln5otgkv

<bruce_bailey> (1) I am not sure it is the most current version (v2.1.1, 2018-02)

<bruce_bailey> (2) It does not include the annexes

<bruce_bailey> Link to current PDF version of EN 301 549 is: https://www.etsi.org/deliver/etsi_en/301500_301599/301549/02.01.02_60/en_301549v020102p.pdf

<bruce_bailey> Annex B, relationship between requirements (WCAG 2.1 SC) and functional performance statements, starts on p. 83.

<bruce_bailey> Oops, current version of EN 301 549 is v2.1.2, 2018-08

<bruce_bailey> Annex B starts on page 88 of the PDF -- and the print page number does match the PDF page number.

<johnkirkwood> can't take advantage of tools like resize, spacing, voice assistant reading of text while

<johnkirkwood> don't use images of text.

<johnkirkwood> color blindness as well.

SC 142 Audio Control & 2.2.4 Interruptions

<johnkirkwood> very good point Janina!

<bruce_bailey> https://docs.google.com/spreadsheets/d/1W5CSvU4XxWXNneu4ibokjcYUCsG386xL1rGOiTrDvt8/edit#gid=1061857871&range=A1

<bruce_bailey> Link to GoogleSheet version of Annex B excerpt:

<KimD> (working together as a group on SC 1.4.4 Resize text, SC 1.4.5 Images of Text, SC 1.4.9 Images of Text (No Exception), SC 1.4.8 Visual Presentation, SC 1.4.12 Text Spacing)

<bruce_bailey> https://docs.google.com/spreadsheets/d/1W5CSvU4XxWXNneu4ibokjcYUCsG386xL1rGOiTrDvt8/edit#gid=1834752082&range=A1

<johnkirkwood> Janinina mad point to overlapping audio interactions

<johnkirkwood> made point that audio interactions of competing voices requesting input such as 'press one' can compete with assistive technology.

<johnkirkwood> was that right

<KimD> And that when there's one audio stream, it's nearly impossible to cognitively separate the combined audio stream.

<KimD> ... When two audio streams, it may be possible to separate and understand.

<KimD> (my recollection)

Bruce: - explaining codes in the spreadsheet - from EN 301 549

<Makoto> This is very helpful. Thanks Bruce!

Bruce: Cautions that I don't know if this document had wide review.

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/08/27 14:31:25 $

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)

Present: jeanne Chuck janina KimD CharlesHall Makoto johnkirkwood
Regrets: Shawn
No ScribeNick specified.  Guessing ScribeNick: jeanne
Inferring Scribes: jeanne
Found Date: 27 Aug 2019
People with action items: 

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]