Re: CFC: Change of Content SC

+1 to Jason.

While I generally believe that this SC is headed in the right direction, I
also agree with Gregg that there remains some serious outstanding questions
(game or simulation & continual changes of content). At a minimum, I would
exempt any multi-media (as media already has a requirement - SC 1.2.3 -
that essentially covers the use-case needs) - but does "media" here also
include animation and <canvas>-based content as well?


I can live with advancing this into the current editor's draft, but as
Jason notes we should be flagging this one as having some outstanding
issues in the Draft.

JF

On Tue, May 30, 2017 at 2:04 PM, White, Jason J <jjwhite@ets.org> wrote:

> Where we publish a proposal that has known (and potentially challenging)
> unresolved issues, we should flag the issues in a note to reviewers of the
> public working draft. The note is typically placed adjacent to the text of
> the proposal in the draft. This practice encourages reviewers to
> consider, and comment on, the issues that have been identified.
>
>
>
> *From:* Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
> *Sent:* Tuesday, May 30, 2017 2:47 PM
> *To:* Gregg C Vanderheiden <greggvan@umd.edu>
> *Cc:* w3c-waI-gl@w3. org <w3c-wai-gl@w3.org>
>
> *Subject:* Re: CFC: Change of Content SC
>
>
>
> Gregg,
>
> The continual changes concern has been raised and discussed (
> https://www.w3.org/2017/05/30-ag-minutes.html#item04) and while we don’t
> believe that we have the perfect solution right now we feel like it is
> worth getting this SC into the Editor’s draft so we can get additional
> comments.
>
>
>
> Regarding your other question, this is not just in response to a user
> action. A news site might add articles on some interval and that is in
> response to time or external events, and in that situation the site would
> need to provide notification that the content was changed.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *Gregg Vanderheiden <greggvan@umd.edu>
> *Date: *Tuesday, May 30, 2017 at 14:31
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2FSCreview_May_17%2Fresults%23xq10&data=02%7C01%7C%7Ce6860c3219a64497531f08d4a78a21ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317659151993986&sdata=XDd3C%2FoLkxYh0Zp9GDHwBlOyWsfrqCT00eprA9BCzi4%3D&reserved=0>
>
>
> Call minutes: https://www.w3.org/2017/05/30-ag-minutes.html#item04
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F05%2F30-ag-minutes.html%23item04&data=02%7C01%7C%7Ce6860c3219a64497531f08d4a78a21ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317659151993986&sdata=qvWrVqal3tmBNIJEGGPHj8UH2ECQxcZfZ0RMTmGh8%2F8%3D&reserved=0>
>
>
>
>
> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fchange-of-content_ISSUE-2%2Fguidelines%2F%23change-of-content&data=02%7C01%7C%7Ce6860c3219a64497531f08d4a78a21ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317659151993986&sdata=NEM9tqww%2Bi2UM0%2Bu6JOGqg2FkS3a0Dptj2DwdXnqDOE%3D&reserved=0>
>
>
>
>
> 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
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7Ce6860c3219a64497531f08d4a78a21ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317659151993986&sdata=XPxMsjofk%2FX1X0Lc1%2Bx2R%2BFEVbBoCv5yqcEWi1%2FeGm0%3D&reserved=0>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7Ce6860c3219a64497531f08d4a78a21ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317659151993986&sdata=XPxMsjofk%2FX1X0Lc1%2Bx2R%2BFEVbBoCv5yqcEWi1%2FeGm0%3D&reserved=0>
>
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
> Thank you for your compliance.
> ------------------------------
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion