W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2010

Bug 8751 Auto scrolling pages

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 2 Sep 2010 11:48:38 -0500
Message-ID: <AANLkTikTsuMkTrV3sy84YL79NWoGLFHVjVOeD+DVarNy@mail.gmail.com>
To: gez.lemon@gmail.com, WAI-ua <w3c-wai-ua@w3.org>
Gez
RE: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8751
This is interesting. We do not have a Success Criteria specific to
scrolling. We have lots of SC for user control and user override of
many other things. Can you provide some example pages?
to me scrolling is vertical, and panning is horizontal.
I don't know of any HTML that causes auto scrolling (vertical).
Please enlighten me.
I know about the 'marquee' element for horizontal panning. That can be
stopped via the 'esc' key.
UAAG does not have any SC for preemptive stopping of HTML moving
things (animated gif, marquee, etc).
We are aware of javascript doing an auto-jump of focus to some
location on a page (e.g. first form element). Some might call that
auto-scrolling.
UAWG has difficulty with, and could use some input, javascript.
Although, the browser (UA) parses and causes actions on the content;
these are generally not actionable by the user using standard UA
interface controls.
For example, if the UA had a setting that anything that moves on a
page will be stopped when the page loads. So all animated gifs and
marquees would not move except on explicit user request (there would
need to be a mechanism to let the user know that image X is animated,
and does the user want to start it). I think this is doable.
Where things get difficult is when the auto-scrolling (panning,
jumping, whatever) is controlled by javascript, flash (although this
is a separate UA), or svg, or some other embedded object or script.
All of these things operate on the content but they operate outside
the knowledge of the UA. User setting and overrides have little
impact, because the UA does not know what is going on. And, there is
no implemented standard way for the UA settings to impact/override
actions/settings of native functionality (javascript) or embedded
objects (flash, etc.).
the only way I know of to stop something from automatically happening
on a page with javascript is to have javascript turned off.

The User Agent Working Group welcomes any input, ideas, concepts,
enlightenment, etc. in this area. It is a HUGE accessibility issue. We
would like to invite you to be a guest on a call or to join the group.
We need your expertise.

Jim

-- 
Jim Allan, Accessibility Coordinator & Webmaster

Texas School for the Blind and Visually Impaired

1100 W. 45th St., Austin, Texas 78756

voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/

"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 2 September 2010 16:49:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 2 September 2010 16:49:08 GMT