Re: New SC relating to notifications of content change (was Re: Some thinking around the orientation discussion)

On 12/05/2016 01:40, ALAN SMITH wrote:
> Help me here, I don’t see how 3.2.2 can be nullified. It is clearly
> stated in my opinion.
>
> So if I select a radio button and new fields appear, the content as well
> as the context has changed and I should be informed it is going to do so
> or else it is a failure of 3.2.2.
>
>
>         *3.2.2* On Input
>
> Level A
>
> Changing the setting of any user interface component does not
> automatically cause a change of context unless the user has been advised
> of the behavior before using the component.

I wouldn't say it's "nullified", but down to interpretation - likely 
comes down to what's considered a "major change" per 
https://www.w3.org/TR/WCAG20/#context-changedef

...which incidentally is a possible problem of subjective interpretation 
similar to what Gregg mentioned elsewhere in this thread

 > b) figure out if and how to word an SC that avoids the problems and 
is still testable   (e.g. you can’t say “significant change in content” 
— since an author would never know what an evaluator would consider 
significant.

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 Thursday, 12 May 2016 00:48:55 UTC