RE: Proposed SC on notification of dynamic changes to apage



From: David MacDonald [mailto:david@can-adapt.com]
Sent: Saturday, June 25, 2016 11:24 AM

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
[Jason] In essence, yes.

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: ...

[Jason] I like it. I’m not sure that “by the page” conveys the right idea. Suppose we say “whether or not initiated by the user” just to cover all cases unambiguously.


________________________________

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.

________________________________

Received on Saturday, 25 June 2016 15:29:18 UTC