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

I thought about 4.1.2 also — but decided (as well) that it was about changing settings — not changing the page content. 

page content changing would be part of conformance — and was intended to be covered — but didnt think it needed to be said specifically. 
so Understanding WCAG 2.0  would be the place to explain that it is covered.   When we say contents of the page — we mean all contents - - as they become visible / presented. 

gregg

> On May 6, 2016, at 10:13 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote:
> 
> On 06/05/2016 13:48, Jonathan Avila wrote:
>>> I think WCAG currently lacks an SC that essentially says something
>>> along the lines of "When content/structure/functionality is changed
>>> dynamically (either automatically or as a result of a user
>>> interaction), ensure that this change is conveyed to the user"
>>> (probably single or double A).
>> 
>> I believe this would currently fall under SC 4.1.2.    That SC talks
>> about events and APIs and that is the likely way this information
>> would be communicated.
>> 
>> For example, F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to
>> not updating text alternatives when changes to non-text content occur
>> is mapped to SC 4.1.2
> 
> I interpret 4.1.2 as relating to the controls (making sure they're updated to reflect a change), but not directly about notifying the user about changes that happened elsewhere on the page (for cases like search results dynamically changing when a user ticks/changes filter options above them or something).
> 
> 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
>