Silver Community Group Teleconference

30 Jul 2019


Lauriat, jeanne, Chuck, CharlesHall, bruce_bailey, Makoto, jf, KimD, Jan
Shawn, jeanne


<scribe> Meeting: Silver Content Migration Teleconference

<scribe> scribe: jeanne

Call & communication changes: parallel tracks & summary of minutes

SL: Today is the first day of parallel tracks.
... this call will focus on content migration
... later today (or earlier tomorrow) will be the conformance call
... Friday will be a combined meeting that will address the issues that we wnat the entire group can here
... Minutes: We want to start sending out the email with the minutes with a summary of what was discussed or decided in the meeting sot that it is easier for others to follow the work being done in the sub-group


Functional user needs

SL: The content migration work has finished the outline of the grouping of the different kinds of guidance based on user needs.
... for example, non-text content has 3 different WCAG SC that cover it.
... We want to build up the user needs for each of the groupings

<Lauriat> Migration outline working doc: https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit

SL: then write the tests to test the whether the user need is met.

<Lauriat> Alternative text prototype draft: https://docs.google.com/document/d/1HturJb9GK2UUjrlUc09ACC4KeYMdzAKc2nGX5X6lJvk/edit

SL: We want to start fleshing out some of the SC that we need for testing, illustration purposes

<Lauriat> Short: Individuals who are blind or with visual impairments need to understand the purpose and context of any web content that is not in text format.

JF: Don't we want to include more groups who also benefit from the guidance, like Cognitive

<CharlesHall> Use with or without vision; Use with or without limited vision; Use with or without limited cognition

SL: We do. And we wnat to phrase it as functional needs.

<CharlesHall> from the adapted descriptions of Functional Performance Statements of EN 301 549

JS: Content writing process update: https://docs.google.com/document/d/10zDtAvu0vP4BpZ4yYqupj7nDfk1jPNnbnHmnby_AGn8/edit
... This alternative text draft was written in early May. We have done a lot more work on the process of writing the content.

SL: Functional needs assessment

CA: THis is an expert evaluation of what the user needs are

SL: For example, users who cannot see need alternative text that describes the image

<Makoto> I'm working on this with Jennifer and Nicolas.

<Makoto> https://docs.google.com/document/d/16RIRKhU21FlgkgkoF5pZLUR3uXjN2I6OmfCSpqlv2vA/edit

Makoto: I just started working on this with Jennifer and Nicholas. We are working on this document separately. We will be able to share it after 11 August or later.

<CharlesHall> I am still in favor of the functional need language over the person-first or disability-first language

<Lauriat> 1. People who can’t see the images (who are blind, who has low vision, etc.).

<Lauriat> 2. People who have difficulty understanding the meaning of photographs, drawings, and other images (e.g., line drawings, graphic designs, paintings, three-dimensional representations), graphs, charts, animations, etc. (from “Benefits” in Understanding doc)

<Lauriat> 3. People who are having trouble reading image of text (who has dyslexia.).

<CharlesHall> rephrased: Use with or without vision; Use with or without limited vision; Use with or without limited cognition

<Zakim> bruce_bailey, you wanted to say that I think Jeanne suggesting FPC without listing all possible FPC

Charles: It depends on what list we use

Jeanne: I think we can use the specific functions we want to address and use that style of language to phrase it with sensitivity.

Charles: How granular do we want to get, especially with cognitive disabilities, for example, people with anxiety disorders have a different need than people with limited cognition or dyslexia

<CharlesHall> they originally came from Functional Performance Statements of EN 301 549


<Lauriat> http://mandate376.standards.eu/standard/functional-statements

JS: This is one that Alastair adapted to map WCAG SC to EN301-549

SL: These are the EN301549 functional performance statements:

4.2.1 Usage without vision

4.2.2 Usage with limited vision

4.2.3 Usage without perception of colour

4.2.4 Usage without hearing

4.2.5 Usage with limited hearing

4.2.6 Usage without vocal capability

4.2.7 Usage with limited manipulation or strength

4.2.8 Usage with limited reach

4.2.9 Minimize photosensitive seizure triggers

4.2.10 Usage with limited cognition

Chuck: Cybele and I didn't do this. Do we need to change our language?

SL: No, this is more of a sanity check to make sure we have covered the basic areas

Color Contrast

<CharlesHall> note: that list of FPS does not include mental health or intersectional needs

<Lauriat> +1 to Charles, I think it leaves out a lot, but it at least gives us a good starting point.

JS: We received a detailed email from Andy Somers with a lot of detailed comments of technical information on Visual Contrast. I put it in a new document and linked it from the main wiki page. Color Contrast Discussion

Chuck: Cybele and I had a lot of discussion about scope. I wanted to keep the scope narrow, and Cybele wanted to expand the scope.

SHawn: We don't know yet. We need to experiment with it and test to see how well each of them works. We may need to split this into separate guidelines or grouped together.

JF: Are we also looking at the new SC coming in WCAG 2.2?

<CharlesHall> I found the list of Modalities adapted from the Functional Performance Statements that extends them. https://docs.google.com/document/d/1lEkht-bhkaPMzOojWpDjZhbnGeckiYLh-J4-ze7cGS0/edit#

SL: We saw the 2.2 spreadsheet list yesterday for the first time. Right now we are focusing on the examples of work that could not get into WCAG 2.1 for structural reasons to make sure they can be included in Silver.

JF: I want to make sure that anything we do is adaptable enough to include the new success criteria.

SL: That is a primary requirement for Silver, that we can be adaptable and flexible to add in additional coverage, either of new functional needs or new guidance.

CH: This document on Functional Performance Statements was done as part of the Heuristic Walkthrough proposal.

<Lauriat> 1. People with colour blindness can miss distinctions in visualizations and text, if there is insufficient colour contrast.

<Lauriat> 2. People with moderately low vision, including seniors, can have difficulty perceiving content in documents which do not have sufficient size or contrast. With smaller font there may be more need for higher contrast; likewise, larger font may reduce the need for higher contrast.

<Lauriat> 3. People with some cognitive, language and learning disabilities and some low vision users may find colour contrast distracting if it doesn’t directly serve the intent of the communication.

<Lauriat> 4. SCOPE EXPLORATION: Too much contrast can trigger headaches, disorientation, distraction and other symptoms for some users with migraines, sensory sensitivities and various cognitive disabilities.

Color Contrast draft: https://docs.google.com/document/d/18CRsPyrpDHwt1fS-7IPR6iLyW2qr7LbdL-3lzzFiwRY/edit

SL: I copied the functional user needs into the Migration document.

<CharlesHall> Use with or without perception of color

<Lauriat> Editing in the outline: https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.6qr1ipbfmz1x

Color COntrast DIscussion from Andy SOmers: https://docs.google.com/document/d/12AfVx_KyNaw7Dj-OZlWFs6riJGBQGOuxmUeBY5Spgq4/edit

Chuck: THis is a well-established standard, do we want to consider changing it?

SL: One of our goals is to build on the guidance of WCAG, but I do think we want to expand coverage, but we don't want to boil the ocean in the first version.
... one of the issues is that excessive color contrast causing physical pain.

<Lauriat> "People who miss distinctions in visualizations and text, if there is insufficient colour contrast. (colorblindness)"

SL: we need to discuss whether we are going to add to the guidance, and we may identify guidance that we will document for a future guidance

<CharlesHall> Use with or without perception of color

Also, ”color blindness” is actually very rare. What most people have is ”color vision deficiency”. Protan, Deutan, and Tritan all can see SOME colors, just they perceive a smaller gamut of colors. Only those with a rare impairments such as ”blue cone monochromat” are truly ”color blind”.

<CharlesHall> but color vision deficiency is still a named disability versus a functional need

From ANdy SOmers email

<Lauriat> "People who have trouble distinguishing between colors. (colorblindness)"

Charles: the functional performance statement from EN301549 is "perception without color" I think it should be "with or without color"
... the wording you pasted is still "person first" language without saying what the underlying need is.

<bruce_bailey> use with or without seems like a no op

BB: We need more clarity. WIth or without inlcudes everything.

Charles: We were trying to import a specific WCAG criteria that doesn't include the "without". We may want to split it into two criteria -- the original WCAG intent, then an expansion of scope that includes those who have issues with too much color contrast.

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/07/30 14:30:27 $

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/lol//
Present: Lauriat jeanne Chuck CharlesHall bruce_bailey Makoto jf KimD Jan
Found Scribe: jeanne
Inferring ScribeNick: jeanne
Found Date: 30 Jul 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]