- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Fri, 10 May 2019 15:05:06 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <EAC575CE-B466-444B-AD21-AFF1BE55087C@nomensa.com>
+1 With a small note about assumptions as I’ve been reading the document in one way and discovered other people might have been reading it differently. (One person anyway.) Specifically for conformance, the introduction says: “Silver builds on the WCAG 2.0 Requirements of 2006.” (which includes conformance) “Silver wishes to advance the WCAG 2.0 Requirements of” (which includes “clear conformance”) Then it specifies which requirements it does not wish to ‘advance’. My interpretation is that a conformance model that meets *similar* goals to WCAG 2.0 is a requirement of Silver. The WCAG 2.0 version (https://www.w3.org/TR/wcag2-req/) does not use the same terminology that Silver would use, but I’m assuming that when the conformance model is fleshed out it will be incorporated as a requirement in Silver terms. I only add this as I was speaking to someone yesterday who had assumed differently, so I wanted to be clear about the +1. Cheers, -Alastair From: Andrew Kirkpatrick Call For Consensus — ends Tuesday, May 14th at 11am Boston time. The Working Group has discussed updates to the Silver requirements document following a review, discussion at a Face to Face meeting, and survey (https://www.w3.org/2002/09/wbs/35422/Silver_Requirements/results) and the chairs believe that there is a consensus to accept the requirements document. Requirements document: https://w3c.github.io/silver/requirements/ Call minutes: Silver requirements update<https://www.w3.org/2019/05/07-ag-minutes.html#item01> 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%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>
Received on Friday, 10 May 2019 15:05:32 UTC