- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Fri, 6 May 2016 15:50:51 +0000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, "GLWAI Guidelines WG org" <w3c-wai-gl@w3.org>
- CC: lisa.seeman <lisa.seeman@zoho.com>
Patrick wrote: > "Where? Under which SC would this fall? To clarify, this is not (I think) 4.1.2 as that SC relates to updating/notifying user of change to interactive elements/controls ... not about changes in the overall document/structure/content elsewhere on the page." In support of this idea, there are two things I over-emphasise in training compared to the guidelines: 1. Off-screen changes for people using magnifiers (not covered). 2. Plain language (under 3.1 at AAA, but it actually helps almost everyone). I do that having seen issues related to these come up a lot in usability testing. For example, on an ecommerce site you add an item to your basket and the indicator that it has worked is away from your focus. If affects everyone to some degree, but if it is completely off-screen (or if you are using a screen reader and no ARIA live) you have no idea. I'd been meaning to check if the LVTF had covered this scenario, perhaps not? I think one success criteria could cover the magnifier and screen reader aspects if written well, as it is about notifying someone of a change away from the keyboard and/or visual focus. It can't just be covered by the user-agent as the meaning of the change will vary depending on the site and functionality of the site. Automatic notification would be overwhelming, and it probably needs some indication of what the change actually means. Cheers, -Alastair
Received on Friday, 6 May 2016 15:51:21 UTC