22 May 2017

See also: IRC log


JohnRochford, MichaelC, kirkwood, janina
Mike_Pluke, JohnRochford


<lisa> agenda: this

<lisa> other usefull links rewording https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html

<lisa> Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html instuctions: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1, issues: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA

<JohnRochford> 4x now, WebEx has hung up and called me back

<lisa> scribe: Mike_Pluke

accessible authentication


<lisa> https://www.w3.org/2017/11/TPAC/

TPAC is in San Francisco. Mike can't make it, John Rochford might be able to. John Kirkwood and Thaddeus can.

<JohnRochford> https://github.com/w3c/wcag21/issues/23

Mike queried whether our new proposed SC would replace the existing AAA SCs as several techniques were already associated to these SCs

<lisa> lets get what we have to coga end f this week and propos it in 3 weeks to wcag

<lisa> http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017May/0095.html

<lisa> Provide words or phrases or abbreviations that are the most-common form to refer to the concept

Plain language - Suggesting a tool that can present the most commonly used words from a language.

<lisa> google ingram in a common tool

Most famous tool and Google engram?

<JohnRochford> Google Ngram articles: https://www.google.com/search?q=google+ngram&oq=google+n&aqs=chrome.0.69i59j0j69i60l3j69i57.2247j0j7&sourceid=chrome&ie=UTF-8

<lisa> scribe: JohnRochford

Jan: Help SC is not in great shape because we can find the research we need.
... Recent search found new abstract requirements reveals a length of 100 words.

<lisa> https://github.com/w3c/wcag21/issues/32 http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017May/0098.html

<lisa> Help and support: comprehension support is available via:

<lisa> =Charts, tables, or graphics to summarize [complex numerical information];

<lisa> =Summaries of [long documents];

<lisa> =Emphasis of key words in [long documents];

<lisa> =Instructions for [non-standard controls];

<lisa> =Information about a user's position in multi-step forms;

<lisa> =Alternative terms for relative and cardinal directions;

<lisa> =Non-numerical versions of numerical values.

Jan: What do we think about emphasizing keywords rather than document length?

Lisa: Help SC is now more testable than it was.

Michael: If you have to have a summary for every little thing, the working group will reject.
... Last I saw was 300 words, which won't catch too many web pages.

<lisa> note that content that does not have

Lisa: Should we have scope statements or exceptions?

Michael: Each bullet could be its own SC, but we are trying to make things easier by combining.
... A complex SC wording for a minor increase in scope may not get through the AG working group.
... Perhaps we could define what complex wording is.

Jan: People do not know how they could define what complex wording is.

Michael: Word length is very variable across languages.

Mike said the above, not Michael.

Jan: Do we have a research basis for the terminology/wording we are using?

Michael: The lower the author burden, the fewer requests for research backing there will be.
... I'm trying to simplify the SC for acceptance by the AG working group.

<lisa> Help and support: comprehension support is available via one of the following

Michael: The more complex the wording of an SC, the less likely it will be accepted.
... Maybe it should be "at least one of the following".

Jan: The complexity of the text would determine how many could be done.

Michael: We could say only one is required, but authors could follow as many as they want.

I'm signing off.

<lisa> https://github.com/ayelet-seeman/coga.personalisation

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/05/22 17:39:13 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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: JohnRochford MichaelC kirkwood janina
Found Scribe: Mike_Pluke
Inferring ScribeNick: Mike_Pluke
Found Scribe: JohnRochford
Inferring ScribeNick: JohnRochford
Scribes: Mike_Pluke, JohnRochford
ScribeNicks: Mike_Pluke, JohnRochford

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

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

Got date from IRC log name: 22 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/22-coga-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]