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 24992 - clarify that use of all h1's is not encouraged while use of properly nested headings is
Summary: clarify that use of all h1's is not encouraged while use of properly nested h...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, CR
Depends on:
Blocks:
 
Reported: 2014-03-10 19:42 UTC by steve faulkner
Modified: 2014-03-12 10:01 UTC (History)
4 users (show)

See Also:


Attachments

Description steve faulkner 2014-03-10 19:42:16 UTC
http://www.w3.org/TR/html5/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements
the W3C HTML5 CR presents two approaches, one using heading elements by nesting depth and one using <h1> inside <section>, and adds: "Authors might prefer the former style for its terseness, or the latter style for its convenience in the face of heavy editing; which is best is purely an issue of preferred authoring style." I cannot see this as encourageing, even mildly, the use of the former approach (which is surely much more practical).
Comment 1 steve faulkner 2014-03-10 20:21:07 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: modified heading levels used in example to reflect outline depth.
Rationale: The spec encourages authors to use heading levels that reflect their outline depth, this change in the example supports the advice.