- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Fri, 6 May 2016 16:20:24 +0100
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
- Cc: "lisa.seeman" <lisa.seeman@zoho.com>
On 06/05/2016 15:56, Gregg Vanderheiden wrote: > > I think this is essential - but I think it is already covered. Where? Under which SC would this fall? To clarify, this is not (I think) 4.1.2 as that SC relates to updating/notifying user of change to interactive elements/controls (so that if their status changes, or their actual function/label, that this is done in a way that then conveys the change programmatically to users), not about changes in the overall document/structure/content elsewhere on the page. > If not - then it would need to be clarified in connection with > conformance rather than as another SC. > If this isn’t obvious/clear already (and evidently it isnt) then I > THINK it could be clarified in Understanding WCAG 2.0 — and be done > immediately with the next publication of that document. > > I and Loretta and David and others can confirm that it was the intent > and understanding of the group that if it changed - it should remain > accessible. > > > does this help? > > > > /gregg/ -- 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 Friday, 6 May 2016 15:23:08 UTC