| Title | Set of web pages with heading elements at the beginning of each section of content |
|---|---|
| Description | A set of web pages - the web site of the fictitious newspaper The Narnia Times - that has a top navigation section at the top of each page. Each major section of each page - Site Navigation, Today's Picks (on the home page), articles in main content area - have a heading element, so users can navigate from section to section by means of the headings, and thus also skip the top navigation. However, the heading for the top navigation is hidden (moved to the left of the visible areas by means of a negative margin in CSS). |
| Creator | BenToWeb (Christophe.Strobbe@…) |
| Rights | Copyright BenToWeb 2004-2007 |
| Language | English |
| Date | 2006-10-11 |
| 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: h2
(namespace: http://www.w3.org/1999/xhtml)
.
Technical specification:
Headings: The H1, H2, H3, H4, H5, H6 elements
.
This test case is intended to pass because the heading elements allow the user to navigate by headings and thus skip the top navigation.
Accessibility expert.
“Rules” refer to success criteria in WCAG 2.0, checkpoints in WCAG 1.0 and similar requirements.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 22, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 57, column 3) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 59, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 60, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 62, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 59, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 60, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 59, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 77, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
The test case passes (line 68, column 5) the following success criterion: http://www.w3.org/TR/2007/WD-WCAG20-20070517/Overview.html#navigation-mechanisms-title.
Users can bypass the top navigation by navigating the headings. Opera users can use the S and W keys to navigate to the next and previous heading, respectively. Firefox users can use a plugin or the "Heading Navigation Greasemonkey User Script" (http://juicystudio.com/article/heading-navigation-greasemonkey-user-script.php).
This test case maps to technique H69: Providing heading elements at the beginning of each section of content.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 22, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 57, column 3: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 59, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 60, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 62, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 59, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 60, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 59, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 77, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
The test case fails the following success criterion at line 68, column 5: http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html#navigation-mechanisms-title.
Users can bypass the top navigation by navigating the headings. Opera users can use the S and W keys to navigate to the next and previous heading, respectively. Firefox users can use a plugin or the "Heading Navigation Greasemonkey User Script" (http://juicystudio.com/article/heading-navigation-greasemonkey-user-script.php).
This test case maps to technique H69: Providing Heading elements at the beginning of each section of content (http://www.w3.org/TR/2006/WD-WCAG20-TECHS-20060427/Overview.html#H69).
Online version: sc2.4.1_l1_005.