Web Content Accessibility Guidelines Working Group Teleconference

01 Sep 2015

See also: IRC log


EricE, Laura, AWK, Srinivasu_Chakravarthula, Kathy, jon_avila, kenny, adam_solomon, David_MacDonald, Katie, Haritos-Shea, MichaelC, Katie_Haritos-Shea
Wayne, Bruce, Mike, Moe


<trackbot> Date: 01 September 2015

<scribe> scribe: Laura

Quickref update

<yatil> http://w3c.github.io/wai-wcag-quickref/

Eric: Polishing and doing stuff under the hood.
... Next steps is to define text in filter.
... Will draft wiki page and invite people to participate.
... Thinking about welcome text and help page.

<yatil> http://github.com/w3c/wai-wcag-quickref/issues/

Eric: It is coming along.

JOC: Thanks Eric.

Re-approval of publication (due to minor change) - survey item1 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/#wbsq2

<Joshue> LC: Just a minor typo in some br elements

Laura: Minor typo: http://www.w3.org/WAI/GL/2015/WD-UNDERSTANDING-WCAG20-20150714/media-equiv-captions.html#media-equiv-captions-examples-head

AWK: easy to fix.

MichaelC: will take a look

RESOLUTION: WG Accepted of re-publication.

"Future link" techniques - survey item2 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/#wbsq3

<Joshue> http://www.w3.org/WAI/GL/2015/WD-WCAG20-TECHS-20150714/

JOC: Future links that we don’t have yet. Proposal to remove.

David: Are they in the tech docs?

JOC: It is in the understanding doc

Jon: Confusing but could be helpful.

JOC: Okay to move?

Jon: okay.

AWK: We could link to a new doc with the info.

Jon: maybe rephrase?

<AWK> For people to see what this is about, take a look at http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html and see the "additional techniques (advisory) for 1.3.1" section for two "future links"

JOC: Should we create a separate page?

AWK: Whatever makes the most sense.

MichaelC: Has started on it. Has spent a few hours.

<Zakim> MichaelC, you wanted to say categorizing on wiki orthagonal to what we do with formal publicaiton

MichaelC: My work is orthagonal to what we do with formal publicaiton

RESOLUTION: Leave open. MichaelC will continue with work.

Working group Decision policy


AWK: Is still on the radar an want to come to a final proposal.

JOC: We will get back to this soon.

Github issues and work progress - survey item3,4,5,6 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/

<Joshue> [Github] SCR37 appears to duplicate SCR26? #108

<Joshue> https://github.com/w3c/wcag/issues/108

JOC: Suggestion to merge. Veering to no. Need to be reviewed.

Jon: Only mapped to focus order. Is reading order a failure? Maybe in some cases.

AWK: We are not entirely sure if we should combine or not. Either way may work.

<Joshue> Github] if auto-redirect despite WCAG but UA blocks, tell user where to go #102


katie: When you land on a new page and focus goes to an advertisment.

David: Can’t really map it to a failure.

katie: seems like a clear failure

James: we are talking about browser redirects.
... Don’t see how this is an accessibility issue.
... It is a bug for everyone.

JOC: leave it open.

RESOLUTION: Leave open. More info needed.

<Joshue> [Github]question on [Low Vis] Failure of Success Criterion 1.4.3 and 1.4.6 due to using background color[...]

<Joshue> https://github.com/w3c/wcag/issues/95

<Joshue> http://www.w3.org/TR/2015/NOTE-WCAG20-TECHS-20150226/G18

JOC: Relates to G18

Katie: Depends on if background is moving. Squint test. Other tests.

Jon: takes lowest contrast and uses that. Android has a hallo.

<jamesn> hmmmm.... I wonder if we could do that with a CSS override (the double halo)....

Jon: Have to test responsive in different modes.

kathy: Greg Kause has good tool.

<jon_avila> http://accessibility.oit.ncsu.edu/blog/2013/10/29/color-contrast-analyzer-for-chrome-text-in-images-gradients-pdfs-and-more/

James: Greg Kaus’ tool is still manual.
... The does a pixel test.

s/Hallo/ Halo/

RESOLUTION: Leave open. Discuss with Wayne.

<Kathy> http://accessibility.oit.ncsu.edu/tools/color-contrast-chrome/

<Joshue> [Github] List of sufficient techniques for situation B seems to be not complete #103

<Joshue> https://github.com/w3c/wcag/issues/103

AWK: Not completely empty.

JOC: Not clear what should go in there.

AWK: Surprised if all of the ARIA techniques fit.

JAMES: Several ARIA techniques are not relevant.

RESOLUTION: Leave open. Discuss with Wayne further.

<David> I've extracted out all the advisory techniques in WCAG and posted them here. http://davidmacd.com/blog/Advisory-Techniques-WCAG.html about 238 future techniques not written up.

My mics not working . It is the last item


<jamesn> regrets for next 2 weeks

trackbot, end meeting

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/09/01 16:17:30 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/It iscoming along./ It is coming along./
Succeeded: s/Present+Katie Haritos-Shea/Present+ Katie_Haritos-Shea/
Succeeded: s/rephrrase?/rephrase?/
FAILED: s/Hallo/ Halo/
Found Scribe: Laura
Inferring ScribeNick: laura
Default Present: EricE, Laura, AWK, Srinivasu_Chakravarthula, Kathy, jon_avila, kenny, adam_solomon, David_MacDonald, Katie, Haritos-Shea, MichaelC
Present: EricE Laura AWK Srinivasu_Chakravarthula Kathy jon_avila kenny adam_solomon David_MacDonald Katie Haritos-Shea MichaelC Katie_Haritos-Shea

WARNING: Replacing previous Regrets list. (Old list: Bailey_Bruce, Mike_Elledge)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ Wayne, Bruce, Mike, Moe

Regrets: Wayne Bruce Mike Moe
Found Date: 01 Sep 2015
Guessing minutes URL: http://www.w3.org/2015/09/01-wai-wcag-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]