- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Wed, 15 Feb 2017 17:13:57 +0200
- To: Patrick H. Lauke <redux@splintered.co.uk>
- Cc: <w3c-wai-gl@w3.org>
Received on Wednesday, 15 February 2017 15:14:32 UTC
Hi PatrickThe main point here is not if you like this specific exception, but if we can bundle in an implication into a resolution where it disallows things that were not understood or agreed . It was not what was discussed and I think a real discussion is needed before we make a policy that blocks them. All the best Lisa Seeman LinkedIn, Twitter ---- On Wed, 15 Feb 2017 16:43:24 +0200 Patrick H. Lauke<redux@splintered.co.uk> wrote ---- My concern with having user testing as a means to trigger an exception would be that it's a slippery slope. Will other SCs get this type of exception? Does this in essence say "you as an author MUST follow this SC ... unless you can find 5 people that say you not following this SC is fine" This suggests to me as a reader that the normative advice in the SC is actually quite context-dependent, so perhaps shouldn't be normative advice in the first place unless the exact context can be unambiguously defined? P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 15 February 2017 15:14:32 UTC