Re: Proposed SC on notification of dynamic changes to apage

HI Jason

When you say extend 4.1.2, you mean that it apply to more than changes set
by the user, but also changes set by the page

I think there is another limiting factor about 4.1.2 and that is that it
applies to  just "components". Currently, it requires "components" to
provide notification of updates, so I would fail a shopping cart that did
not have a live region to say it was updated. However, I think our
intention when writing 4.1.2 was to ensure custom widgets made out of spans
and divs still had an accessible name etc...

For that reason I'm shy about trying to extend it to the entire page AND to
non-user actions. I think we might be better introducing a new SC. The
proposed language of the new SC covers user actions AND page actions and it
is specifically about notification rather than what we find in 4.1.2 which
is primarily about NAME, ROLE, VALUE.

I've introduce the phrase "whether initiated by the user or by the page"

*SC x.x.x.x Change of content:* Programmatic notification is provided for
each change in content that indicates an action was taken or that conveys
information, whether initiated by the user or by the page, unless one or
more of the following is true: ...

Does that in combination with the loading/busy SC cover it.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Sat, Jun 25, 2016 at 11:24 AM, David MacDonald <david@can-adapt.com>
wrote:

> HI Jason
>
> When you say extend 4.1.2, you mean that it apply to more than things set
> by the user, but also changes set by the page
>
> I think there is another limiting factor about 4.1.2 and that is that it
> applies to  just "components". I Currently it requires "components" to
> provide notification of updates, so I would fail a shopping cart that did
> not have a live region to say it was updated. However, I think our
> intention when writing 4.1.2 was to ensure custom widgets made out of spans
> and divs still had an accessible name etc...
>
> For that reason I'm shy about trying to extend it to the entire page AND
> to non-user actions. I think we might be better introducing a new SC. The
> proposed language of the new SC covers user actions AND page actions and it
> is specifically about notification rather than what we find in 4.1.2 which
> is primarily about NAME, ROLE, VALUE.
>
> I've introduce the phrase ", whether initiated by the user or by the
> page" Does that in combination with the loading/busy SC cover it.
>
> *SC x.x.x.x Change of content:* Programmatic notification is provided for
> each change in content that indicates an action was taken or that conveys
> information, whether initiated by the user or by the page, unless one or
> more of the following is true: ...
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> *  Adapting the web to all users*
> *            Including those with disabilities*
>
> If you are not the intended recipient, please review our privacy policy
> <http://www.davidmacd.com/disclaimer.html>
>
> On Sat, Jun 25, 2016 at 10:43 AM, White, Jason J <jjwhite@ets.org> wrote:
>
>>
>>
>>
>>
>> *From:* David MacDonald [mailto:david@can-adapt.com]
>> *Sent:* Saturday, June 25, 2016 7:33 AM
>>
>> Thanks Rachel and Jason
>>
>>
>>
>> I think this is an important hole to plug and it's not covered in the
>> current SC proposal ... I've tried to weave it into the existing proposal,
>> but it is beginning to get a bit long and winding. I think it could stand
>> alone as another success criteria. How about this?
>>
>>
>>
>> *SC x.x.x Loading/Busy:* Programmatic notification is provided for each
>> loading or busy signal which is visually conveyed, after the page has been
>> initially loaded (Level AA)
>>
>>
>> *[Jason] This elegantly solves the immediate problem. My wider concern,
>> nevertheless, is that notification of events resulting from changes other
>> than user actions isn’t covered adequately in WCAG 2. For example, it isn’t
>> obvious that authors would be required to use ARIA liv regions correctly to
>> provide notification of, for example, arriving instant messages, news
>> artcles, etc, which do not result from users’ actions.*
>>
>> This is why I suggested a new requirement that would extend 4.1.2.
>> Alternative suggestions (or arguments that these scenarios are already
>> addressed) are most welcome, as always.
>>
>>
>>
>> ------------------------------
>>
>> 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.
>> ------------------------------
>>
>
>