RE: Renaming the Guideline it falls under. (was Re: CFC - Decision to keep 1.3.4 where it is)

I would not be in support of renaming the guidelines as that in my opinion would break the backward compatibility of WCAG 2.1 – we could add new ones – but I think at this CR stage that is too late as well.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access
jon.avila@levelaccess.com
703.637.8957 office

Visit us online:
Website<http://www.levelaccess.com/> | Twitter<https://twitter.com/LevelAccessA11y> | Facebook<https://www.facebook.com/LevelAccessA11y/> | LinkedIn<https://www.linkedin.com/company/level-access> | Blog<http://www.levelaccess.com/blog/>

See you at CSUN in March!<http://info.levelaccess.com/CSUN-2018-Sessions.html>

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Sent: Thursday, March 15, 2018 4:51 PM
To: John Foliot <john.foliot@deque.com>; Michael Gower <michael.gower@ca.ibm.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Renaming the Guideline it falls under. (was Re: CFC - Decision to keep 1.3.4 where it is)

I’m inclined to agree with John – if we were going to rename guidelines we should have done that before CR. We can discuss and get Michael’s perspective also, but this seems problematic at this point.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk


From: John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>>
Date: Thursday, March 15, 2018 at 16:45
To: Michael Gower <michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>>
Cc: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>, WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Renaming the Guideline it falls under. (was Re: CFC - Decision to keep 1.3.4 where it is)

That would run afoul of one of our mandated requirements: Backward compatibility<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fwcag2-req%2F%23backwards-compatible&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285524361&sdata=gYufCcmSEkPjqaoqfINS8VPME8S585YU9%2BbsrPreOTc%3D&reserved=0>, as that would be a significant change to WCAG 2.0.

It is a great suggestion for the Silver TF however...

JF




On Thu, Mar 15, 2018 at 1:00 PM, Michael Gower <michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>> wrote:
-1
I can't live with us not making an attempt at a better analysis of SC classifications in general. After more consideration, I've realized we can likely have our cake and eat it too for 1.3.4 by renaming the Guideline it falls under. I've put my thoughts into a new comment<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F806-2523issuecomment-2D373461750-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C3eae10ba854540fa045d08d58a9cae86-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636567327900254973-26sdata-3D-252B1ImDmfB67IFJ65m6v4qbcakQ8Zuq52wbjBVorqnFB4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3Dm5h1sX-YmS9bCEEqqJryxLVwns_pPf6eYXlbmiwpdXA%26s%3DHfvoil-4KgEijw-NzkQq-2PbJk8r7054UwYddIDcouQ%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285524361&sdata=68ac%2Br8uwQTIOIbdf36DvYVM1APgmYbRoVlMWzLz0mo%3D&reserved=0>in the existing new issue I opened Addressing weak SC classifications #806<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F806-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C3eae10ba854540fa045d08d58a9cae86-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636567327900254973-26sdata-3DaN2yJK8DHQvEc5q-252BXLN1FHj8ql6H159ULJasZYe-252BmL8-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3Dm5h1sX-YmS9bCEEqqJryxLVwns_pPf6eYXlbmiwpdXA%26s%3DlnwzYMvdi3CQlFdiEfzQ5V2BUe4Jz_IC_G4rjLYDaY0%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285524361&sdata=iP20D2Uv0SRr2vml3z3ce%2BdPMJYfX6MyyFdhekHkNCg%3D&reserved=0>

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaps.google.com%2F%3Fq%3D1803%2BDouglas%2BStreet%2C%2BVictoria%2C%2BBC%2B%2BV8T%2B5C3%26entry%3Dgmail%26source%3Dg&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285680612&sdata=VPvvXm5BwZWeBiGunQdypjIWw7uYHCibcxxZrOJOkxY%3D&reserved=0>  V8T 5C3<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaps.google.com%2F%3Fq%3D1803%2BDouglas%2BStreet%2C%2BVictoria%2C%2BBC%2B%2BV8T%2B5C3%26entry%3Dgmail%26source%3Dg&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285680612&sdata=VPvvXm5BwZWeBiGunQdypjIWw7uYHCibcxxZrOJOkxY%3D&reserved=0>
gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com>
voice: (250) 220-1146<tel:(250)%20220-1146> * cel: (250) 661-0098<tel:(250)%20661-0098> *  fax: (250) 220-8034<tel:(250)%20220-8034>



From:        Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
To:        WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Date:        2018-03-15 08:34 AM
Subject:        CFC - Decision to keep 1.3.4 where it is
________________________________


Call For Consensus — ends Monday March 19th at 11:00am Boston time.



The Working Group has discussed a change which would move SC 1.3.4 Identify Common Controls to Guideline 3.3. This CFC is to evaluate the apparent consensus to not move the SC. On the WG call there was a lower level of support to move the SC than to not move it.



Call minutes: https://www.w3.org/2018/03/13-ag-minutes.html#item02<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.w3.org_2018_03_13-2Dag-2Dminutes.html-23item02%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DI5BvMBel_d7yDetgxrMmkf1U58ofNYBs4BA2G-UUS2c%26s%3DTyD3rCLO3aRHxa4X9iXmKdEaYowVoS_AbZjcVT21oKI%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285680612&sdata=4gR%2B4Jf7HwJF8XJ%2Fbt2BH%2Bi83ocZWk8Iyd42UgAiW6s%3D&reserved=0>



If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.



Thanks,

AWK



Andrew Kirkpatrick

Group Product Manager, Accessibility

Adobe



akirkpat@adobe.com<mailto:akirkpat@adobe.com>

http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257C-257C54093524ef264326424008d51cd66c05-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636446629619786436-26sdata-3Dc5UP0xiniJIppvd6Esu1XA-252FbX1ykpABkhgCCmBp-252Fht8-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DI5BvMBel_d7yDetgxrMmkf1U58ofNYBs4BA2G-UUS2c%26s%3DKdT0Jv6CXFDj2rZub99NGsAvewpgwlhcDfIsaRuervY%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7Cf9658e361b384084e79808d58ab5ab4f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636567435285680612&sdata=X4GUanV%2F2%2BY8MxpuuWWCMrxti0AZXznKz%2Bm62A3OTls%3D&reserved=0>








--
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com<mailto:john.foliot@deque.com>

Advancing the mission of digital accessibility and inclusion