This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8751 - User should have ability to override automatic scrolling
Summary: User should have ability to override automatic scrolling
Status: VERIFIED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/TR/html5/editing.ht...
Whiteboard:
Keywords: a11y, a11ytf, a11y_display
Depends on:
Blocks:
 
Reported: 2010-01-14 15:33 UTC by Gez Lemon
Modified: 2010-10-04 14:54 UTC (History)
5 users (show)

See Also:


Attachments

Description Gez Lemon 2010-01-14 15:33:44 UTC
There should be a way for the user to override automatic scrolling. Automatic scrolling can make the cursor jump in ways that causes the user to go through extra steps to get back to what he was doing. This is a special hardship for some users. This is another example of allowing for full accessibility by giving the user a way to override inappropriate design.
Comment 1 Michael Cooper 2010-02-11 17:18:37 UTC
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
Comment 2 Ian 'Hixie' Hickson 2010-02-23 06:40:26 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: no spec change
Rationale: The spec already allows for this — that's why the scrolling requirement is a "should" and not a "must" (only bringing the user's attention to the given element is a "must", and the spec doesn't say how the UA is to do that).
Comment 3 Michael Cooper 2010-08-28 14:48:59 UTC
http://www.w3.org/2002/09/wbs/44061/20100520_bugs/results

Close as far as the HTML bug tracker is concerned. Refer the issue to be addressed in an external user interface recommendations document, initially to be coordinated by the User Agent Accessibility Guidelines Working Group.

http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0350.html