<LisaSeemanKestenbaum> WCAG 2.1 understanding sections https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<LisaSeemanKestenbaum> Approving the tables and next publications

<LisaSeemanKestenbaum> scribe: jan

<LisaSeemanKestenbaum> xakim, next item

Updates and WCAG survey https://www.w3.org/2002/09/wbs/35422/Updated_CR_pub/

Lisa: WCAG 2.1 survey is available. It's a controversial question because it's approving the transition of the working draft to candidate recommendation.

<LisaSeemanKestenbaum> http://rawgit.com/w3c/wcag21/exit-criteria-review/guidelines/

<LisaSeemanKestenbaum> Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these. Thes

<LisaSeemanKestenbaum> i cant aprove that statment

<kirkwood> I agree, shouldn’t approve cognitive

<LisaSeemanKestenbaum> we have two hours to vote against it

Lisa: The introduction to WCAG 2.1 says the following: "Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these."

Janina: Perhaps we should recommend language that better reflects the current state.
... maybe something like, "begins to address...."

<LisaSeemanKestenbaum> Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web conte

<kirkwood> Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, begins to address learning disabilities and cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these.

Lisa: Maybe something like, "begins to address at AAA."

<kirkwood> begins to address learning disabilities and cognitive limitations

<LisaSeemanKestenbaum> Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web conte

<alastairc> Does it matter that the language refered to above hasn't changed from 2.0?

<LisaSeemanKestenbaum> i dont think so

<LisaSeemanKestenbaum> we need the group to understand that they have not done what they are saying they have done

<LisaSeemanKestenbaum> janina: if it claims to do things that it isnt then it is dangrouse to the respect that wcag has

<LisaSeemanKestenbaum> John: it damidgers wcag reputation and alientaes people who could help

<LisaSeemanKestenbaum> https://www.w3.org/2002/09/wbs/35422/Updated_CR_pub

Lisa: okay ... I am back as the scribe.

<LisaSeemanKestenbaum> https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3ACOGA+-label%3A%22Integrated+into+Draft+Guidelines%22

Lisa: There's a page of comments that we are meant to think about answers for and make sure that our understandings sections address them.

<LisaSeemanKestenbaum> the cmments

<LisaSeemanKestenbaum> understanding sections : https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<LisaSeemanKestenbaum> action alister to review comments at https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3ACOGA+-label%3A%22Integrated+into+Draft+Guidelines%22 and check they are adressed in understding sections in https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

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

<LisaSeemanKestenbaum> action alaster to review comments at https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3ACOGA+-label%3A%22Integrated+into+Draft+Guidelines%22 and check they are adressed in understding sections in https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

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

<alastairc> alastairc

<LisaSeemanKestenbaum> action alastairc to review comments at https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3ACOGA+-label%3A%22Integrated+into+Draft+Guidelines%22 and check they are adressed in understding sections in https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

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

<LisaSeemanKestenbaum> action alastair to review comments at https://github.com/w3c/wcag21/issues?q=is%3Aissue+label%3A%22Implementation+Follow-up%22+label%3ACOGA+-label%3A%22Integrated+into+Draft+Guidelines%22 and check they are adressed in understding sections in https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<trackbot> Created ACTION-260 - Review comments at https://github.com/w3c/wcag21/issues?q=is%3aissue+label%3a%22implementation+follow-up%22+label%3acoga+-label%3a%22integrated+into+draft+guidelines%22 and check they are adressed in understding sections in https://www.w3.org/wai/gl/wiki/accepted_wcag_2.1_sc [on Alastair Campbell - due 2018-02-01].

<NeilMilliken> +neilmilliken

<LisaSeemanKestenbaum> action lisa to review understding sections in https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<trackbot> Created ACTION-261 - Review understding sections in https://www.w3.org/wai/gl/wiki/accepted_wcag_2.1_sc [on Lisa Seeman-Kestenbaum - due 2018-02-01].

Lisa: Need to make sure that the understandings documents are up-to-date
... JohnR was working on accessible authentication, but that is not making it into 2.1

Alastair: Where are the current documents located?

Lisa: The are in github branches
... one other issue is that there is a subgroup on making content usable for people with cognitive and learning disabilities - the meetings will be on Tuesday. Lisa sent out an email. If you don't see the time, or did not receive the email and you want to be involved in the writing of that document, please let Lisa know.

<alastairc> Meeting email: https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2018Jan/0043.html

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: Jan janina

WARNING: Fewer than 3 people found for Present list!

Found Scribe: jan
Inferring ScribeNick: Jan

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


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

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.)