From 4f721b24f3dc033aff726502175f1d4696904e84 Mon Sep 17 00:00:00 2001
From: rmontgomery <rmontgomery@loc.gov>
Date: Tue, 26 Nov 2024 11:07:17 -0500
Subject: [PATCH 1/5] link fix

---
 guidelines/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guidelines/index.html b/guidelines/index.html
index ac5248a..bf613c3 100644
--- a/guidelines/index.html
+++ b/guidelines/index.html
@@ -155,7 +155,7 @@ <h4>Image alternatives</h4>
 								</li>
 
 								<li>Is the <a>image</a> presented in a way that is available to user agents and assistive technology?
-									<ul><li>Yes, <a>image</a> must meet <a href="#detectable-image">Image is programmatically determinable</a> AND the <a>accessibility support set</a> meets <a href="#content-image">Equivalent text alternative is available for image that conveys content</a>. Stop.</li>
+									<ul><li>Yes, <a>image</a> must meet <a href="#detectable-image">Image is programmatically determinable</a> AND the <a>accessibility support set</a> meets <a href="#equivalent-text-alternative">Equivalent text alternative is available for image that conveys content</a>. Stop.</li>
 									<li>No, continue.</li></ul>
 								</li>
 

From 07e64f83cf9bc2f47bc220c4c9e1c0ed2ab97360 Mon Sep 17 00:00:00 2001
From: rmontgomery <rmontgomery@loc.gov>
Date: Tue, 26 Nov 2024 11:11:24 -0500
Subject: [PATCH 2/5] method link fixes

---
 how-to/outcomes/image-alternatives/methods.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/how-to/outcomes/image-alternatives/methods.md b/how-to/outcomes/image-alternatives/methods.md
index 68a8c72..a2f56ab 100644
--- a/how-to/outcomes/image-alternatives/methods.md
+++ b/how-to/outcomes/image-alternatives/methods.md
@@ -6,8 +6,8 @@ layout: layout/methods.md
 
 <div class="nested">
 
-- [Decorative image is programmatically hidden](methods/decorative-images)
-- [Equivalent text alternative is available for image that conveys content](methods/equivalent-alternative-text)
+- [Decorative image is programmatically hidden](decorative-images)
+- [Equivalent text alternative is available for image that conveys content](equivalent-alternative-text)
 
 </div>
 
@@ -15,8 +15,8 @@ layout: layout/methods.md
 
 <div class="nested">
 
-- [The role and importance of the image is programmatically indicated](methods/role-of-images) (Supporting requirement).
-- [The type of image (photo, icon, etc.) is indicated](methods/type-of-image)  (Supporting requirement).
-- [Auto generated text descriptions are editable by content creator](methods/editable-alt-text)  (Supporting requirement).
+- [The role and importance of the image is programmatically indicated](role-of-images)
+- [The type of image (photo, icon, etc.) is indicated](type-of-image)
+- [Auto generated text descriptions are editable by content creator](editable-alt-text)
 
 </div>
\ No newline at end of file

From 8c331876b7abf052853267e11fab8076a2f26de5 Mon Sep 17 00:00:00 2001
From: rmontgomery <rmontgomery@loc.gov>
Date: Tue, 26 Nov 2024 12:18:35 -0500
Subject: [PATCH 3/5] fixes

---
 .DS_Store                                     | Bin 6148 -> 6148 bytes
 .../previous-notable-contributors.html        |   7 ++++---
 guidelines/index.html                         |  18 +++++++-----------
 3 files changed, 11 insertions(+), 14 deletions(-)

diff --git a/.DS_Store b/.DS_Store
index d6857e47ee108535c289abf9a0534f4d99be1f22..222e0612cbeaee42fe61f16953e0df9c8ac1fec6 100644
GIT binary patch
delta 59
zcmZoMXfc@J&&a$nU^gQp^JE^T|8iUm=?tX|nG7imsSG(lIuA$}rxYjWB<1JlFm4uP
MzQ?keo#QV*0Oem0$N&HU

delta 33
pcmZoMXfc@J&&aefU^nAr0}+<V{7io~n=oHynb@GYnVsV=KLEU-3rqk2

diff --git a/guidelines/acknowledgements/previous-notable-contributors.html b/guidelines/acknowledgements/previous-notable-contributors.html
index 7fc0704..e0bd20c 100644
--- a/guidelines/acknowledgements/previous-notable-contributors.html
+++ b/guidelines/acknowledgements/previous-notable-contributors.html
@@ -1,7 +1,8 @@
 <section>
-	<h2>Previous notable contributors:</h2>
+	<h3>Previous notable contributors:</h3>
 	<ul>
-		<li>Shawn Lauriat (Editor 2021-2023)</li>
-		<li>Wilco Fiers (Project Manager 2021-2023)</li>l
+		<li>Michael Cooper, Staff Editor 2021-2023 (W3C)</li>
+		<li>Shawn Lauriat, Editor 2021-2023 (Google)</li>
+		<li>Wilco Fiers, Project Manager 2021-2023 (Deque))</li>l
 	</ul> 
 </section> 
\ No newline at end of file
diff --git a/guidelines/index.html b/guidelines/index.html
index bf613c3..6d7b299 100644
--- a/guidelines/index.html
+++ b/guidelines/index.html
@@ -16,7 +16,7 @@
 			<p>See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3.0 Introduction</a> for an introduction and links to WCAG technical and educational material.</p>
 		</section>
 		<section id="sotd">
-			<p>This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for two Guidelines: Image alternatives and Keyboard Focus Appearance.</p>
+			<p>This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Clear meaning, Image alternatives, and Keyboard focus appearance.</p>
 			<p>To comment, <a href="https://github.com/w3c/wcag3/issues/new">file an issue in the W3C wcag3 GitHub repository</a>. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:public-agwg-comments@w3.org?subject=WCAG%203.0%20public%20comment">public-agwg-comments@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). In-progress updates to the guidelines can be viewed in the <a href="https://w3c.github.io/wcag3/guidelines/">public editors’ draft</a>.</p>
 		</section>
 		<section class="informative">
@@ -70,13 +70,13 @@ <h2>Introduction</h2>
 			<p>The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft:
 				<ul><li>What requirements are missing from this list to make web content accessible?</li>
 					<li>What research supports or refutes the requirements marked as needing additional research?</li>
-					<li>Three guidelines (<a href="#clear-meaning">Clear meaning</a>, <a href="#image-alternatives">Image alternatives</a>, and <a href="#keyboard-focus-appearance">Keyboard Focus Appearance</a>) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use:
+					<li>Three guidelines (<a href="#clear-meaning">Clear meaning</a>, <a href="#image-alternatives">Image alternatives</a>, and <a href="#keyboard-focus-appearance">Keyboard focus appearance</a>) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use:
 					<ul>
 						<li>Grouping related requirements and assertions?</li>
 						<li>Using a decision tree for foundational requirements?</li>
 					 </ul>
 					</li>
-					<li>The organization of the decision trees in <a href="#clear-meaning">Clear meaning</a> and <a href="#keyboard-focus-appearance">Keyboard Focus Appearance</a> differ slightly. Does one seem clearer than the other?</li>
+					<li>The organization of the decision trees in <a href="#clear-meaning">Clear meaning</a> and <a href="#keyboard-focus-appearance">Keyboard focus appearance</a> differ slightly. Does one seem clearer than the other?</li>
 					<li>The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3.0. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3.0? </li>
 				</ul></p>
 	
@@ -145,7 +145,7 @@ <h4>Image alternatives</h4>
 					</div>
 
 					<details class="decision-tree">
-						<summary>Which foundational provision applies?</summary>
+						<summary>Which foundational requirements apply?</summary>
 
 						<p>For each <a>image</a>:
 							<ol>
@@ -349,7 +349,7 @@ <h4>Clear meaning</h4>
 							<svg aria-hidden="true" class="i-info"><use xlink:href="img/icons.svg#i-info"></use></svg> How to meet Clear Meaning</a></p>
 					</aside>
 					<details class="decision-tree">
-						<summary>Which foundational provision applies?</summary>
+						<summary>Which foundational requirements apply?</summary>
 						<p>For each item of ambiguous text, such as <a>non-literal text</a>, abbreviations and acronyms, <a>ambiguous numbers</a>, or text missing letters or diacritics:</p>
 						<ol>
 							<li>Is the text presented in a way that is available to <a>user agents</a>, including assistive technology (AT)?
@@ -446,7 +446,7 @@ <h4>Keyboard Focus Appearance</h4>
 					</div>
 					
 					<details class="decision-tree">
-						<summary>Which foundational provision applies?</summary>
+						<summary>Which foundational requirements apply?</summary>
 						<p>For each focusable item:
 							<ol>
 
@@ -1625,22 +1625,18 @@ <h2>Change log</h2>
 		</section>
 		<section class="appendix">
 			<h2>Acknowledgements</h2>
-		<section class="appendix">			
-			<h3>Current Contributors</h3>			
+		<section class="appendix">					
   			<p>Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the <a href="https://www.w3.org/groups/wg/ag/">Working Group home page</a>.</p>
 			<div data-include="acknowledgements/current-contributors.html" data-include-replace="true"></div>
 		</section>
 		<section class="appendix">	
-			<h3>Prior Notable Contributors</h3>
 			<div data-include="acknowledgements/previous-notable-contributors.html" data-include-replace="true"></div>
 		</section>			
 		<section class="appendix">
-			<h3>Prior Contributors</h3>
 			<div data-include="acknowledgements/previous-contributors.html" data-include-replace="true"></div>
 			<div data-include="acknowledgements/research-partners.html" data-include-replace="true"></div>
 		</section>
 		<section>
-			<h3>Funders</h3>
 			<div data-include="acknowledgements/funders.html" data-include-replace="true"></div>			
 		</section>
 	</body>

From 2d04b2d9c457036fb82ef97a17bf6c7bb2b50cb5 Mon Sep 17 00:00:00 2001
From: rmontgomery <rmontgomery@loc.gov>
Date: Tue, 26 Nov 2024 12:31:38 -0500
Subject: [PATCH 4/5] apendix

---
 guidelines/index.html | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/guidelines/index.html b/guidelines/index.html
index 6d7b299..bb43a7f 100644
--- a/guidelines/index.html
+++ b/guidelines/index.html
@@ -1624,19 +1624,12 @@ <h2>Change log</h2>
 
 		</section>
 		<section class="appendix">
-			<h2>Acknowledgements</h2>
-		<section class="appendix">					
+			<h2>Acknowledgements</h2>				
   			<p>Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the <a href="https://www.w3.org/groups/wg/ag/">Working Group home page</a>.</p>
 			<div data-include="acknowledgements/current-contributors.html" data-include-replace="true"></div>
-		</section>
-		<section class="appendix">	
 			<div data-include="acknowledgements/previous-notable-contributors.html" data-include-replace="true"></div>
-		</section>			
-		<section class="appendix">
 			<div data-include="acknowledgements/previous-contributors.html" data-include-replace="true"></div>
 			<div data-include="acknowledgements/research-partners.html" data-include-replace="true"></div>
-		</section>
-		<section>
 			<div data-include="acknowledgements/funders.html" data-include-replace="true"></div>			
 		</section>
 	</body>

From 58f7b641f4b9fdc6ff94559a184e779c7165e002 Mon Sep 17 00:00:00 2001
From: rmontgomery <rmontgomery@loc.gov>
Date: Tue, 26 Nov 2024 12:36:56 -0500
Subject: [PATCH 5/5] editorial fixes

---
 guidelines/acknowledgements/funders.html               |  2 +-
 guidelines/acknowledgements/previous-contributors.html |  2 +-
 .../previous-notable-contributors.html                 |  4 ++--
 guidelines/index.html                                  | 10 ++++++++--
 4 files changed, 12 insertions(+), 6 deletions(-)

diff --git a/guidelines/acknowledgements/funders.html b/guidelines/acknowledgements/funders.html
index 935b946..8ea47dd 100644
--- a/guidelines/acknowledgements/funders.html
+++ b/guidelines/acknowledgements/funders.html
@@ -1,4 +1,4 @@
 <section id="enabling-funders">
-	<h2>Enabling funders</h2>
+	<h3>Enabling funders</h3>
 	<p>This publication has been funded in part with U.S. Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services or the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.</p>
 </section>
\ No newline at end of file
diff --git a/guidelines/acknowledgements/previous-contributors.html b/guidelines/acknowledgements/previous-contributors.html
index 911ae95..a49d0b0 100644
--- a/guidelines/acknowledgements/previous-contributors.html
+++ b/guidelines/acknowledgements/previous-contributors.html
@@ -1,5 +1,5 @@
 <section>
-	<h2>Previous contributors to the development of this document</h2>
+	<h3>Previous contributors to the development of this document</h3>
 	<p>Abi James, 
 		Abi Roper, 
 		Alastair Campbell, 
diff --git a/guidelines/acknowledgements/previous-notable-contributors.html b/guidelines/acknowledgements/previous-notable-contributors.html
index e0bd20c..ee64403 100644
--- a/guidelines/acknowledgements/previous-notable-contributors.html
+++ b/guidelines/acknowledgements/previous-notable-contributors.html
@@ -2,7 +2,7 @@
 	<h3>Previous notable contributors:</h3>
 	<ul>
 		<li>Michael Cooper, Staff Editor 2021-2023 (W3C)</li>
-		<li>Shawn Lauriat, Editor 2021-2023 (Google)</li>
-		<li>Wilco Fiers, Project Manager 2021-2023 (Deque))</li>l
+		<li>Shawn Lauriat, Editor 2021-2023 (Google, Inc.)</li>
+		<li>Wilco Fiers, Project Manager 2021-2023 (Deque Systems, Inc.)</li>
 	</ul> 
 </section> 
\ No newline at end of file
diff --git a/guidelines/index.html b/guidelines/index.html
index bb43a7f..a69f075 100644
--- a/guidelines/index.html
+++ b/guidelines/index.html
@@ -1561,12 +1561,18 @@ <h2>Glossary</h2>
 				</dd>
 				<dt data-status="developing"><dfn>Task flow</dfn></dt>
 				<dd>
-					<p>Testing scope that includes a series views that support a specified <a>user activity</a>. A task flow may include a subset of <a>items</a> in a <a>view</a> or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.</p>
+					<p>Testing scope that includes a series views that support a specified user activity. A task flow may include a subset of <a>items</a> in a <a>view</a> or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.</p>
 				</dd>
 				<dt data-status="developing"><dfn>Test</dfn></dt>
 				<dd>
 					<p>Mechanism to evaluate implementation of a <a>method</a>.</p>
 				</dd>
+				<dt><dfn>Text</dfn></dt>
+				<dd>
+					<div class="ednote">
+						<p>To be defined.</p>
+					</div>
+				</dd>
 				<dt><dfn>User agent</dfn></dt>
 				<dd>
 					<div class="ednote">
@@ -1583,7 +1589,7 @@ <h2>Glossary</h2>
 				</dd>
 				<dt data-status="developing"><dfn>View</dfn></dt>
 				<dd>
-					<p>Testing scope that includes all <a>content</a> visually and <a>programmatically</a> available without a <a>significant change</a>. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.</p>
+					<p>Testing scope that includes all <a>content</a> visually and <a>programmatically</a> available without a significant change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.</p>
 				</dd>
 				<dt><dfn>Web technologies</dfn></dt>
 				<dd>