30 Nov 2015

See also: IRC log


janina, MichaelC, Lisa_Seeman, Mike_Pluke, Neil_Milliken, John_Rochford, Steve_Lee, Debbie_Dahl, E.A._Draffan, Tony_Doran, Rich_Schwerdtfeger, Mary_Jo, John, Renaldo
EA, Ayelet_Seeman


<Lisa_Seeman> agenda: this

<Lisa_Seeman> scribe: maryjom

<Lisa_Seeman> next item:

Suggested lang for wcag

Ronaldo: New member. Looking into emotions.

LS: Ronaldo will write issue paper on depression.
... People with dementia typically have depression and anxiety.

Issue papers - GA

LS: Will look into any issues and potential techniques in that area.
... Typical techniques for people with dyslexia say to give encouragement.

Ronaldo: Issue paper will focus on depression and anxiety in general, not only for people with dementia but generally people who have depression and/or anxiety.

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Current_schedules

LS: The above link is to the updated schedule.
... Next deadline is 28 January to freeze the content of the Gap Analysis to go into a working draft.
... Went over the list of dates in the Current Schedules page.

Techniques - GA

<Lisa_Seeman> ACTION: lisa to followup on MJ access to github [recorded in http://www.w3.org/2015/11/30-coga-minutes.html#action01]

<trackbot> Created ACTION-146 - Followup on mj access to github [on Lisa Seeman - due 2015-12-07].

RS: We need a table for the gap analysis. To know what standards we need to fill in the gaps
... It could be done in the form of a roadmap
... Like in ARIA 1.0 we had a roadmap to educate the industry on what is needed and why.

Janina: We should keep the table and do a summary like around what the media accessibility did. Helps people understand what the issues are and how to address them.

It needs an introduction to summarize what is in the issue papers so readers don't have to read all of the issue papers and then pointers to the issue papers if someone wants to read more.

<richardschwerdtfeger> http://www.w3.org/TR/2006/WD-aria-roadmap-20060926/

RS: In ARIA we put a description of the problem. So we could have a high level description of cognitive disabilities and then more details about the gaps and what needs to be done to fill them.

Janina: There are a lot of areas not covered and we want to take a systematic approach. Want to describe who benefits and how.

<janina> http://w3c.github.io/pfwg/media-accessibility-reqs/

Janina: Michael and Shane are working on this media accessibility document. (link above).
... You need a starting point so readers can start to understand what the problems are.
... Then you can point to other places for readers to dig further for more detail.

LS: Need volunteers to work on the summary.

JR: Agreed to help out with the gap analysis summary.

<Lisa_Seeman> ACTION: Lisa, Maryjo and john to work on gap analisis summary [recorded in http://www.w3.org/2015/11/30-coga-minutes.html#action02]

<trackbot> Error finding 'Lisa,'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

MM: Will help out too.

RS: Will also help with the roadmap.

JS: In the media accessibility the cognitive disability description doesn't mention comprehension or the different modes of delivery to help with comprehension.

LS: When we had a discussion of the multimedia we had an example of using headers - which are visible in the video content and an ability to navigate to these specific headings in the video.

JS: Asked John to send in comments today regarding coga issues in the media accessibility document so the team can determine how serious the issue may be and if it needs to be improved before it is published.
... This may be authoring and user agent issues which are excluded from the media accessibility requirements. The focus of this document was what HTML5 needed to support that it has the right capabilities.

JR: Was convinced no further updates are needed to the media accessibility doc.

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/table.html

LS: The formatting of this table is still being improved. Should there be user stories/use cases added in here, or should there be potential solutions added in there?
... The table also will have links to issue papers and discussions on that particular user need.

JR: It would help for us to see a completed example or two in the table with a full row or two completed.

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Proposal_for_WCAG

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Proposal_for_WCAG#New_success_criteria

LS: This isn't done yet, but would like team to look at the new success criteria. The comment was to make this more testable.
... We added some exceptions to help out, and were more prescriptive to make the requirements more testable.
... Would like team to take a look and see how the requirements were reworded.

Janina: This looks good.

Michael: Will have to look more in-depth.

<Tony_Doran> I need to drop off, sorry.

MC: Proposed requirements need to have levels (A, AA, or AAA)

LS: Every level 3 heading is a new proposed SC.

MC: These need to be worded in WCAG success criterion language.

MP: These could be reworded fairly easily.

MC: WCAG SC are really brief, so including a lot of bullets may cause an issue.

LS: We can't split these up into a lot of success criteria, as our goal is to minimize how many are added.

MC: In an extension we could add more success criteria, but we don't want to add too many so implementers won't think this will be too difficult to meet.
... Will need better wording that aligns better with the WCAG guidelines.
... We have to be careful about providing any type of writing style guide as it is difficult to internationalize. If you want to defer things to techniques you'll wind up with SC that are more straightforward.

The things that you put in as SC should be the things that you absolutely must do.

MC: You could put one of these SC in front of the working group to get better feedback on the structure and then apply to the rest of the document.

LS: Let's send Clear Writing Style to the working group to see what they think.

Summary of Action Items

[NEW] ACTION: lisa to followup on MJ access to github [recorded in http://www.w3.org/2015/11/30-coga-minutes.html#action01]
[NEW] ACTION: Lisa, Maryjo and john to work on gap analisis summary [recorded in http://www.w3.org/2015/11/30-coga-minutes.html#action02]

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2015/11/30 18:22:25 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: maryjom
Inferring ScribeNick: maryjom
Default Present: janina, MichaelC, Lisa_Seeman, Mike_Pluke, Neil_Milliken, John_Rochford, Steve_Lee, Debbie_Dahl, E.A._Draffan, Tony_Doran
Present: janina MichaelC Lisa_Seeman Mike_Pluke Neil_Milliken John_Rochford Steve_Lee Debbie_Dahl E.A._Draffan Tony_Doran Rich_Schwerdtfeger Mary_Jo John Renaldo
Regrets: EA Ayelet_Seeman
Got date from IRC log name: 30 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/30-coga-minutes.html
People with action items: john lisa maryjo

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

[End of scribe.perl diagnostic output]