W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2018

RE: CFC - Decision to keep 1.3.4 where it is

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Thu, 15 Mar 2018 20:32:22 +0000
To: WCAG <w3c-wai-gl@w3.org>
Message-ID: <BN6PR03MB2513C93E113AF980B50AF692F1D00@BN6PR03MB2513.namprd03.prod.outlook.com>
+1 to keep 1.3.4 where it is – 1.3 is the better place as it fits very nicely with the intent of the SC to “ Create content that can be presented in different ways <https://www.w3.org/TR/WCAG20/#content-structure-separation> “


Jonathan Avila
Chief Accessibility Officer
Level Access
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 11:26 AM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC - Decision to keep 1.3.4 where it is
Importance: High

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

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.


Andrew Kirkpatrick
Group Product Manager, Accessibility


Received on Thursday, 15 March 2018 20:32:53 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:22 UTC