- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 9 May 2016 08:18:16 +0000
- To: Gregg Vanderheiden <gregg@raisingthefloor.org>
- CC: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, "GLWAI Guidelines WG org" <w3c-wai-gl@w3.org>
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
Received on Monday, 9 May 2016 08:55:52 UTC