- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 9 May 2016 14:03:16 +0000
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- CC: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
Jonathan Avila” wrote: >There is always a balance between between too much or too little feedback. Agreed, and that is partly why I think it needs to be done on the author/developer side of things. An automated solution (e.g. user-agent detecting changes) would be too blunt, it needs to take account of the context. A straw-man SC could be: If the page is updated away from the “Point of regard” [1], and the change is important to their task, the user must be notified. The middle part of that (about task) isn’t workable, but that’s what I’m trying to get at. Cheers, -Alastair 1] I’m not a big fan of this term, but it has the right meaning for this point. http://w3c.github.io/low-vision-a11y-tf/requirements.html#point-of-regard-and-proximity
Received on Monday, 9 May 2016 14:22:18 UTC