Re: CFC: Change of Content SC

Looks interesting.

But before we reach consensus on this    -  a couple questions and suggestion (depending on answer to question) 
. 

?? Do we have techniques for doing this?  

For example in a game or simulation - there will continual changes of content.   There is no exception for this  — so is there a technique that should be used in these situations  to indicate that there are continuously changing content?

?? Or is this ONLY supposed to apply to content that changes in response to a user action.   

That would make sense - but the current language does not say this 

current language 
Programmatic notification is provided for each change of content <> that indicates a user action was taken or that conveys information, unless one or more of the following is true

Perhaps something like 

Programmatic notification is provided for each change of content <> that RESULTS FROM A USER ACTION AND THAT indicates a user action was taken or that conveys information, unless one or more of the following is true:


??  If you DON’T mean changes due to user action — then for dynamic content (constantly changing) content is a simple notice someplace that says that the page has continually changing content sufficient?  or would the page need to stream a constant flow of notifications through some mechanism that is supported by AT? 

 


Gregg

Gregg C Vanderheiden
greggvan@umd.edu




> On May 30, 2017, at 1:12 PM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
> 
> Call For Consensus — ends Thursday June 1rd at 1:00pm Boston time.
> 
> The Working Group has reviewed and approved a new Success Criterion for inclusion in the Editor’s Draft: Change of Content, at level AA, with the goal of obtaining additional input external to the working group.
> 
> Survey results: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/results#xq10 <https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/results#xq10> 
> Call minutes: https://www.w3.org/2017/05/30-ag-minutes.html#item04 <https://www.w3.org/2017/05/30-ag-minutes.html#item04> 
> 
> The new SC can be reviewed here, in the context of the full draft: 
> https://rawgit.com/w3c/wcag21/change-of-content_ISSUE-2/guidelines/#change-of-content <https://rawgit.com/w3c/wcag21/change-of-content_ISSUE-2/guidelines/#change-of-content> 
> 
> If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.
> 
> Thanks,
> AWK
> 
> Andrew Kirkpatrick
> Group Product Manager, Standards and Accessibility
> Adobe 
> 
> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk <http://twitter.com/awkawk>
> Thanks,
> AWK
> 
> Andrew Kirkpatrick
> Group Product Manager, Accessibility
> Adobe 
> 
> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk <http://twitter.com/awkawk>