Re: New SC relating to notifications of content change (was Re: Some thinking around the orientation discussion)

I've defined "Change in content" to be "changes that occur to a web page
after it's been delivered to the user agent. "

This would exclude links that take the user somewhere else or that don't
add/remove content. Links don't generally change content, they change the
user's location.

I see a small problem with my definition of change of content ... I think
we also want to include changes to a page from server side refreshes also
(which should be discouraged unless its AJAX where the page doesn't reload
and sent the user back to the top of the page)

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 Wed, May 11, 2016 at 4:41 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 11/05/2016 21:33, Sailesh Panchang wrote:
>
>> "User awareness" is  used in the same manner as is used in the
>> glossary explaining "change of context". Any other alternative
>> wording?
>> The SC will need a note to clarify that this does not apply to links
>> and such  listed in the exclusions listed  in that email.
>>
>
> Ditto for "regular" forms, whose submit action would reload the current
> page / load another page.
>
> Would the exclusion be, in very broad strokes, along the lines of "unless
> the change in content as a result of user action is expected and follows
> standard behavior (e.g. activation of a link resulting in a new webpage
> being loaded)" or similar?
>
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>