From 01f516f642b95b48f04e421c95a0bbf4363b113c Mon Sep 17 00:00:00 2001
From: Francis Storr <francis.storr@intel.com>
Date: Fri, 5 Apr 2024 11:16:42 -0700
Subject: [PATCH 1/2] Mark input purposes list as non-normative

Closes #3777
---
 guidelines/input-purposes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guidelines/input-purposes.html b/guidelines/input-purposes.html
index b83e94c842..69c053d91e 100644
--- a/guidelines/input-purposes.html
+++ b/guidelines/input-purposes.html
@@ -1,4 +1,4 @@
-<section id="input-purposes">
+<section class="informative" id="input-purposes">
 	<h2>Input Purposes for User Interface Components</h2>
 	<p>This section contains a listing of common <a>user interface component</a> input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content.</p>
   

From 65249feacb1a6acf622fd2410aa0b0a5737a5c3d Mon Sep 17 00:00:00 2001
From: Francis Storr <francis.storr@intel.com>
Date: Mon, 8 Apr 2024 10:14:58 -0700
Subject: [PATCH 2/2] Update guidelines/input-purposes.html

Co-authored-by: Mike Gower <mikegower@gmail.com>
---
 guidelines/input-purposes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guidelines/input-purposes.html b/guidelines/input-purposes.html
index 69c053d91e..255ec9a7d6 100644
--- a/guidelines/input-purposes.html
+++ b/guidelines/input-purposes.html
@@ -1,5 +1,5 @@
 <section class="informative" id="input-purposes">
-	<h2>Input Purposes for User Interface Components</h2>
+	<h2>Appendix: Input Purposes for User Interface Components</h2>
 	<p>This section contains a listing of common <a>user interface component</a> input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content.</p>
   
   <p class="note">The list of input type purposes is based on the control purposes defined in the <a href="https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill">HTML specification's Autofill section</a>, but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required.</p>