Correct. I don’t things we want to alert the reader to any minor changes that are not considered changes in context. (e.g. if you check a box - it might change color if you check a box - it might open up another question below (popping an alert box up for each would drive people crazy — and since the person is moving down to it next..) if it changes content above in any important way - then that changes the context of the page we used “change of context” to separate important from unimportant changes… since you don’t want an alert each time the clock rolls over or ticker on the page changes content. gregg > On May 6, 2016, at 12:07 PM, David MacDonald <david100@sympatico.ca> wrote: > > Jonathan and Gregg feel this is covered. I don't remember any sustained discussion about notifying users of changes on a page in WCAG except changes in context where the author moves the user focus or as patrick says, changes in the role state value of an interactive control ...I'm my reports and training, I've been marking it as a best practice to notify users of changes to the page, but haven't been logging failures. I'd have to search through the WCAG 2 minutes archives 2000-2008, but I don't remember us addressing additions/deletions specifically, and mapping it to a success criteria. Perhaps I missed a meeting where this happened. It wasn't very common back then... >
Received on Friday, 6 May 2016 17:49:45 UTC