| Title | Page starts scrolling down at user request but cannot be stopped |
|---|---|
| Description | A document with content that is too long to fit on most current computer displays. The document starts scrolling down when the user activates the ‘start scrolling’ button at the top of the document. There is no mechanism to stop the scrolling once it has started; other user actions, such as pressing the "Home" key, only take effect after the scrolling has ended. However, the scroll effect does not come back until the page has been refreshed. (If the entire content fitted into the browser window, no scrolling would be visible; hence the length of the document.) |
| Creator | BenToWeb (Christophe.Strobbe@…) |
| Rights | Copyright BenToWeb 2004-2007 |
| Language | English |
| Date | 2005-09-30 |
| Status | validated |
Technologies are markup languages or data formats. If the technology is a markup language, “features” refers to elements and attributes.
XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition)
Feature: script
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification:
The script element.
Standard ECMA-262: ECMAScript Language Specification
Feature: scrollTo().
Technical specification:
The scrollTo() method.
This test case is intended to fail because there is no mechanism to stop or pause the scrolling. Only the scrolling is tested here, not the table structure or other aspects of the content.
Accessibility expert.
“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.
The test case fails the following success criterion at line 31, column 12: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#time-limits-pause.
The test case fails the following success criterion at line 31, column 49: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#time-limits-pause.
The test case fails the following success criterion at line 17, column 1: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#time-limits-pause.
The page starts crolling when the user clicks the button at the top of the page without giving the user the opportunity to stop the scrolling.
This test case maps to failure F16: Failure of SC 2.2.3 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content.
(Success criterion 2.2.3 does not exempt content that scrolls on user request.)
The test case fails the following success criterion at line 31, column 12: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#time-limits-pause.
The test case fails the following success criterion at line 31, column 49: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#time-limits-pause.
The test case fails the following success criterion at line 17, column 1: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#time-limits-pause.
The page starts crolling when the user clicks the button at the top of the page without giving the user the opportunity to stop the scrolling.
The test case fails the following success criterion at line 31, column 12: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#time-limits-pause.
The test case fails the following success criterion at line 31, column 49: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#time-limits-pause.
The test case fails the following success criterion at line 17, column 1: http://www.w3.org/TR/2006/WD-WCAG20-20050630/#time-limits-pause.
The page starts crolling when the user clicks the button at the top of the page without giving the user the opportunity to stop the scrolling.