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

I’m not sure I understand exactly what you are asking — but

If I were clicking on a button to add something to my basket.. and the only change is a notification at the top of  the page that there is now one more thing in my basket — I would not think call THAT a change of context.   Just  a change of data on the page - and a change I created.   Any time  I want to know the answer to that question - I could go to the top of the page and read it.   On some pages (e.g. Amazon) that information isnt available to anyone if the page is scrolled up )

If there is a pop up — it should be large enough that it won’t be missed if the page is enlarged.    And programmatically obvious    (ESPECIALLY IF IT IS MODAL -  but also important otherwise)
(this IS a change of context and covered by the existing SC

If the user does something and the change is a completely predictable outcome - then we don’t treat it as a change in context that the user needs notification of.  (e.g. expand all   or    any link that takes you to a new page ) 

gregg

> On May 9, 2016, at 3:18 AM, Alastair Campbell <acampbell@nomensa.com> wrote:
> 
> Gregg wrote:
>> "we used “change of context” to separate important from unimportant changes…  since you don’t want an alert each time the clock rolls over  or ticker on the page changes content.”
> 
> So I can see how changing search results by a filter (onchange) gets caught, but how about the add to basket scenario?
> 
> E.g. You are in a product page or search results page on an ecommerce site, select ‘add to basket’, which updates a widget in the header.
> 
> For example, one of the lower products on this page: http://www.next.co.uk/g312266s4
> BTW I’m not saying that site is accessible except for this issue, I’m using this as a visual / magnification example.
> 
> I’m fairly sure that site added the pop-up by the basket due to the inherent usability issue, but that ‘fix' doesn’t help magnification / screen reader users (unless they use ARIA live, which they don’t appear to).
> 
> That wouldn’t seem to qualify as a change of context, and it happens due to a user-action, what would that fail under at the moment?
> 
> Cheers,
> 
> -Alastair