Edit ISSUE-19: Should h69 be merged into h42?

Nickname:

Title:

State:

Product:

Raised By:

Description:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. ISSUE-19: Should h69 be merged into h42? (from sysbot+tracker@w3.org on 2014-05-20) (from sysbot+tracker@w3.org on 2014-05-20)

Related notes:

[AWK]: See minutes from http://www.w3.org/2014/05/20-wai-wcag-minutes.html#item01

21 May 2014, 13:42:52

Sailesh on July 7, 2014:
I re-reviewed the minuted comments at
http://www.w3.org/2014/05/20-wai-wcag-minutes.html#item01.
I strongly feel H69 should be merged into H42 and a single technique should reference both SCs.
Reasoning:
The concept about jumping to a particular section is introduced almost after 10 sentences in the description of H69. So it does not seem to be the main idea in the description. The first sentence reads "The objective of this technique is to use section headings to convey the structure of the content" ... no reference to skip-nav.
Everything that precedes it describes how headings expose structure and info-relationships. i.e. SC 1.3.1.
Consider a page that has no headings and hence no heading markup.
So is H69 suggesting that headings should be inserted (off-screen?) so that SR users can jump to it?
So if a page has main nav, left nav, right side content, main content, footer content then is the expectation that there should be a heading preceding "each section" to help SR users? Why each section? And should there be 5 skip links from the top?
And is this the expectation even if the UI does not support visible headings on the page?
Only SC 2.4.10 (AAA) may require "Providing heading elements at the beginning of each section of content", and that SC is not referenced by H69.
SC 2.4.1 does not require ability to jump to every section on the page but only to help users bypass repetitive blocks.

H42 also suggests ability of SRs to naviggate to headings helps efficient navigation.
The duplication of content across the two techniques may make the reader wonder what's the difference.
So when H42 is used i.e. h-tags to mark up heading-content on a page, it will help one to skip past nav blocks to main content and thus satisfy SC 2.4.1 too.

Sailesh Panchang, 7 Jul 2014, 20:00:14

Sailesh on July 7, 2014:
I re-reviewed the minuted comments at
http://www.w3.org/2014/05/20-wai-wcag-minutes.html#item01.
I strongly feel H69 should be merged into H42 and a single technique should reference both SCs.
Reasoning:
The concept about jumping to a particular section is introduced almost after 10 sentences in the description of H69. So it does not seem to be the main idea in the description. The first sentence reads "The objective of this technique is to use section headings to convey the structure of the content" ... no reference to skip-nav.
Everything that precedes it describes how headings expose structure and info-relationships. i.e. SC 1.3.1.
Consider a page that has no headings and hence no heading markup.
So is H69 suggesting that headings should be inserted (off-screen?) so that SR users can jump to it?
So if a page has main nav, left nav, right side content, main content, footer content then is the expectation that there should be a heading preceding "each section" to help SR users? Why each section? And should there be 5 skip links from the top?
And is this the expectation even if the UI does not support visible headings on the page?
Only SC 2.4.10 (AAA) may require "Providing heading elements at the beginning of each section of content", and that SC is not referenced by H69.
SC 2.4.1 does not require ability to jump to every section on the page but only to help users bypass repetitive blocks.

H42 also suggests ability of SRs to naviggate to headings helps efficient navigation.
The duplication of content across the two techniques may make the reader wonder what's the difference.
So when H42 is used i.e. h-tags to mark up heading-content on a page, it will help one to skip past nav blocks to main content and thus satisfy SC 2.4.1 too.

Sailesh Panchang, 7 Jul 2014, 20:15:12


Alastair Campbell <acampbell@nomensa.com>, Rachael Bradley Montgomery <rmontgomery@loc.gov>, Charles Adams <charles.adams@oracle.com>, Chairs, Michael Cooper <cooper@w3.org>, Shawn Henry <shawn@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $