W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: CFC: Change of Content SC

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Wed, 7 Jun 2017 10:43:25 -0400
Message-ID: <CAJi9Cqo062JrmP8+bh=bzUqj_wocNGhM6vR4OChuXxn7GNcmug@mail.gmail.com>
To: Andrew Kirkpatrick <akirkpat@adobe.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Kindly record this following comment  as part of the CFC as the
concerns raised by me on this thread have not been addressed.
Content on a Web page  changing in response to user action is not new.
This is a characteristic of dynamic pages and has been around for a
dozen years plus.
WCAG 2.0  covers dynamic content. This is   referenced in the normative text:
1. Changes of context cover content changes "if made without user
awareness, can disorient users who are not able to view the entire
page simultaneously". So 3.2.1 and 3.2.2 address some types of dynamic
content.
2. SC 4.1.2 covers another block : "notification of changes to these
items is available to user agents, including assistive technologies".

There are a couple of  ARIA techniques that  reference WCAG 2 SC for
added content:
ARIA18: Using role="alertdialog" creates a notification.
ARIA19: Using ARIA role=alert or Live Regions to Identify Errors

Also, David's last email above notes: "I can see the rational for
added content to components in 4.1.2".

Therefore one really may need to apply one or more of the existing SCs
 to evaluate the new content added to a page as a result of user
action. One can apply 4.1.2 / 3.3.1  as ARIA 18/19 suggest  as well as
ensure compliance with 1.3.1, 1.3.2, 2.4.3, 3.2.1, 3.2.2 as the
situation demands.

Thanks and best wishes,
Sailesh Panchang
Principal Accessibility Consultant
Deque Systems Inc
Phone 703-225-0380 ext 105
Mobile: 571-344-1765


On 6/6/17, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
> AGWG’ers,
>
> As we have received substantially positive feedback leading up to this CfC,
> this CfC is agreed on as a consensus opinion of the working group.
>
> In addition, in response to comments we will also add a reviewer note to the
> SC to clarify that there are outstanding questions that the Working Group is
> interested in additional feedback on related to how to best handle content
> with continual changes of content such as games and simulations.
>
> This decision will be recorded at
> https://www.w3.org/WAI/GL/wiki/Decisions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Fwiki%2FDecisions&data=02%7C01%7C%7C1ab6006ec2be48e88f9008d4a210961e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311639507586899&sdata=IafGoKjeQf7zBqxVj8m380hh8%2BWgU1VfPa2tZjq0Bx8%3D&reserved=0>
>
> Thanks,
> AWK
>
> Andrew Kirkpatrick
> Group Product Manager, Accessibility
> Adobe
>
> akirkpat@adobe.com
> http://twitter.com/awkawk
>
> From: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
> Date: Tuesday, May 30, 2017 at 13:12
> To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
> Subject: CFC: Change of Content SC
> Resent-From: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
> Resent-Date: Tuesday, May 30, 2017 at 13:13
>
> 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%7C6a7d4a78043f48f5dab308d4a77f44dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317612434615141&sdata=Okf0JE8v9L3KHEtTV1WoBkkynnQOt01S72abhaualTk%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%7C6a7d4a78043f48f5dab308d4a77f44dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317612434615141&sdata=%2F3FA5IQMojJ3KxpURZeEw9kaQaai2PlZ7n7liDnuPiQ%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%7C6a7d4a78043f48f5dab308d4a77f44dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317612434615141&sdata=yJZ%2FnwEScLAYTlwQ2eZ4cxPEWU6dl6rRGhwGyCo2rcs%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<mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C6a7d4a78043f48f5dab308d4a77f44dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317612434615141&sdata=WXIOlDgSmjs8RA701PHIwW2a41iGdgiljy4cZ6ePY9w%3D&reserved=0>
> Thanks,
> AWK
>
> Andrew Kirkpatrick
> Group Product Manager, Accessibility
> Adobe
>
> akirkpat@adobe.com<mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C6a7d4a78043f48f5dab308d4a77f44dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636317612434615141&sdata=WXIOlDgSmjs8RA701PHIwW2a41iGdgiljy4cZ6ePY9w%3D&reserved=0>
>


-- 
Sailesh Panchang
Principal Accessibility Consultant
Deque Systems Inc
Phone 703-225-0380 ext 105
Mobile: 571-344-1765
Received on Wednesday, 7 June 2017 14:43:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:13 UTC