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

RE: CFC - Focus for Working Group

From: White, Jason J <jjwhite@ets.org>
Date: Fri, 22 Feb 2019 15:02:34 +0000
To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <BN7PR07MB48496AA52C023386CCB44E5BAB7F0@BN7PR07MB4849.namprd07.prod.outlook.com>
-1 to the CfC.

I am concerned that WCAG 2.2 would absorb considerably more time and effort than anticipated on the part of the working group, for at best modest improvements in the accessibility of conforming content, constrained by the WCAG 2.x heritage (including the conformance scheme), and delaying progress toward completion of Silver.

I could live with a WCAG 2.2 effort if there were a strong rationale, statement of scope and drafts of success criteria to be added – sufficient to confine the required work within manageable limits.

Development of Silver should be moved into the full working group and not carried out primarily in a task force.

Phase 1: a suitable first objective for Silver would be to write a document that specifies equivalent requirements to WCAG 2.1 (without adding or removing requirements), but which is structured according to the Silver architecture and uses the Silver conformance scheme. (The architecture and conformance scheme would need to be completed and agreed upon.) This would eliminate the pressure to agree on new normative requirements while developing the approach to be carried forward in Silver. It would also provide a clear mapping of WCAG 2.1 conformance levels to Silver conformance statements to facilitate the transition.

Phase 2: in the second phase, establish considerably shorter update cycles for adding and changing requirements along the various “functional performance” dimensions of Silver – physical, sensory, cognitive, or whatever they turn out to be.

Requirements originating in the Authoring Tool Accessibility Guidelines or User Agent Accessibility Guidelines could be included in either phase 1 or phase 2, depending on the design chosen for the specification and considerations of scope.

All of phase 1 would need to be carried out within a charter period; having a draft of additional requirements suitable for the first phase 2-style revision would be a desirable objective as well, but not essential.

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Sent: Tuesday, February 19, 2019 3:32 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC - Focus for Working Group
Importance: High

Call For Consensus — ends Friday February 22nd at 3:30pm Boston time.

The Working Group has discussed how to focus the efforts of the group over the next 12-24 months and the proposal is that the WG can address the short-term need for improvements to Techniques and Understanding and begin to ramp-up work within the Working Group on Silver as well as commit to a WCAG 2.2, which will avoid the possibility of a large gap in time between the June 2018 WCAG 2.1 and Silver reaching Rec.

Proposed Schedule
March 2019-April 2019: 45% Techniques and Understanding, 45% Silver, 10% WCAG 2.2 (most drafting of new SC in ad hoc groups or TFs)
May 2019-forward: 45% WCAG 2.2, 45% Silver, 10% Techniques and Understanding maintenance

Survey: https://www.w3.org/2002/09/wbs/35422/WCAG22_yesno/results


Call minutes: https://www.w3.org/2019/02/19-ag-minutes.html#item11


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
Head of Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7Cjjwhite%40ets.org%7C7443c04983b74a85b87f08d696a9777a%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636862051934130826&sdata=xgy3LZN4Wdd%2FV22I3IjIcPkv0Aa1zs7FkeUwqFvL2Bg%3D&reserved=0>



________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________
Received on Friday, 22 February 2019 15:02:59 UTC

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