1. Normative Document Representation

1. normativeVersionTest At least one normative representation MUST be available for requests that use the "This Version" URI. More than one normative representation MAY be delivered in response to such requests. A "This Version" URI MUST NOT be used to identify a non-normative representation.
2. valideHTMLTest recursive All normative representations MUST validate as one of the following: HTML 4.x, or some version of XHTML or XHTML+RDFa that is a W3C Recommendation. HTML5 is also permitted with the following limitations:
   • Inline markup for SVG 1.1 or MathML 2.0 is permitted but only with a (fallback) alternative.
   • If the HTML5 validator issues content warnings, the publication request must include rationale why the warning is not problematic.
   Note: Please consider how your content will render in browsers that do not support HTML5.
3. Visual styles SHOULD NOT vary significantly among normative alternatives.

Note: Serving two representations at the "this version" URI is an assertion by W3C that the documents are equivalent for the purposes of conveying the requirements of the document. In practice, the Comm Team will not read each alternative to verify that this is the case. If the Communications Team learns of substantive discrepancies between normative alternatives, the W3C Head of Communications may request that the author no longer serve the alternative as normative.

2. Document Metadata

1. goodStylesheetTest recursive Each document MUST include the following absolute URI to identify a style sheet for this maturity level: http://www.w3.org/StyleSheets/TR/2016/W3C-WDhttp://www.w3.org/StyleSheets/TR/2016/W3C-CRhttp://www.w3.org/StyleSheets/TR/2016/W3C-PRhttp://www.w3.org/StyleSheets/TR/2016/W3C-REChttp://www.w3.org/StyleSheets/TR/2016/W3C-PERhttp://www.w3.org/StyleSheets/TR/2016/W3C-RSCNDhttp://www.w3.org/StyleSheets/TR/2016/W3C-WG-NOTEhttp://www.w3.org/StyleSheets/TR/2016/W3C-IG-NOTEhttp://www.w3.org/StyleSheets/TR/2016/W3C-CG-NOTEhttp://www.w3.org/StyleSheets/TR/2016/W3C-Member-SUBMhttp://www.w3.org/StyleSheets/TR/2016/W3C-Team-SUBMhttp://www.w3.org/StyleSheets/TR/2016/W3C-XGR

   Include this source code:
   <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/2016/W3C-WDhttp://www.w3.org/StyleSheets/TR/2016/W3C-CRhttp://www.w3.org/StyleSheets/TR/2016/W3C-PRhttp://www.w3.org/StyleSheets/TR/2016/W3C-REChttp://www.w3.org/StyleSheets/TR/2016/W3C-PERhttp://www.w3.org/StyleSheets/TR/2016/W3C-RSCNDhttp://www.w3.org/StyleSheets/TR/2016/W3C-WG-NOTEhttp://www.w3.org/StyleSheets/TR/2016/W3C-IG-NOTEhttp://www.w3.org/StyleSheets/TR/2016/W3C-CG-NOTEhttp://www.w3.org/StyleSheets/TR/2016/W3C-Member-SUBMhttp://www.w3.org/StyleSheets/TR/2016/2016/W3C-Team-SUBMhttp://www.w3.org/StyleSheets/TR/2016/W3C-XGR"/>

2. lastStylesheetTest recursive Any internal style sheets MUST be cascaded before this link; i.e., the internal style sheets MUST NOT override the W3C tech report styles.
3. viewportTest recursive The viewport meta tag is required.

   Include this source code:
   <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">

See also Style Guidelines for Group-Internal Drafts.

3. Front Matter

1. divClassHeadTest The front matter MUST appear at the beginning of the body of the document, within <div class="head">. There is one exception to that requirement: the hr element after the copyright MAY appear inside or after the div element. Editors SHOULD NOT include other information in this section.

Logos

1. logoTest The document MUST include a link to the W3C logo identified below. The URI used to identify the logo MUST be absolute.
   
2. logoTest In addition to the W3C logo, use this logo:
   
3. logoTest In addition to the W3C logo, use this logo:
   
4. logoTest In addition to the W3C logo, use this logo:
   

Title, Date, Maturity Level

1. titleTest The document's title MUST be in the title element and in an h1 element.
2. Technical report version information, i.e., version and edition numbers.
   1. If a Recommendation modified in place, see the Comm Team's policy regarding in-place modification of W3C Technical Reports, otherwise
   2. See the (non-normative) Version Management in W3C Technical Reports for more information
3. dateTitleH2Test The document's status and date MUST be in an h2 element as follows (see also date syntax):

   <h2>W3C STATUS 14 August YYYY</h2>

   If this is a modified Recommendation that was modified in place or is a new edition, the document MUST include both the original publication date and the modification date. For example:

   <h2>W3C Recommendation 7 April 2004, 
       edited in place 19 August2004</h2>

Document Identifiers

1. docIDFormat Document identifier information MUST be presented in a dl list, where each dt element marks up an identifier role ("This Version", "Latest Version", "Previous Version", etc.) and each dd element includes a link whose link text is the identifier.
2. docIDOrder Document identifier information MUST be present in this order:
   • This version URI.
   • Latest version URI(s). See also the (non-normative) Version Management in W3C Technical Reports for information about "latest version" URI and version management.
   • Previous version URI
   • "Rescinds this Recommendation" URI
   Note: Because this is a first draft, there SHOULD NOT be a Previous version URI. Use the status section to identify the relationship(s) to previous work (e.g., previous Recommendations). In some cases (e.g., mere change of short name or when a monolithic specification has been split into multiple parts) a Previous version URI MAY appear. Ask the Comm Team if you have questions.
3. docIDThisVersion The syntax of a "This Version" URI MUST SHOULD be <http://www.w3.org/TR/YYYY/WDCRPRPERRECNOTERSCND-shortname-YYYYMMDD/>. <http://www.w3.org/Submission/YYYY/SUBM-shortname-YYYYMMDD/>. <http://www.w3.org/TeamSubmission/YYYY/SUBM-shortname-YYYYMMDD/>. <http://www.w3.org/2005/Incubator/xgname/XGR-shortname-YYYYMMDD/>.
4. docIDLatestVersion The syntax of a "Latest Version" URI MUST SHOULD be <http://www.w3.org/TR/shortname/>. <http://www.w3.org/Submission/shortname/>. <http://www.w3.org/2005/Incubator/xgname/XGR-shortname/>.
5. docIDDate The title page date and the date at the end of the "This Version" URI MUST match.

Editor/Author Information

1. editorSectionTest The editors'/authors' names MUST be listed. Affiliations and email addresses are OPTIONAL; email addresses are NOT RECOMMENDED. If an editor/author is acknowledged in an earlier version of this document and the individual's affiliation has since changed, list the individual using the notation "<name>, <affiliation> (until DD Month YYYY)". If the list of authors is very long (e.g., the entire Working Group), identify the authors in the acknowledgments section, linked from the head of the document. Distinguish any contributors from authors in the acknowledgments section.

Links to non-normative document representations

1. Authors MAY provide links to alternative (non-normative) representations or packages for the document. For instance:

   <p>This document is also available in these non-normative formats: <a href="STATUS-shortname-20020101.html">single HTML file</a>, <a href="STATUS-shortname-20020101.tgz">gzipped tar file of HTML</a>.</p> <a href="shortname-20020101.html">single HTML file</a>, <a href="shortname-20020101.tgz">gzipped tar file of HTML</a>.</p>

Copyright Information

1. copyrightTest The copyright MUST use the following markup (fill in with the appropriate year, years, or year range). The abbr element MAY be used in place of acronym.

   Copyright © YYYY W3C^® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.

2. W3CDocNoticeTest The document must include a link to the W3C document notice. The copyright may be held by the Submitters.
3. hrAfterCopyrightTest A horizontal rule (hr) MUST follow the copyright.

4. Document Abstract

1. abstractTest There MUST be an abstract, labeled with an h2 element with content "Abstract" that follows the hr element.

5. Document Status Section

1. sotdTest There MUST be a status section that follows the abstract, labeled with an h2 element with content "Status of This Document". The Team maintains the status section of a document.
2. boilerplateTRDocTest It MUST begin with the following boilerplate text:

   This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

3. boilerplateMemberSubmTest It MUST include this boilerplate text (with links to the published Submission and Team Comment):

   By publishing this document, W3C acknowledges that the Submitting Members have made a formal Submission request to W3C for discussion. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. This document is not the product of a chartered W3C group, but is published as potential input to the W3C Process. A W3C Team Comment has been published in conjunction with this Member Submission. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of W3C Membership. Please consult the requirements associated with Member Submissions of section 3.3 of the W3C Patent Policy. Please consult the complete list of acknowledged W3C Member Submissions.

4. boilerplateTRDocTest It MUST begin with the following boilerplate text:

   This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of Final Incubator Group Reports is available. See also the W3C technical reports index at http://www.w3.org/TR/.

5. teamSubmLinkTest It MUST include a link to the page listing all Team Submissions.
6. datesFormatTest All dates MUST have the form DD Month YYYY. A leading zero in the day is OPTIONAL.
7. FPWDTest It MUST indicate that this is a First Public Working Draft.
8. LCTest It MUST indicate that this is a Last Call Working Draft.
9. WGLinkTest It MUST include the name of the W3C group that produced the document. The name MUST be a link to a public page for the group.
10. XGLinkTest It MUST include the name of the W3C Incubator Group that produced the document. The name MUST be a link to a public page for the group.
11. mailingListNameTest It MUST include the name of a mailing list for comments that has a public archive.
12. mailingListLinkTest It MUST include a link to the public archive of that mailing list.
13. ACRepFeedbackEmailTest It also MUST provide information to Advisory Committee Representatives about how to send their review comments (e.g., the link to all AC reviews, or a link to a specific questionnaire)
14. commentsMailingListTest It MUST include the name of a mailing list for comments.
15. reviewEndDateLCTest It MUST include the end date of the Last Call review period.
16. reviewEndDateCRTest It MUST include the end date of the Candidate Recommendation review period.
17. reviewEndDateCRTest It MUST include a minimal duration (before which the group will not request the next transition). The duration MUST be expressed as an estimated date.
18. It SHOULD include an estimated date by which time the Working Group expects to have sufficient implementation experience.
19. reviewEndDatePRTest It MUST include the end date of the review period.
20. implReportTest It MUST include a link to a preliminary interoperability or implementation report, or a statement that no such report exists.
21. implReportTest It MUST include either:
    • a link to an interoperability or implementation report if the Director used such a report as part of the decision to advance the specification, or
    • a statement that the Director's decision did not involve such a report.
22. implReportTest It SHOULD include either:
    • a link to an interoperability or implementation report if the Director used such a report as part of the decision to advance the specification, or
    • a statement that the Director's decision did not involve such a report.
23. featAtRiskTest It MUST identify any "features at risk" declared by the Working Group (as defined in section 6.4 of the W3C Process Document).
24. If the previous version of this document was not a Candidate Recommendation, the status section SHOULD include rationale for the Director's decision to skip CR (e.g., there was already sufficient implementation experience).
25. recRelationTest It MUST indicate its relationship to previous related Recommendations (e.g., an indication that a Recommendation supersedes, obsoletes, or subsumes another, or that a Recommendation is an editorial revision) and MUST link to the most recent Recommendation (if any) having the same major revision number. The document thus links to two important resources: the previous edition of the Recommendation via the status section, and the previous draft (the Proposed [Edited] Recommendation) via the "Previous version" link.
26. It MUST indicate that it rescinds a Recommendation and MUST link to the most recent Recommendation (if any) having the same major revision number.
27. A STATUS that revises a previously published Recommendation with the same major revision number SHOULD link to the most recent Recommendation with that major revision number. Example: The version 2.5 Working Draft is published after the 2.1 Second Edition Recommendation and links to it as the most recent 2.x Recommendation available at time of publication. Example: The version 2.1 Working Draft (Second Edition) is published after the 2.1 Recommendation and links to it as the most recent 2.x Recommendation available at time of publication.
28. rescindDecisionTest It MUST include or link to rationale for the decision to rescind the Recommendation.
29. If the document was published due to a W3C decision to stop work on this material, the status section SHOULD include that rationale.
30. It SHOULD direct readers to alternative technologies.
31. It SHOULD indicate the level of endorsement within the group for the material, set expectations that the group has completed work on the topics covered by the document, and set expectations about the group's commitment to respond to comments about the document.
32. customParagraphTest It MUST include at least one customized paragraph. This section SHOULD include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs SHOULD explain the publication context, including rationale and relationships to other work. See examples and more discussion in the Manual of Style.
33. changesListTest It SHOULD MUST include a link to changes since the previous draft (e.g., a list of changes or a diff document or both; see the online HTML diff tool). The group MUST indicate which changes may affect conformance.
34. stabilityTest It MUST set expectations about the (in)stability of the document. The RECOMMENDED text (see also ideas for status sections regarding the stability of group notes) is:

    Publication as a an STATUS does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

35. stabilityTest It MUST set expectations about the stability of the document. The RECOMMENDED text is:

    This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.

36. stabilityTest It MUST set expectations about the stability of the document. The RECOMMENDED text is:

    Publication of this document by W3C as part of the W3C Incubator Activity indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. Participation in Incubator Groups and publication of Incubator Group Reports at the W3C site are benefits of W3C Membership.

37. patPolReqTest It MUST include this text related to patent policy requirements (with suitable links inserted; see guidelines for linking to disclosure pages):

    This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. This document is governed by the 24 January 2002 CPP as amended by the W3C Patent Policy Transition Procedure. This document is governed by the 24 January 2002 CPP as amended by the W3C Patent Policy Transition Procedure. The group does not expect this document to become a W3C Recommendation. This document is informative only. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

    Note: Contact the Communications Team for suitable adaptations in the case where a document has been published jointly by more than one group. In the adaptation, be sure that the text for informative-only specs or specs not going to Rec is the same as the standard text.

38. patPolReqTest It MUST include this text related to disclosure requirements (with a link to the disclosure section of the group charter).

    The disclosure obligations of the Participants of this group are described in the charter.

39. Note: Please contact the Communications Team for information about what text to include related to patent policy requirements.
40. Note: Incubator Groups have as a goal to produce work that can be implemented on a Royalty Free basis, as defined in the W3C Patent Policy. Please contact the Communications Team for information about what text to include related to patent policy requirements. Sample text for XGs where Participants have made no statements:

    Incubator Groups have as a goal to produce work that can be implemented on a Royalty Free basis, as defined in the W3C Patent Policy. Participants in this Incubator Group have made no statements about whether they will offer licenses according to the licensing requirements of the W3C Patent Policy for portions of this Incubator Group Report that are subsequently incorporated in a W3C Recommendation.

41. knownDisclosureNumberTest It MUST NOT indicate the number of known disclosures at the time of publication.
42. whichProcess If published 2 September 2014 or later, according to your selection of the governing process at the top of this form, the document MUST include the following boilerplate text in the status section to identify the governing process:

    This document is governed by the 1 September 2015 W3C Process Document. 14 October 2005 W3C Process Document.

6. Table of Contents

1. tocTest There SHOULD be a table of contents after the status section, labeled with an h2 element with content "Table of Contents".
2. tocNavTest The table of content MUST be inside a navigation element (nav or div).

   Include this source code:
   <nav id="toc"><h2>Table of Contents</h2>

7. Document Body

1. headingWithoutIDTest recursive Every marked-up section and subsection of the document MUST have a target anchor. A section is identified by a heading element (h1-h6). The anchor may be specified using an id (or name if an a element is used) attribute on any of the following: the heading element itself, the parent div or section element of the heading element (where the heading element is the first child of the div or section), a descendant of the heading element, or an a immediately preceding the heading element.
2. brokenLinkTest The document MUST NOT have any broken internal links or broken links to other resources at w3.org. The document SHOULD NOT have any other broken links.
3. cssValideTest recursive The document MUST NOT have any style sheet errors.
4. namespacesTest recursive All proposed XML namespaces created by the publication of the document MUST follow URIs for W3C Namespaces.
5. wcagTest The document(s) MUST conform to the Web Content Accessibility Guidelines 2.0, Level AA. Note: You may wish to consult the customizable quick reference to Web Content Accessibility Guidelines 2.0.

8. Compound Documents

1. compoundFilesLocationTest If the document is compound (i.e., if it consists of more than one file), all the files MUST be under a directory /TR/Submission/TeamSubmission/YYYY/WDCRPRPERRECNOTERSCNDSUBM-shortname-YYYYMMDD/ /2005/Incubator/xgname/XGR-shortname-YYYYMMDD/
2. compoundOverviewTestThe main page SHOULD be called Overview.html.
3. fixupJsTestThe document MUST include the script fixup.js.

   Include this source code:
   <script src="//www.w3.org/scripts/TR/2016/fixup.js"></script>

4. compoundTestAll other files MUST be reachable by links from the document.