- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 23 Feb 2016 20:15:49 +0000
- To: ALAN SMITH <alands289@gmail.com>, 'GLWAI Guidelines WG org' <w3c-wai-gl@w3.org>
- Message-ID: <16B9460917C67BE0.8ECF7A6F-8DEE-4B94-822C-CA3D19F45033@mail.outlook.com>
Hi Alan, I just find the longer version harder to parse, could it be shortened to: Ensure that web pages which conform to a WGAG 2.0 extension also conform to WCAG 2.0 The web page that is the thing being tested (although not everyone likes that terminology), I'm not sure what "dependent code/feature" means in this context. Kind regards, Alastair _____________________________ From: ALAN SMITH <alands289@gmail.com<mailto:alands289@gmail.com>> Sent: Tuesday, February 23, 2016 6:52 pm Subject: RE: Coming to a decision on 2.2 To: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>, 'GLWAI Guidelines WG org' <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Alastair, It is an important consideration that needs to be communicated, even if it takes a little longer sentence. Yes, the paragraph below it does explain it. To me, it just does not sound right without something else in the main 2.2 sentence to make that "without" thought a primary communicated concern. People will copy/paste, share and quote 2.2 and may or will not include the underneath paragraph. Alan Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Alastair Campbell<mailto:acampbell@nomensa.com> Sent: Tuesday, February 23, 2016 1:06 PM To: ALAN SMITH<mailto:alands289@gmail.com>; 'GLWAI Guidelines WG org'<mailto:w3c-wai-gl@w3.org> Subject: Re: Coming to a decision on 2.2 Hi Alan, To be honest I copied the current wording and chopped a couple of bits out ;-) You're suggest would make for a very long heading (which is quite long as it is), are you sure the paragraph underneath doesn't explain it well enough? I took the text out of a structured format, perhaps you didn't notice it was a heading? Kind regards, -Alastair From: ALAN SMITH I should have added the following in bold and underlined. 2.2 Ensure that web pages which conform to WCAG 2.0 with an extension also conform to WCAG 2.0 if the extension dependent code/feature is not part of the review. Alan
Received on Tuesday, 23 February 2016 20:16:23 UTC