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

Hi Gregg,

I guess I’m saying that it isn’t a change of context, but it is an issue that should be covered by WCAG (but isn’t yet). One that I’ve seen in usability testing whenever this type of feature is used.

The pop-up I mentioned was a small one Next (the site I linked to) have added to draw attention to the change in the basket, probably because it was a problem for everyone. However,  it wouldn’t work for people using magnification or a screenreader therefore it is an accessibility issue. The basket issue doesn’t always (or even often) have this additional pop-up, sometimes it just updates the basket with no notification or sign of change where your focus is.

In old school usability terms people have a “Locus of attention” when using screens, if something appears out of your focus area you tend not to notice it. It becomes an accessibility issue with magnifiers because of the narrow visual field, and screenreaders if it is above (or far away from) the focus point.

The solution for screenreader users would be ARIA-live with a notification of the update (e.g. "Basket updated, total $84”), but I don’t think magnifiers have the ability to highlight updates outside of the focus area? (I can imagine a computer-game style arrow pointing to the updated region!)

Cheers,

-Alastair


From: Gregg Vanderheiden

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


  1.  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 )

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