From fe9fc4207c128c1ccd62e2275303befd0770eed1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Re=CC=81mi=20Be=CC=81tin?= <git@remibetin.fr>
Date: Thu, 20 Jun 2024 19:14:05 +0200
Subject: [PATCH] Display H2 to H4 in TOC

---
 _config.yml                       | 2 +-
 content/forms/instructions.md     | 2 +-
 content/forms/labels.md           | 1 +
 content/forms/notifications.md    | 2 +-
 content/menus/flyout.md           | 1 +
 content/page-structure/content.md | 2 +-
 6 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/_config.yml b/_config.yml
index 5a926283..20b80762 100644
--- a/_config.yml
+++ b/_config.yml
@@ -25,7 +25,7 @@ exclude:
 
 # Build settings
 markdown: kramdown
-kramwdown:
+kramdown:
   toc_levels: 2..3
   input: GFM
   syntax_highlighter: rouge
diff --git a/content/forms/instructions.md b/content/forms/instructions.md
index b0879ae3..d4f44dad 100755
--- a/content/forms/instructions.md
+++ b/content/forms/instructions.md
@@ -18,7 +18,6 @@ navigation:
   previous: /tutorials/forms/grouping/
   next: /tutorials/forms/validation/
 
-
 wcag_success_criteria:
   - 1.3.1
   - 2.4.6
@@ -56,6 +55,7 @@ Provide instructions to help users understand how to complete the form and use i
 {% include box.html type="end" %}
 {:/}
 
+{::options toc_levels="2,3,4" /}
 {% include_cached toc.html %}
 
 **Important:** Screen readers often switch to “Forms Mode” when they are processing content within a `<form>` element. In this mode they usually only read aloud form elements such as `<input>`, `<select>`, `<textarea>`, `<legend>`, and `<label>`. It is critical to include form instructions in ways that can be read aloud. This will be explained further below.
diff --git a/content/forms/labels.md b/content/forms/labels.md
index c840e689..0090f57d 100755
--- a/content/forms/labels.md
+++ b/content/forms/labels.md
@@ -59,6 +59,7 @@ Provide labels to identify all form controls, including text fields, checkboxes,
 {% include box.html type="end" %}
 {:/}
 
+{::options toc_levels="2,3,4" /}
 {% include_cached toc.html %}
 
 Labels need to describe the purpose of the form control. This section of the tutorial describes how to provide labels that are properly associated with form controls. Later sections explain how to provide [instructions](../instructions), [validate user input](../validation), and [provide feedback](../notifications) to help users complete your form.
diff --git a/content/forms/notifications.md b/content/forms/notifications.md
index 6501063e..16ff3c53 100755
--- a/content/forms/notifications.md
+++ b/content/forms/notifications.md
@@ -17,7 +17,6 @@ navigation:
   previous: /tutorials/forms/validation/
   next: /tutorials/forms/multi-page/
 
-
 wcag_success_criteria:
   - 3.3.1
   - 3.3.3
@@ -50,6 +49,7 @@ Provide feedback to users about the results of their form submission, whether su
 {% include box.html type="end" %}
 {:/}
 
+{::options toc_levels="2,3,4" /}
 {% include_cached toc.html %}
 
 Notifications have to be concise and clear. In particular, error messages should be easy to understand and should provide simple instructions on how they can be resolved. Success messages are also important to confirm task completion.
diff --git a/content/menus/flyout.md b/content/menus/flyout.md
index 19aa53d8..119f779d 100644
--- a/content/menus/flyout.md
+++ b/content/menus/flyout.md
@@ -45,6 +45,7 @@ People with reduced dexterity, such as tremors, often have trouble operating fly
 {% include box.html type="end" %}
 {:/}
 
+{::options toc_levels="2,3,4" /}
 {% include_cached toc.html %}
 
 ## Indicate submenus
diff --git a/content/page-structure/content.md b/content/page-structure/content.md
index 253d78aa..e6902692 100755
--- a/content/page-structure/content.md
+++ b/content/page-structure/content.md
@@ -27,7 +27,6 @@ contributing_participants:
   - see <a href="/WAI/tutorials/acknowledgements/">Acknowledgements</a>
 support: Developed by the Education and Outreach Working Group (<a href="https://www.w3.org/groups/wg/eowg">EOWG</a>). Developed with support from the <a href="https://www.w3.org/WAI/ACT/">WAI-ACT project</a>, co-funded by the <strong>European Commission <abbr title="Information Society Technologies">IST</abbr> Programme</strong>.
 
-
 wcag_success_criteria:
   - 1.3.1
 wcag_techniques:
@@ -47,6 +46,7 @@ Mark up website content semantically, so that the website is extensible. Valid s
 {% include box.html type="end" %}
 {:/}
 
+{::options toc_levels="2,3,4" /}
 {% include_cached toc.html %}
 
 ## Articles