sounds like the right idea yea — it is always the "how do you define “important” in a quantitative way?” that killed us in trying to create these things. Yet you can’t know if you met this without it. gregg > On May 9, 2016, at 9:03 AM, Alastair Campbell <acampbell@nomensa.com> wrote: > > 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:54:01 UTC