- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 16 Jun 2020 17:08:56 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <AM7PR09MB41678904AE087E2BC91C0863B99D0@AM7PR09MB4167.eurprd09.prod.outlook.com>
Just to note that I emailed Justine off list, this was from a version mix-up and doesn’t affect the version CFCed. -Alastair From: Pascalides, Justine E Hello All, The exceptions to this SC are included in the Techniques section. I would like to see the exceptions included at the end of the main SC text (rather than in the Techniques section) to be consistent with the manner in which other SCs address exceptions. Best, Justine From: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> Sent: Tuesday, June 16, 2020 7:01 AM To: Wilco Fiers <wilco.fiers@deque.com<mailto:wilco.fiers@deque.com>> Cc: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: RE: Add Findable Help > But then how far should a tester look before concluding there is no contact mechanism? Within the conformance scope for that set of web pages / SPA. So where a site has sub-domains / blogs / 3rd party forms, if one of the listed things is available in that conformance scope then it needs to be present in a consistent location. > I don't think I understand what you mean. How is a "small content change" not a "content change"? It is a content change, but it is not ‘all content changes’. > I don't think we're going to get consistent test results if we leave "consistent location" undefined. I don’t we should try and define ‘consistent’, it already has a well understood meaning and I’m struggling to think of examples where it could be misconstrued. The only alternative I can think of is “relative location”. The other question is: Are these things that need working out before it goes for wide review? (I.e. can you live with it for this purpose.) We need to get the remaining SCs out for review, then we have time to deal with remaining issues. -Alastair ________________________________ 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 Tuesday, 16 June 2020 17:09:12 UTC