[Page Title - H1 Bold]
[Introductory Paragraph (Paragraph)]
Use 1–2 short paragraphs to explain:
-
Why this topic matters
-
Who the content is for
-
What the reader will learn
Avoid placing additional headings here.
Example: Proper heading structure helps screen-reader users navigate content, improves SEO, and is required under the Title II digital accessibility standards. Headings must communicate meaning and hierarchy, not just visual styling.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
[Section Heading (H2): Why This Topic Matters]
Follow the heading with paragraphs or bullet lists to introduce each major section of the page.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
[Section Heading (H2): Rules or Principles]
Use short explanatory text to frame the section to introduce rules, guidelines, or concepts.
[Insert a newline (<p> </p>) above the subsection for easy visual separation]
Subsection (H3): Specific Heading 1
Explain the rule in plain language to break down the section into clear parts.. Keep
paragraphs concise.
[Insert a newline (<p> </p>) above the Example Block for easy visual separation]
Example Block (Plain Text or Styled Callout) (H4):
- Use labeled examples to show correct usage.
- Avoid changing heading levels just for visual emphasis.
[Insert a newline (<p> </p>) above the next subsection for easy visual separation]
Subsection (H3): Specific Heading 2
Explain the rule in plain language to break down the section into clear parts.. Keep
paragraphs concise.
[Insert a newline (<p> </p>) above the Example Block for easy visual separation]
Example Block (Plain Text or Styled Callout) (H4):
- Use labeled examples to show correct usage.
- Avoid changing heading levels just for visual emphasis.
[Insert a newline (<p> </p>) above the next subsection for easy visual separation]
(Optional) Tip or Callout Section - Use "1_Callouts – Callout Box with Red Border" Component (H3)
(Optional) Tip or Callout Section - Use "1_Callouts – Callout Box with Red Border" Component (H3)
(Optional) Tip or Callout Section - Use "1_Callouts – Callout Box with Red Border" Component (H3)
Section Heading (H2): What to Avoid
Explain common errors in paragraph form to call out mistakes or anti-patterns.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
Section Heading (H2): Platform-Specific Guidance
Explain CMS-specific behavior or tools:
-
What editors can control
-
Why this matters
-
What best practices to follow
Avoid technical jargon unless absolutely necessary.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
Section Heading (H2): Accessibility Benefits
Use this section to tie content back to compliance, usability, and standards. Keep tone informative, not punitive.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
Section Heading (H2): Tools or Tips
Use this section for optional auditing or validation tools. List tools or browser extensions editors can use.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
Example Summary or Demo Section (Optional)
Use this section to show a complete example without explanation.
[Insert a newline (<p> </p>) above the divider for easy visual separation]
[Insert a newline (<p> </p>) below the divider for easy visual separation]
Closing Paragraph (Plain Text)
End with a short reinforcing statement. No new headings needed.
Example: Correct heading structure is one of the simplest ways to improve accessibility, usability, and search visibility at the same time.