W3C

- DRAFT -

Accessibility Guidelines Working Group Teleconference

13 Dec 2018

Attendees

Present
alastairc
Regrets
Chair
SV_MEETING_CHAIR
Scribe
alastairc

Contents


Meeting times over the holidays

Next meeting on 20th, start after the holidays on the 10th Jan.

LVTF update on gap analysis

http://w3c.github.io/low-vision-a11y-tf/user-needs-coverage.html

Contradictory failure & technique?

<scribe> scribe:alastairc

<AbiJ> https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 - states colour can not be the only discrimination for a link

<AbiJ> https://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G183 - states that colour can be used but with sufficient contrast

Always worth checking the procedure: "Check that each link in the page that is identifiable by color (hue) is visually identifiable via some other means (e.g., underlined, bolded, italicized, sufficient difference in lightness, etc).

<EA> https://www.w3.org/TR/WCAG21/

Article on this: https://webaim.org/blog/wcag-2-0-and-link-colors/

Survey, 2 items https://www.w3.org/2002/09/wbs/35422/technique-approvals2/

http://htmlpreview.github.io/?https://github.com/w3c/wcag/blob/tech-icon-contrast/techniques/general/icon-contrast.html

EA: That's great, more like that.

http://htmlpreview.github.io/?https://github.com/w3c/wcag/blob/non-text-contrast-updates/understanding/21/non-text-contrast.html

https://www.w3.org/TR/WCAG21/#non-text-contrast

Low vision gap analysis: http://w3c.github.io/low-vision-a11y-tf/user-needs-coverage.html

Abi: There's quite a big overlap with COGA, are they going to work in parallel?

EA: The LVTF doc is good, but the tables are difficult.

AC: Suggest that Steve does a high-level overview of COGA user-needs and coverage in WCAG 2.1 / Silver

Silver IA/plain English exercises

Example technique tracking: https://docs.google.com/spreadsheets/d/15idlBl1qQTNr2SIi4Drzk1Q1vnWAi5L26GCCv6mjD2g/edit?usp=sharinghttps://docs.google.com/spreadsheets/d/15idlBl1qQTNr2SIi4Drzk1Q1vnWAi5L26GCCv6mjD2g/edit?usp=sharing

EA: Have explored 'white space', but noticed discussion in LV about what it actually is.
... got put in with chunking / management blocks.

AC: Purpose is to test the framework, not so much the content.

Abi: Discussed this with others about methods. Will try next week

trackbot end meeting

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: 2018/12/13 10:05:19 $

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)

Default Present: alastairc
Present: alastairc

WARNING: Fewer than 3 people found for Present list!

Found Scribe: alastairc
Inferring ScribeNick: alastairc

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 13 Dec 2018
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]