From 84f4a8b034c226234342bfdb1d5ffd6063d6a793 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 11:23:46 -0400
Subject: [PATCH 01/19] Update WCAG 2.4.6 atomic rule draft

This is work-in-progress still at its early stage, more examples will be added, some may be removed. Everything is open to discussion.
---
 _rules/heading-descriptive-b49b2e.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 0a133cc43f..c63e0ca876 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -1,6 +1,6 @@
 ---
 id: b49b2e
-name: Heading is descriptive
+name: Heading is relevant and meaningful
 rules_format: 1.1
 rule_type: atomic
 description: |

From 1d6fe02a2a52781bc96381e5cdd526c708a75ab2 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 11:59:41 -0400
Subject: [PATCH 02/19] Clarify heading relevance rule description and
 applicability

Updated the description and applicability of the heading relevance rule to clarify its requirements and scope.
---
 _rules/heading-descriptive-b49b2e.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index c63e0ca876..f753957a96 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -4,7 +4,7 @@ name: Heading is relevant and meaningful
 rules_format: 1.1
 rule_type: atomic
 description: |
-  This rule checks that headings describe the topic or purpose of the content.
+  This rule checks that headings are relevant to a specific topic, purpose or page or they are not meaningless.
 accessibility_requirements:
   wcag20:2.4.6: # Headings and labels (AA)
     forConformance: true
@@ -28,7 +28,9 @@ acknowledgments:
 
 ## Applicability
 
-This rule applies to any [semantic][semantic role] `heading` element that is [included in the accessibility tree][] and has a non-empty (`””`) [accessible name][].
+This rule applies to any visible content that is perceived as a heading on a given page, as well as to any semantic heading element that is [included in the accessibility tree](included-in-the-accessibility-tree "Definition of included in the accessibility tree") while not visible. In other words, this rule applies to headings and their relation to the content, regardless of their compliance with any other accessibility criteria.
+
+This rule requires that testing be limited to the wording in headings, in plain language.
 
 ## Expectation
 

From d2ad7daa8c5676b30cc9bde03b05dfa05e007d35 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 13:00:26 -0400
Subject: [PATCH 03/19] Update acknowledgments and refine rule scope

Added authors to acknowledgments and clarified rule scope.
---
 _rules/heading-descriptive-b49b2e.md | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index f753957a96..ff619a097a 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -18,6 +18,7 @@ input_aspects:
   - Language
 acknowledgments:
   authors:
+    - Armagan Tekdoner
     - Carlos Duarte
     - Dagfinn Rømen
     - Geir Sindre Fossøy
@@ -32,11 +33,17 @@ This rule applies to any visible content that is perceived as a heading on a giv
 
 This rule requires that testing be limited to the wording in headings, in plain language.
 
-## Expectation
+### None of the following is within this rule's scope:
+* Complete lack of headings
+* Heading structure and hierarchy (incorrectly nested, skipped, or missing heading levels, or heading elements that do not follow a logical sequence)
+* Source code errors, provided that the heading is visible or exposed to assistive technologies
+* Grammar or spelling errors in headings, unless they render the text entirely unintelligible
+* Styling and presentation, unless the styling renders the heading completely illegible
+* Other accessibility failures covered by distinct WCAG success criteria, regardless of their severity
 
-Each target element describes the topic or purpose of the first [perceivable content][] after the test target that is not [decorative][]. The order of elements is determined by the [flat tree][].
+## Expectation
 
-**Note:** Headings do not need to be lengthy. A word, or even a single character, may be sufficient.
+Each heading is relevant to the content on the page where it appears. This content may encompass the entire page, the section or paragraph immediately following the heading, or elements clustered within its visual or structural scope.
 
 ## Background
 

From 816bc57a43ee51b5a11cd3371f21865dc35a83f5 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 14:45:36 -0400
Subject: [PATCH 04/19] Refine heading relevance rule description and context

Updated the description for clarity and improved the explanation of the rule's evaluation criteria. Added sections on assumptions, limitations, and exceptions to provide more context.
---
 _rules/heading-descriptive-b49b2e.md | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index ff619a097a..15b5125ae1 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -4,7 +4,7 @@ name: Heading is relevant and meaningful
 rules_format: 1.1
 rule_type: atomic
 description: |
-  This rule checks that headings are relevant to a specific topic, purpose or page or they are not meaningless.
+  This rule checks that headings are meaningful and they are relevant to a specific topic, purpose or page.
 accessibility_requirements:
   wcag20:2.4.6: # Headings and labels (AA)
     forConformance: true
@@ -13,7 +13,6 @@ accessibility_requirements:
     inapplicable: further testing needed
 input_aspects:
   - Accessibility Tree
-  - DOM Tree
   - CSS Styling
   - Language
 acknowledgments:
@@ -47,19 +46,28 @@ Each heading is relevant to the content on the page where it appears. This conte
 
 ## Background
 
-Headings that are visible but not in the accessibility tree are a failure of [Success Criterion 1.3.1 Info and Relationships][sc131]. These are not tested by this rule but they can still fail [Success Criterion 2.4.6 Headings and Labels][sc246].
+This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all equally applicable under this rule.
 
-Testing tools treat empty headings `<h1></h1>` or `div role="heading" aria-level="1"></div>` differently. Some fail empty headings under 1.3.1, others under 2.4.6, while others pass these headings because they are ignored by most assistive technologies causing no accessibility barriers at all. This rule doesn't include examples of empty headings because there is currently no harmonized approach for testing them.
+To pass, a heading must convey meaning and be relevant to its associated content. Headings consisting purely of non-default placeholder text or uninformative character strings fail this rule inherently. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
 
 ### Assumptions
+This rule assumes that the tester evaluating the content possesses the necessary language proficiency and contextual comprehension required to assess the relationship between the headings and their associated content. 
 
-This rule assumes that the [flat tree][] order is close to the reading order as elements are rendered on the page. Due to positioning, it is possible to render a document in an order that greatly differs from the tree order, in which case the content which is visually associated with a heading might not be the content following it in tree order and this rule might fail while [Success Criterion 2.4.6 Headings and Labels][sc246] is still satisfied.
+#### Limitations
+The following scenarios present inherent limitations to evaluation, and the headings being tested may be deemed out of scope:
+* Multilingual Content: Web pages containing content in multiple languages (e.g., a heading in one language preceding content in another) where the tester does not possess professional working proficiency in all languages present.
+* Rapidly Changing or Real-Time Content Streams: Live, dynamic content fields (e.g., streaming data feeds, live social walls, or active chat interfaces) where the content updates at a rate that prevents static evaluation against its structural headings.
+* Transient Loading States: Temporary layout interfaces, such as skeletal loaders or placeholder templates, where the final text content has not yet completely rendered in the Document Object Model (DOM).
 
-This rule also assumes that the content the heading is intended to describe is [visible][] and not hidden from assistive technologies. Otherwise, cases such as expandable content using a heading might fail this rule while [Success Criterion 2.4.6 Headings and Labels][sc246] is still satisfied.
+#### Exceptions
+The following scenarios constitute exceptions to this rule, as the contextual intent of the author cannot be objectively determined by a general evaluator:
+* Highly Specialized or Technical Domains: Content involving advanced scientific, technical, or academic material (e.g., specialized research documentation) that requires domain-specific expertise.
+* Abstract or Creative Works: Content consisting of creative literary works, poetry, or abstract text where relevance is interpretive or non-linear rather than purely informational.
+* Legally Mandated or Standardized Boilerplate: Documents or user interfaces where the text and structure of headings are rigidly dictated by statutory, regulatory, or legal mandates (e.g., standardized privacy disclosures or government forms) and cannot be altered by the author.
 
 ### Accessibility Support
 
-Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `heading` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue.
+This rule is inherently subjective and relies entirely on human judgment; it is not intended for automated testing environments. Because evaluating the relevance of textual content is non-technical, findings may be subject to varying interpretations by individuals regardless of their technical background. Consequently, this rule is designed as a test-to-pass evaluation. Testers should default to a passing result unless an irrelevance or lack of meaning is obvious; any identified failure should be immediately apparent and acknowledgeable by the content creators or those familiar with the page context.
 
 ### Other Resources
 

From 4974e86d4d5f5d48fa213ddd43e5a6eb45cdf373 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 16:48:19 -0400
Subject: [PATCH 05/19] Refine heading rule by removing duplicates and
 clarifying scope

Edits made until Passed example 6
---
 _rules/heading-descriptive-b49b2e.md | 117 +++++++++------------------
 1 file changed, 39 insertions(+), 78 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 15b5125ae1..1a6b392751 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -27,25 +27,22 @@ acknowledgments:
 ---
 
 ## Applicability
-
 This rule applies to any visible content that is perceived as a heading on a given page, as well as to any semantic heading element that is [included in the accessibility tree](included-in-the-accessibility-tree "Definition of included in the accessibility tree") while not visible. In other words, this rule applies to headings and their relation to the content, regardless of their compliance with any other accessibility criteria.
 
 This rule requires that testing be limited to the wording in headings, in plain language.
 
 ### None of the following is within this rule's scope:
-* Complete lack of headings
-* Heading structure and hierarchy (incorrectly nested, skipped, or missing heading levels, or heading elements that do not follow a logical sequence)
-* Source code errors, provided that the heading is visible or exposed to assistive technologies
-* Grammar or spelling errors in headings, unless they render the text entirely unintelligible
-* Styling and presentation, unless the styling renders the heading completely illegible
-* Other accessibility failures covered by distinct WCAG success criteria, regardless of their severity
+- Complete lack of headings
+- Heading structure and hierarchy (incorrectly nested, skipped, or missing heading levels, or heading elements that do not follow a logical sequence)
+- Source code errors, provided that the heading is visible or exposed to assistive technologies
+- Grammar or spelling errors in headings, unless they render the text entirely unintelligible
+- Styling and presentation, unless the styling renders the heading completely illegible
+- Other accessibility failures covered by distinct WCAG success criteria, regardless of their severity
 
 ## Expectation
-
 Each heading is relevant to the content on the page where it appears. This content may encompass the entire page, the section or paragraph immediately following the heading, or elements clustered within its visual or structural scope.
 
 ## Background
-
 This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all equally applicable under this rule.
 
 To pass, a heading must convey meaning and be relevant to its associated content. Headings consisting purely of non-default placeholder text or uninformative character strings fail this rule inherently. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
@@ -55,111 +52,75 @@ This rule assumes that the tester evaluating the content possesses the necessary
 
 #### Limitations
 The following scenarios present inherent limitations to evaluation, and the headings being tested may be deemed out of scope:
-* Multilingual Content: Web pages containing content in multiple languages (e.g., a heading in one language preceding content in another) where the tester does not possess professional working proficiency in all languages present.
-* Rapidly Changing or Real-Time Content Streams: Live, dynamic content fields (e.g., streaming data feeds, live social walls, or active chat interfaces) where the content updates at a rate that prevents static evaluation against its structural headings.
-* Transient Loading States: Temporary layout interfaces, such as skeletal loaders or placeholder templates, where the final text content has not yet completely rendered in the Document Object Model (DOM).
+- Multilingual Content: Web pages containing content in multiple languages (e.g., a heading in one language preceding content in another) where the tester does not possess professional working proficiency in all languages present.
+- Rapidly Changing or Real-Time Content Streams: Live, dynamic content fields (e.g., streaming data feeds, live social walls, or active chat interfaces) where the content updates at a rate that prevents static evaluation against its structural headings.
+- Transient Loading States: Temporary layout interfaces, such as skeletal loaders or placeholder templates, where the final text content has not yet completely rendered in the Document Object Model (DOM).
 
 #### Exceptions
 The following scenarios constitute exceptions to this rule, as the contextual intent of the author cannot be objectively determined by a general evaluator:
-* Highly Specialized or Technical Domains: Content involving advanced scientific, technical, or academic material (e.g., specialized research documentation) that requires domain-specific expertise.
-* Abstract or Creative Works: Content consisting of creative literary works, poetry, or abstract text where relevance is interpretive or non-linear rather than purely informational.
-* Legally Mandated or Standardized Boilerplate: Documents or user interfaces where the text and structure of headings are rigidly dictated by statutory, regulatory, or legal mandates (e.g., standardized privacy disclosures or government forms) and cannot be altered by the author.
+- Highly Specialized or Technical Domains: Content involving advanced scientific, technical, or academic material (e.g., specialized research documentation) that requires domain-specific expertise.
+- Abstract or Creative Works: Content consisting of creative literary works, poetry, or abstract text where relevance is interpretive or non-linear rather than purely informational.
+- Legally Mandated or Standardized Boilerplate: Documents or user interfaces where the text and structure of headings are rigidly dictated by statutory, regulatory, or legal mandates (e.g., standardized privacy disclosures or government forms) and cannot be altered by the author.
 
 ### Accessibility Support
-
 This rule is inherently subjective and relies entirely on human judgment; it is not intended for automated testing environments. Because evaluating the relevance of textual content is non-technical, findings may be subject to varying interpretations by individuals regardless of their technical background. Consequently, this rule is designed as a test-to-pass evaluation. Testers should default to a passing result unless an irrelevance or lack of meaning is obvious; any identified failure should be immediately apparent and acknowledgeable by the content creators or those familiar with the page context.
 
 ### Other Resources
-
-- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)
 - [Understanding Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html)
 - [G130: Providing descriptive headings](https://www.w3.org/WAI/WCAG22/Techniques/general/G130)
-- [H42: Using h1-h6 to identify headings](https://www.w3.org/WAI/WCAG22/Techniques/html/H42)
-- [ARIA12: Using role=heading to identify headings](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA12)
+- [Understanding Success Criterion 2.4.10 Section Headings)](https://www.w3.org/WAI/WCAG21/Understanding/section-headings)
+- [Use headings to convey meaning and structure](https://www.w3.org/WAI/tips/writing/#use-headings-to-convey-meaning-and-structure)
 - [HTML Specification - Heading content](https://html.spec.whatwg.org/#heading-content)
 
-## Examples
+## Test Cases
 
-### Passed
+### Passed (category 1)
+Headings that are compliant under this criterion, while exhibiting no other accessibility or structural failures under WCAG.
 
 #### Passed Example 1
-
-This `h1` heading element describes the topic of the following paragraph.
-
+This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
-<html lang="en">
-	<h1>Opening Hours</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
+	<h1>Passport Renewal</h1>
+	<!-- Followed by a page that has instructions, images and a form about how to make the renewal application -->
 ```
 
 #### Passed Example 2
-
-This heading marked up with an [explicit role][] of `heading` describes the topic of the following paragraph.
-
+This `h1` element provides a relevant heading for the marketing content that follows it.
 ```html
-<html lang="en">
-	<span role="heading" aria-level="1">Opening Hours</span>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
+	<h1>Fresh deals just dropped</h1>
+	<!-- Followed by a carousel displaying newly arrived products on a shopping website -->
 ```
 
 #### Passed Example 3
-
-This `h1` heading element with an image describes the topic of the following paragraph.
-
+This `h1` element provides a relevant heading for the informational data that follows it.
 ```html
-<html lang="en">
-	<h1>
-		<img src="/test-assets/descriptive-heading-b49b2e/opening_hours_icon.png" alt="Opening hours" />
-	</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
+	<h1>Current Weather in New York</h1>
+	<!-- Followed by a data table that contains icons and other legend -->
 ```
 
-#### Passed Example 4
-
-This `h1` heading element has a single character text that describes the topic of the following description list.
+### Passed (category 2)
+Headings that are compliant under this criterion, despite exhibiting other accessibility or structural failures under WCAG.
 
+#### Passed Example 4
+This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, as the text is hidden from assistive technologies and has an insufficient contrast ratio.
 ```html
-<html lang="en">
-	<h1>A</h1>
-	<dl>
-		<dt>airplane</dt>
-		<dd>
-			a powered flying vehicle with fixed wings and a weight greater than that of the air it displaces.
-		</dd>
-		<dt>apple</dt>
-		<dd>
-			the round fruit of a tree of the rose family, which typically has thin green or red skin and crisp flesh.
-		</dd>
-	</dl>
-</html>
+	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts at Our University</h1>
+	<!-- Followed by the name of the university and some other promotional content -->
 ```
 
 #### Passed Example 5
-
-This heading marked up with an [explicit role][] of `heading` describes the topic of the following paragraph. The heading is positioned off screen but is [included in the accessibility tree][].
-
+This `p` element is perceived as a heading. It passes this rule because its text is relevant, despite failing other WCAG criteria by relying entirely on visual presentation to convey heading structure and utilizing an invalid ARIA role and value.
 ```html
-<html lang="en">
-	<span role="heading" aria-level="1" style="position: absolute; top: -9999px; left: -9999px;">Opening Hours</span>
-	<p>
-		We are open Monday through Friday from 10 to 16
-	</p>
-</html>
+	<p class="h1" role="headline">A Million Different Journeys</p>
+	<!-- Followed by the home page of a travel website that advertises their services -->
 ```
 
 #### Passed Example 6
-
-This heading describes the first [perceivable content][] after it (the first `p` element). The next [perceivable content][] (the second `p` element) is not considered by this rule.
-
+This `img` element is perceived as a heading. It passes this rule because its text content is relevant, despite failing other WCAG criteria by lacking an accessible name.
 ```html
-<html lang="en">
-	<h1>Opening Hours</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-	<p>We are open Saturday from 10 to 13</p>
-</html>
+<!-- The image of text below is large and reads "Our Mortgage Interest Rates" -->
+<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
+<!-- Followed by a data table showing different rates for different amortizations -->
 ```
 
 ### Failed

From edcaf8a962f86bbb9ef1f325fd61e54283dfb468 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 17:13:16 -0400
Subject: [PATCH 06/19] Revise heading examples and add new passed cases

---
 _rules/heading-descriptive-b49b2e.md | 46 ++++++++++++++++++++++------
 1 file changed, 37 insertions(+), 9 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 1a6b392751..2790629c4a 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -80,15 +80,15 @@ Headings that are compliant under this criterion, while exhibiting no other acce
 #### Passed Example 1
 This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
-	<h1>Passport Renewal</h1>
+	<h1>Renew Your Passport Online</h1>
 	<!-- Followed by a page that has instructions, images and a form about how to make the renewal application -->
 ```
 
 #### Passed Example 2
 This `h1` element provides a relevant heading for the marketing content that follows it.
 ```html
-	<h1>Fresh deals just dropped</h1>
-	<!-- Followed by a carousel displaying newly arrived products on a shopping website -->
+	<h1>Fresh deals just dropped: Printers/h1>
+	<!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
 ```
 
 #### Passed Example 3
@@ -99,30 +99,58 @@ This `h1` element provides a relevant heading for the informational data that fo
 ```
 
 ### Passed (category 2)
-Headings that are compliant under this criterion, despite exhibiting other accessibility or structural failures under WCAG.
+Headings that serve as structural or sequential identifiers, which are inherently compliant regardless of the specific content that follows.
 
 #### Passed Example 4
+This `h1` element provides a sequential identifier for a major document section.
+```html
+	<h1>Chapter 4</h1>
+	<!-- The content that follows can make no difference -->
+```
+
+#### Passed Example 5
+This `h1` element provides a structural identifier for a section of a musical work.
+```html
+	<h1>1st movement</h1>
+	<!-- The content that follows describes the mood of the first movement of a symphony -->
+```
+
+#### Passed Example 6
+This `h1` element provides an official legal citation that serves as an unambiguous identifier for the section.
+```html
+	<h1>Act, SC 2002, c 29</h1>
+	<!-- The content that follows is about that specific act -->
+```
+
+### Passed (category 3)
+Headings that are compliant under this criterion, despite exhibiting other accessibility or structural failures under WCAG.
+
+#### Passed Example 7
 This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, as the text is hidden from assistive technologies and has an insufficient contrast ratio.
 ```html
 	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts at Our University</h1>
 	<!-- Followed by the name of the university and some other promotional content -->
 ```
 
-#### Passed Example 5
+#### Passed Example 8
 This `p` element is perceived as a heading. It passes this rule because its text is relevant, despite failing other WCAG criteria by relying entirely on visual presentation to convey heading structure and utilizing an invalid ARIA role and value.
 ```html
 	<p class="h1" role="headline">A Million Different Journeys</p>
 	<!-- Followed by the home page of a travel website that advertises their services -->
 ```
 
-#### Passed Example 6
+#### Passed Example 9
 This `img` element is perceived as a heading. It passes this rule because its text content is relevant, despite failing other WCAG criteria by lacking an accessible name.
 ```html
-<!-- The image of text below is large and reads "Our Mortgage Interest Rates" -->
-<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
-<!-- Followed by a data table showing different rates for different amortizations -->
+	<!-- The image of text below is large and reads "Our Mortgage Interest Rates" -->
+	<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
+	<!-- Followed by a data table showing different rates for different amortizations -->
 ```
 
+
+______________________ CHANGES MADE FINISH HERE _____________________________
+
+
 ### Failed
 
 #### Failed Example 1

From 4d002c05cfebbf289aa8ad678ae22bd9ba1a0f75 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 17:18:59 -0400
Subject: [PATCH 07/19] Fix link formatting for section headings resource

---
 _rules/heading-descriptive-b49b2e.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 2790629c4a..424aec59b4 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -68,7 +68,7 @@ This rule is inherently subjective and relies entirely on human judgment; it is
 ### Other Resources
 - [Understanding Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html)
 - [G130: Providing descriptive headings](https://www.w3.org/WAI/WCAG22/Techniques/general/G130)
-- [Understanding Success Criterion 2.4.10 Section Headings)](https://www.w3.org/WAI/WCAG21/Understanding/section-headings)
+- [Understanding Success Criterion 2.4.10 Section Headings](https://www.w3.org/WAI/WCAG21/Understanding/section-headings)
 - [Use headings to convey meaning and structure](https://www.w3.org/WAI/tips/writing/#use-headings-to-convey-meaning-and-structure)
 - [HTML Specification - Heading content](https://html.spec.whatwg.org/#heading-content)
 

From bca3157d3f85179eafb439d7f041ba66e419396d Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Mon, 29 Jun 2026 19:13:09 -0400
Subject: [PATCH 08/19] Refine heading examples in descriptive rules

---
 _rules/heading-descriptive-b49b2e.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 424aec59b4..0d06d76ec1 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -128,7 +128,7 @@ Headings that are compliant under this criterion, despite exhibiting other acces
 #### Passed Example 7
 This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, as the text is hidden from assistive technologies and has an insufficient contrast ratio.
 ```html
-	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts at Our University</h1>
+	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts Here, at Our University</h1>
 	<!-- Followed by the name of the university and some other promotional content -->
 ```
 
@@ -142,7 +142,7 @@ This `p` element is perceived as a heading. It passes this rule because its text
 #### Passed Example 9
 This `img` element is perceived as a heading. It passes this rule because its text content is relevant, despite failing other WCAG criteria by lacking an accessible name.
 ```html
-	<!-- The image of text below is large and reads "Our Mortgage Interest Rates" -->
+	<!-- The image of text below is large and reads "Today’s Mortgage Rates at Our Bank" -->
 	<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
 	<!-- Followed by a data table showing different rates for different amortizations -->
 ```

From 94c8e82e496b452bca6e02c615d54c9005c00fb9 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 11:02:41 -0400
Subject: [PATCH 09/19] Major update

Examples section (work-in-progress)
Text reviewed until Passed (situation D)
---
 _rules/heading-descriptive-b49b2e.md | 135 ++++++---------------------
 1 file changed, 30 insertions(+), 105 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 0d06d76ec1..2ccb829174 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -74,162 +74,87 @@ This rule is inherently subjective and relies entirely on human judgment; it is
 
 ## Test Cases
 
-### Passed (category 1)
+### Passed (situation A)
 Headings that are compliant under this criterion, while exhibiting no other accessibility or structural failures under WCAG.
 
 #### Passed Example 1
 This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
 	<h1>Renew Your Passport Online</h1>
-	<!-- Followed by a page that has instructions, images and a form about how to make the renewal application -->
+	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application -->
 ```
 
 #### Passed Example 2
 This `h1` element provides a relevant heading for the marketing content that follows it.
 ```html
-	<h1>Fresh deals just dropped: Printers/h1>
-	<!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
+<h1>Fresh deals just dropped: Printers</h1>
+<!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
 ```
 
 #### Passed Example 3
 This `h1` element provides a relevant heading for the informational data that follows it.
 ```html
 	<h1>Current Weather in New York</h1>
-	<!-- Followed by a data table that contains icons and other legend -->
+	<!-- Followed by a data table that contains info about the weather forecast -->
 ```
 
-### Passed (category 2)
+### Passed (situation B)
 Headings that serve as structural or sequential identifiers, which are inherently compliant regardless of the specific content that follows.
+Similarly:  
+- Headings denoting standard document sections – such as "Glossary," "Summary," or "Appendix" – are inherently compliant, unless an obvious error is observed.
+- Headings serving as call-to-action items, reminders, or warnings followed by list items or other relevant content – such as "Don't Forget To:", "Please Bring...", or "Doors are closed at 10:00 pm sharp!" – are considered compliant, unless a clear contextual mismatch is observed (such as appearing on an unrelated page).
 
 #### Passed Example 4
-This `h1` element provides a sequential identifier for a major document section.
+This `h1` element provides a sequential identifier for a major document section. The content that follows makes no difference to the outcome of this test.
 ```html
 	<h1>Chapter 4</h1>
-	<!-- The content that follows can make no difference -->
+	<!-- Any content -->
 ```
 
 #### Passed Example 5
-This `h1` element provides a structural identifier for a section of a musical work.
+This `h1` element provides a structural identifier for a section of a musical work. The content that follows makes no difference to the outcome of this test, unless an obvious misplacement is observed.
 ```html
 	<h1>1st movement</h1>
 	<!-- The content that follows describes the mood of the first movement of a symphony -->
 ```
 
 #### Passed Example 6
-This `h1` element provides an official legal citation that serves as an unambiguous identifier for the section.
+This `h1` element is for a standard document section. The content that follows makes no difference unless an obvious error indicates it is not a glossary section.
 ```html
-	<h1>Act, SC 2002, c 29</h1>
-	<!-- The content that follows is about that specific act -->
+	<h1>Glossary</h1>
+	<!-- Terms and explanations of them -->
 ```
 
-### Passed (category 3)
+#### Passed Example 7
+This `h1` element is a reminder heading. The content that follows makes no difference unless a clear contextual mismatch indicates it belongs on another page.
+```html
+	<h1>Don't Forget To Bring:</h1>
+	<!-- The content that follows is an items list -->
+```
+
+### Passed (situation C)
 Headings that are compliant under this criterion, despite exhibiting other accessibility or structural failures under WCAG.
 
-#### Passed Example 7
-This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, as the text is hidden from assistive technologies and has an insufficient contrast ratio.
+#### Passed Example 8
+This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, such as hiding the text from assistive technologies and having a severely low contrast ratio.
 ```html
 	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts Here, at Our University</h1>
 	<!-- Followed by the name of the university and some other promotional content -->
 ```
 
-#### Passed Example 8
-This `p` element is perceived as a heading. It passes this rule because its text is relevant, despite failing other WCAG criteria by relying entirely on visual presentation to convey heading structure and utilizing an invalid ARIA role and value.
+#### Passed Example 9
+Because this `p` element looks like a heading, it is perceived as a heading. It passes this rule as its text is relevant, despite failing other WCAG criteria due to using changes in text presentation without using the appropriate markup and utilizing an invalid ARIA role and value.
 ```html
 	<p class="h1" role="headline">A Million Different Journeys</p>
 	<!-- Followed by the home page of a travel website that advertises their services -->
 ```
 
-#### Passed Example 9
-This `img` element is perceived as a heading. It passes this rule because its text content is relevant, despite failing other WCAG criteria by lacking an accessible name.
+#### Passed Example 10
+Because this `img` element is visually presented as a heading, it is perceived as a heading. It passes this rule as its text is relevant, despite failing other WCAG criteria by relying entirely on an image of text and lacking an accessible name.
 ```html
 	<!-- The image of text below is large and reads "Today’s Mortgage Rates at Our Bank" -->
 	<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
 	<!-- Followed by a data table showing different rates for different amortizations -->
 ```
 
-
-______________________ CHANGES MADE FINISH HERE _____________________________
-
-
-### Failed
-
-#### Failed Example 1
-
-This `h1` heading element does not describes the topic of the following paragraph.
-
-```html
-<html lang="en">
-	<h1>Weather</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
-```
-
-#### Failed Example 2
-
-This heading marked up with an [explicit role][] of `heading` does not describe the topic of the following paragraph.
-
-```html
-<html lang="en">
-	<span role="heading" aria-level="1">Weather</span>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
-```
-
-#### Failed Example 3
-
-This heading marked up with an [explicit role][] of `heading` does not describe the topic of the following paragraph. The heading is positioned off screen but is [included in the accessibility tree][].
-
-```html
-<html lang="en">
-	<span role="heading" aria-level="1" style="position: absolute; top: -9999px; left: -9999px;">Weather</span>
-	<p>
-		We are open Monday through Friday from 10 to 16
-	</p>
-</html>
-```
-
-#### Failed Example 4
-
-This `h1` heading element does not describe the first [perceivable content][] after it (the first `p` element). The next [perceivable content][] (the second `p` element) is not considered by this rule.
-
-```html
-<html lang="en">
-	<h1>Weather</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-	<p>It is going to rain tomorrow</p>
-</html>
-```
-
-### Inapplicable
-
-#### Inapplicable Example 1
-
-There is no heading.
-
-```html
-<html lang="en">
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
-```
-
-#### Inapplicable Example 2
-
-This `h1` heading element is not [included in the accessibility tree][].
-
-```html
-<html lang="en">
-	<h1 hidden>Opening Hours</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
-```
-
-[decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure decoration'
-[flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree'
-[included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree'
-[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution'
-[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships ' Success Criterion 1.3.1 Info and Relationships'
-[sc246]: https://www.w3.org/TR/WCAG22/#headings-and-labels 'Success Criterion 2.4.6 Headings and Labels'
-[semantic role]: #semantic-role 'Definition of semantic role'
-[visible]: #visible 'Definition of visible'
-[accessible name]: #accessible-name 'Definition of accessible name'
-[perceivable content]: #perceivable-content 'Definition of perceivable content'
+### Passed (situation D)

From 640c92b786fa68648e04669a3541b914e4c3007e Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 12:26:35 -0400
Subject: [PATCH 10/19] Examples added until Passed (Situation E)

---
 _rules/heading-descriptive-b49b2e.md | 48 ++++++++++++++++++++++++----
 1 file changed, 42 insertions(+), 6 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 2ccb829174..ea614e462e 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -74,7 +74,7 @@ This rule is inherently subjective and relies entirely on human judgment; it is
 
 ## Test Cases
 
-### Passed (situation A)
+### Passed (Situation A)
 Headings that are compliant under this criterion, while exhibiting no other accessibility or structural failures under WCAG.
 
 #### Passed Example 1
@@ -87,8 +87,8 @@ This `h1` element provides a relevant heading that states the functional purpose
 #### Passed Example 2
 This `h1` element provides a relevant heading for the marketing content that follows it.
 ```html
-<h1>Fresh deals just dropped: Printers</h1>
-<!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
+  <h1>Fresh deals just dropped: Printers</h1>
+  <!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
 ```
 
 #### Passed Example 3
@@ -98,7 +98,7 @@ This `h1` element provides a relevant heading for the informational data that fo
 	<!-- Followed by a data table that contains info about the weather forecast -->
 ```
 
-### Passed (situation B)
+### Passed (Situation B)
 Headings that serve as structural or sequential identifiers, which are inherently compliant regardless of the specific content that follows.
 Similarly:  
 - Headings denoting standard document sections – such as "Glossary," "Summary," or "Appendix" – are inherently compliant, unless an obvious error is observed.
@@ -132,7 +132,7 @@ This `h1` element is a reminder heading. The content that follows makes no diffe
 	<!-- The content that follows is an items list -->
 ```
 
-### Passed (situation C)
+### Passed (Situation C)
 Headings that are compliant under this criterion, despite exhibiting other accessibility or structural failures under WCAG.
 
 #### Passed Example 8
@@ -157,4 +157,40 @@ Because this `img` element is visually presented as a heading, it is perceived a
 	<!-- Followed by a data table showing different rates for different amortizations -->
 ```
 
-### Passed (situation D)
+### Passed (Situation D)
+Headings that are compliant under this criterion by remaining meaningful and relevant, irrespective of whether they could be optimized for length, contain redundant phrasing, are entirely unnecessary, or provide editorially unnecessary descriptions.
+
+#### Passed Example 11
+This `h1` element provides a relevant heading from which the purpose of the page content can be understood. It passes this rule despite being overly casual and including unnecessary details.
+```html
+	<h1>Welcome to Our State-of-the-art New Wizard That Will Mail Your Driver's Licence Home</h1>
+	<!-- Followed by a page that has instructions, images, and a form about how to make the driver's licence renewal application -->
+```
+
+#### Passed Example 12
+This `h1` element provides a relevant heading from which the purpose of the page content can be understood. It passes this rule despite containing completely redundant phrasing.
+```html
+	<h1>Travel Advisories and Travel Advisory Information</h1>
+	<!-- Followed by a page that contains a list of hyperlinks to sections about other countries -->
+```
+
+#### Passed Example 13
+This `h2` element accurately describes the content of the promotional banner that follows it. It passes this rule despite being entirely unnecessary, as it repeats the text of the accompanying `figcaption` element verbatim.
+```html
+	<h2>Our hotel, conveniently located near the historic town center, features 118 guest rooms and 18 luxury suites</h2>
+	<figure>
+		<img src="hotel-promo-banner.png" alt="Panoramic view of a mountain ski resort in winter, with the modern hotel facade illuminated in the foreground." />
+		<figcaption>Our hotel, conveniently located near the historic town center, features 118 guest rooms and 18 luxury suites.</figcaption>
+	</figure>
+```
+
+#### Passed Example 14
+This `h2` element provides a relevant heading that accurately describes the content of the section. It passes this rule despite being editorially unnecessary because the following list of hyperlinks makes the purpose of the section immediately obvious. Although an alternative like "Links to External Resources" would provide better clarity, headings cannot be deemed non-compliant under this rule for merely stating the obvious, as such choices remain strictly within the editorial domain.
+```html
+	<h2>List of Links</h2>
+	<!-- Followed by a list of links to external resources -->
+```
+
+### Passed (Situation E)
+
+______________________ CHANGES MADE FINISH HERE _____________________________

From 28e978de1bbfaf22cd36ce48f997bc061d03d193 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 14:49:07 -0400
Subject: [PATCH 11/19] Ends at Failed example 9

---
 _rules/heading-descriptive-b49b2e.md | 107 +++++++++++++++++++++++++++
 1 file changed, 107 insertions(+)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index ea614e462e..9ec18a0ea2 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -192,5 +192,112 @@ This `h2` element provides a relevant heading that accurately describes the cont
 ```
 
 ### Passed (Situation E)
+Headings whose relevance or relationship to the section content is not immediately apparent, but becomes evident upon evaluation of the surrounding content or structural context.
+
+#### Passed Example 15
+This `h2` element uses a satirical or metaphorical phrase to introduce the topic. Although the heading text does not literally match the vocabulary of the section, its contextual relevance becomes evident when considering the immediate context of the paragraph that follows. Headings that use literary devices remain compliant under this rule, as the determination of tone or stylistic approach falls within the editorial domain.
+```html
+	<h2>Final Day for Savings</h2>
+  <p>Everything will be more expensive tomorrow.</p>
+	<!-- Followed by the subsection of an analysis article about inflation that begins with the above paragraph, explaining how long-term economic trends cause prices to rise continuously. -->
+```
+
+#### Passed Example 16
+This `h1` element employs irony to introduce the topic. Although the heading text does not explicitly reference the literal vocabulary of the section, its contextual relevance becomes evident when the primary purpose of the content is determined. Headings that utilize literary or stylistic devices remain compliant under this rule, as the determination of editorial tone falls outside the scope of accessibility evaluation.
+```html
+	<h1>Nobel's Peace Prize Office is Temporarily Closed Due to Declining Business</h1>
+	<!-- Followed by an opinion piece that provides statistics regarding active global conflicts and advocates for international peace. -->
+```
+
+#### Passed Example 16
+This `h3` element employs an interrogative structure to introduce the section topic. Although the heading itself asks a question rather than providing a direct declaration, its contextual relevance becomes immediately evident upon evaluating the concise response that follows in the immediate text. 
+```html
+	<h3>Opening hours?</h3>
+	<p>24/7</p>
+  <p>No opening hours. We are at your service round the clock!<p>
+```
+
+### Failed (Situation A)
+Headings that contain unintended or malformed text resulting from programmatic errors, publishing anomalies, or unremoved development artifacts. These structural failures are typically identifiable through programmatic or visual evaluation without requiring a deep analysis of the surrounding content.
+
+#### Failed Example 1
+This `h1` element contains unremoved placeholder text from a content template. It fails this rule because the text serves as a developmental instruction rather than describing the purpose or topic of the page content.
+```html
+	<h1>[Replace this text with heading 1]</h1>
+```
+
+#### Failed Example 2
+This `h1` element contains a raw back-end runtime error message injected during server-side execution. It fails this rule because the displayed text is a system-generated message rather than an intentional heading describing the purpose or topic of the page content.
+```html
+	<h1>Uncaught Error: Call to undefined function get_user_data() in /var/www/html/profile.php on line 42</h1>
+	<!-- Followed by a page with a form that collects user information. -->  
+```
+
+#### Failed Example 3
+This `h1` element contains only a raw timestamp. Due to a publishing or layout logic failure, this metadata was incorrectly rendered within the primary heading container rather than as a document footer element. It fails this rule because the date and time string do not identify or describe the primary purpose or topic of the page content.
+```html
+  <h1>2026-06-30 13:46 UTC</h1>
+  <!-- Followed by the list of academic programs available at a college -->
+```
+
+### Failed (Situation B)
+Headings that consist entirely of generic phrases, sequential locators, or conversational greetings that, on their face, lack the descriptive property required to identify a specific topic. Because these labels are inherently ambiguous, they typically fail this rule based on their textual content alone, without necessitating any evaluation of the surrounding content.
+
+#### Failed Example 4
+This `h1` element contains a brief, conversational greeting. It fails this rule on its face because the informal text possesses no descriptive value and provides no indication of the highly specific transactional nature of the form that follows.
+```html
+  <h1>Hi</h1>
+  <!-- Followed by a form that collects personal and financial data for a credit card application -->
+```
+
+#### Failed Example 5
+This `h1` element consists solely of a sequential placeholder. It fails this rule because the text lacks any topic-specific descriptor to identify the subject of the section, unless the page is part of a multi-volume document or a strictly paginated publication where the sequence itself serves as the primary identifier. A rapid evaluation of the immediate context confirms that this is a standard product listing, meaning the sequential label provides no descriptive utility.
+```html
+  <h1>Page 1</h1>
+  <!-- Followed by a list of kitchen appliances on sale -->
+```
+
+#### Failed Example 6
+This `span` element utilizes the `role="heading"` attribute to programmatically identify itself as an `h1` equivalent, but contains a generic operational description of the site structure rather than a descriptive label for the current view. It fails this rule because the text describes the navigational tier instead of identifying the unique topic, aggregate purpose, or functional scope of the content that follows; consequently, it provides no discernable indication whatsoever regarding the actual nature of the articles being presented.
+```html
+  <span role="heading" aria-level="1">Home Page of Our Newspaper</span>
+  <!-- Followed by several image buttons that open their own articles  -->
+```
+
+### Failed (Situation C)
+Headings that contain explicitly incorrect, mislabeled, or contradictory information that misrepresents the actual purpose, functional scope, or transactional nature of the content that follows.
+Unlike subjective editorial choices, these failures are characterized by objective, glaring mismatches that can be easily identified by a human reviewer within seconds of contextual evaluation. This situation focuses primarily on structural errors that cause immediate, severe consequences for most users, but especially for screen reader users and for users with cognitive disabilities the consequences may be more severe.
+
+#### Failed Example 7
+This `h2` element misrepresents the operational direction of a financial transaction. The element fails this rule because the heading text explicitly contradicts the functional purpose of the content it introduces.
+By providing an entirely inaccurate label for the transaction, the heading possesses zero descriptive utility and fails to identify the true topic or purpose. When a heading explicitly states an inbound transaction ("Request Money") but the interactive form executes an outbound transaction ("Send Money"), a user may inadvertently authorize an irreversible transfer of funds, resulting in immediate financial loss.
+```html
+  <h2>Request Money</h2>
+  <!-- Followed by the e-transfer screen for sending out money -->
+```
+
+#### Failed Example 8
+This `h1` element contains an explicit mismatch regarding the organizational topic of the page. At first glance, a user or tester is led to believe they are accessing Human Resources information, only to find that the subsequent headings and content are obviously dedicated to Information Technology.
+The `h1` element fails this rule because the primary heading text explicitly misidentifies the subject matter of the content it precedes. A rapid evaluation of the heading structure reveals a direct contradiction between the primary title and the functional content sections, meaning the h1 provides zero accurate descriptive value for the document view.
+
+```html
+<h1>Contact Human Resources</h1>
+<main>
+  <h2>Information Technology (IT) management contact information</h2>
+  <!-- Followed by a list of emails and phones of managers and directors with their job titles clearly posted under their names -->
+</main>
+```
+
+#### Failed Example 9
+This `h1` element contains an explicitly erroneous transactional label, which is directly refuted by the form labels and input fields immediately following it. This `h1` element fails this rule because the primary heading text provides a completely false description of the page's functional utility.
+
+```html
+<h1>Apply for Urgent Passport Renewal</h1>
+<main>
+  <label for="dl-number">Enter your 15-digit Driver's Licence Number:</label>
+  <input type="text" id="dl-number" name="dlNumber" required>
+  <!-- Followed by fields for driving restrictions, vision test results, and vehicle class selections -->
+</main>
+```
 
 ______________________ CHANGES MADE FINISH HERE _____________________________

From 5a978e04095eeee87ad372a9f2e168478afa22af Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 16:44:32 -0400
Subject: [PATCH 12/19] Until Failed Example 12

Updated comments in HTML examples for consistency by adding periods at the end of sentences.
---
 _rules/heading-descriptive-b49b2e.md | 92 +++++++++++++++++++++-------
 1 file changed, 70 insertions(+), 22 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 9ec18a0ea2..009a56f825 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -81,21 +81,21 @@ Headings that are compliant under this criterion, while exhibiting no other acce
 This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
 	<h1>Renew Your Passport Online</h1>
-	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application -->
+	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application. -->
 ```
 
 #### Passed Example 2
 This `h1` element provides a relevant heading for the marketing content that follows it.
 ```html
   <h1>Fresh deals just dropped: Printers</h1>
-  <!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
+  <!-- Followed by a carousel displaying newly arrived printers on a shopping website. -->
 ```
 
 #### Passed Example 3
 This `h1` element provides a relevant heading for the informational data that follows it.
 ```html
 	<h1>Current Weather in New York</h1>
-	<!-- Followed by a data table that contains info about the weather forecast -->
+	<!-- Followed by a data table that contains info about the weather forecast. -->
 ```
 
 ### Passed (Situation B)
@@ -108,28 +108,28 @@ Similarly:
 This `h1` element provides a sequential identifier for a major document section. The content that follows makes no difference to the outcome of this test.
 ```html
 	<h1>Chapter 4</h1>
-	<!-- Any content -->
+	<!-- Any content. -->
 ```
 
 #### Passed Example 5
 This `h1` element provides a structural identifier for a section of a musical work. The content that follows makes no difference to the outcome of this test, unless an obvious misplacement is observed.
 ```html
 	<h1>1st movement</h1>
-	<!-- The content that follows describes the mood of the first movement of a symphony -->
+	<!-- The content that follows describes the mood of the first movement of a symphony. -->
 ```
 
 #### Passed Example 6
 This `h1` element is for a standard document section. The content that follows makes no difference unless an obvious error indicates it is not a glossary section.
 ```html
 	<h1>Glossary</h1>
-	<!-- Terms and explanations of them -->
+	<!-- Terms and explanations of them. -->
 ```
 
 #### Passed Example 7
 This `h1` element is a reminder heading. The content that follows makes no difference unless a clear contextual mismatch indicates it belongs on another page.
 ```html
 	<h1>Don't Forget To Bring:</h1>
-	<!-- The content that follows is an items list -->
+	<!-- The content that follows is an items list. -->
 ```
 
 ### Passed (Situation C)
@@ -139,22 +139,22 @@ Headings that are compliant under this criterion, despite exhibiting other acces
 This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, such as hiding the text from assistive technologies and having a severely low contrast ratio.
 ```html
 	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts Here, at Our University</h1>
-	<!-- Followed by the name of the university and some other promotional content -->
+	<!-- Followed by the name of the university and some other promotional content. -->
 ```
 
 #### Passed Example 9
 Because this `p` element looks like a heading, it is perceived as a heading. It passes this rule as its text is relevant, despite failing other WCAG criteria due to using changes in text presentation without using the appropriate markup and utilizing an invalid ARIA role and value.
 ```html
 	<p class="h1" role="headline">A Million Different Journeys</p>
-	<!-- Followed by the home page of a travel website that advertises their services -->
+	<!-- Followed by the home page of a travel website that advertises their services. -->
 ```
 
 #### Passed Example 10
 Because this `img` element is visually presented as a heading, it is perceived as a heading. It passes this rule as its text is relevant, despite failing other WCAG criteria by relying entirely on an image of text and lacking an accessible name.
 ```html
-	<!-- The image of text below is large and reads "Today’s Mortgage Rates at Our Bank" -->
+	<!-- The image of text below is large and reads "Today’s Mortgage Rates at Our Bank". -->
 	<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
-	<!-- Followed by a data table showing different rates for different amortizations -->
+	<!-- Followed by a data table showing different rates for different amortizations. -->
 ```
 
 ### Passed (Situation D)
@@ -164,14 +164,14 @@ Headings that are compliant under this criterion by remaining meaningful and rel
 This `h1` element provides a relevant heading from which the purpose of the page content can be understood. It passes this rule despite being overly casual and including unnecessary details.
 ```html
 	<h1>Welcome to Our State-of-the-art New Wizard That Will Mail Your Driver's Licence Home</h1>
-	<!-- Followed by a page that has instructions, images, and a form about how to make the driver's licence renewal application -->
+	<!-- Followed by a page that has instructions, images, and a form about how to make the driver's licence renewal application. -->
 ```
 
 #### Passed Example 12
 This `h1` element provides a relevant heading from which the purpose of the page content can be understood. It passes this rule despite containing completely redundant phrasing.
 ```html
 	<h1>Travel Advisories and Travel Advisory Information</h1>
-	<!-- Followed by a page that contains a list of hyperlinks to sections about other countries -->
+	<!-- Followed by a page that contains a list of hyperlinks to sections about other countries. -->
 ```
 
 #### Passed Example 13
@@ -188,7 +188,7 @@ This `h2` element accurately describes the content of the promotional banner tha
 This `h2` element provides a relevant heading that accurately describes the content of the section. It passes this rule despite being editorially unnecessary because the following list of hyperlinks makes the purpose of the section immediately obvious. Although an alternative like "Links to External Resources" would provide better clarity, headings cannot be deemed non-compliant under this rule for merely stating the obvious, as such choices remain strictly within the editorial domain.
 ```html
 	<h2>List of Links</h2>
-	<!-- Followed by a list of links to external resources -->
+	<!-- Followed by a list of links to external resources. -->
 ```
 
 ### Passed (Situation E)
@@ -217,6 +217,30 @@ This `h3` element employs an interrogative structure to introduce the section to
   <p>No opening hours. We are at your service round the clock!<p>
 ```
 
+### Passed (Situation F)
+Headings that are compliant under this criterion, while containing errors in spelling, punctuation, capitalization, syntax, vocabulary, or structure. They may also include replicated text fragments resulting from copy-paste errors. These headings are considered passing if the text remains fairly intelligible. This is because the severity of these errors does not introduce ambiguity, distort the user's comprehension of the page structure, or cause any adverse material impact on any group of users.
+
+#### Passed Example 17
+This `h2` element contains a combination of language errors. Despite the poor linguistic quality of the text, it remains compliant with this rule because the meaning is completely preserved, leaving no room for user misinterpretation or navigational barriers.
+```html
+	<h2>The Goverment is Planing to Introducing New Regulations!.</h2>
+	<!-- Followed by an opinion piece about the upcoming regulations. -->
+```
+
+#### Passed Example 18
+This `h3` element contains a duplicated text fragment and a trailing white space resulting from a mechanical copy-paste or rendering error. It remains compliant because the core descriptive intent remains entirely unambiguous, not introducing a risk for user misunderstanding.
+```html
+	<h3>Contact Contact Customer Support </h3>
+	<!-- Followed by the contact details for customer support. -->
+```
+
+#### Passed Example 19
+This `h2` element utilizes an incorrect word substitution resulting from a literal cross-linguistic translation. While the word "command" cannot replace "order" in English here, the heading remains compliant because the immediate operational context allows the action to be unmistakably understood, not introducing a risk for user misunderstanding.
+```html
+  <h2>Command your food for delivery</h2>
+  <!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button -->
+```
+
 ### Failed (Situation A)
 Headings that contain unintended or malformed text resulting from programmatic errors, publishing anomalies, or unremoved development artifacts. These structural failures are typically identifiable through programmatic or visual evaluation without requiring a deep analysis of the surrounding content.
 
@@ -237,7 +261,7 @@ This `h1` element contains a raw back-end runtime error message injected during
 This `h1` element contains only a raw timestamp. Due to a publishing or layout logic failure, this metadata was incorrectly rendered within the primary heading container rather than as a document footer element. It fails this rule because the date and time string do not identify or describe the primary purpose or topic of the page content.
 ```html
   <h1>2026-06-30 13:46 UTC</h1>
-  <!-- Followed by the list of academic programs available at a college -->
+  <!-- Followed by the list of academic programs available at a college. -->
 ```
 
 ### Failed (Situation B)
@@ -247,21 +271,21 @@ Headings that consist entirely of generic phrases, sequential locators, or conve
 This `h1` element contains a brief, conversational greeting. It fails this rule on its face because the informal text possesses no descriptive value and provides no indication of the highly specific transactional nature of the form that follows.
 ```html
   <h1>Hi</h1>
-  <!-- Followed by a form that collects personal and financial data for a credit card application -->
+  <!-- Followed by a form that collects personal and financial data for a credit card application. -->
 ```
 
 #### Failed Example 5
 This `h1` element consists solely of a sequential placeholder. It fails this rule because the text lacks any topic-specific descriptor to identify the subject of the section, unless the page is part of a multi-volume document or a strictly paginated publication where the sequence itself serves as the primary identifier. A rapid evaluation of the immediate context confirms that this is a standard product listing, meaning the sequential label provides no descriptive utility.
 ```html
   <h1>Page 1</h1>
-  <!-- Followed by a list of kitchen appliances on sale -->
+  <!-- Followed by a list of kitchen appliances on sale. -->
 ```
 
 #### Failed Example 6
 This `span` element utilizes the `role="heading"` attribute to programmatically identify itself as an `h1` equivalent, but contains a generic operational description of the site structure rather than a descriptive label for the current view. It fails this rule because the text describes the navigational tier instead of identifying the unique topic, aggregate purpose, or functional scope of the content that follows; consequently, it provides no discernable indication whatsoever regarding the actual nature of the articles being presented.
 ```html
   <span role="heading" aria-level="1">Home Page of Our Newspaper</span>
-  <!-- Followed by several image buttons that open their own articles  -->
+  <!-- Followed by several image buttons that open their own articles. -->
 ```
 
 ### Failed (Situation C)
@@ -273,7 +297,7 @@ This `h2` element misrepresents the operational direction of a financial transac
 By providing an entirely inaccurate label for the transaction, the heading possesses zero descriptive utility and fails to identify the true topic or purpose. When a heading explicitly states an inbound transaction ("Request Money") but the interactive form executes an outbound transaction ("Send Money"), a user may inadvertently authorize an irreversible transfer of funds, resulting in immediate financial loss.
 ```html
   <h2>Request Money</h2>
-  <!-- Followed by the e-transfer screen for sending out money -->
+  <!-- Followed by the e-transfer screen for sending out money. -->
 ```
 
 #### Failed Example 8
@@ -284,7 +308,7 @@ The `h1` element fails this rule because the primary heading text explicitly mis
 <h1>Contact Human Resources</h1>
 <main>
   <h2>Information Technology (IT) management contact information</h2>
-  <!-- Followed by a list of emails and phones of managers and directors with their job titles clearly posted under their names -->
+  <!-- Followed by a list of emails and phones of managers and directors with their job titles clearly posted under their names. -->
 </main>
 ```
 
@@ -296,8 +320,32 @@ This `h1` element contains an explicitly erroneous transactional label, which is
 <main>
   <label for="dl-number">Enter your 15-digit Driver's Licence Number:</label>
   <input type="text" id="dl-number" name="dlNumber" required>
-  <!-- Followed by fields for driving restrictions, vision test results, and vehicle class selections -->
+  <!-- Followed by fields for driving restrictions, vision test results, and vehicle class selections. -->
 </main>
 ```
 
-______________________ CHANGES MADE FINISH HERE _____________________________
+### Failed (Situation D)
+Headings that are non-compliant under this criterion, due to containing errors in spelling, punctuation, capitalization, syntax, vocabulary, or structure. They may also include replicated text fragments resulting from copy-paste errors. These headings are considered failing if the text no longer remains fairly intelligible. This is because the severity of these errors introduces ambiguity, distorts the user's comprehension of the page structure, or causes an adverse material impact on some group of users.
+
+#### Failed Example 10
+This `h2` element contains severe mechanical typographical errors that render the phrase meaningless. The linguistic corruption crosses the threshold of fair intelligibility. It fails to comply with this criterion because the structural degradation of the text prevents users from determining the topic or purpose of the subsequent content.
+```html
+	<h2>The go ver ings new reguions</h2>
+	<!-- Followed by an opinion piece about the upcoming regulations. -->
+```
+
+#### Failed Example 11
+This `h3` element contains fragmented, truncated text resulting from a catastrophic copy-paste or rendering error. It fails to comply with this criterion because the remaining text fragment fails to convey any meaningful topic, leaving it entirely irrelevant to the underlying content.
+```html
+	<h3>ortcontact Custo</h3>
+	<!-- Followed by the contact details for customer support. -->
+```
+
+#### Failed Example 12
+This `h2` element utilizes an incorrect word substitution resulting from a literal cross-linguistic translation. While the developer intended to convey "finalize or complete your order," the word "terminate" instead implies canceling or deleting the items. The heading is non-compliant because it introduces severe ambiguity and a risk of user misunderstanding.
+```html
+  <h2>Terminate your food basket here</h2>
+  <!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button of an online food delivery company. -->
+```
+______________________ CHANGES MADE END HERE _____________________________
+

From 227b7d5e8dd3e522f441fab94d66d627cc5a0ece Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 17:00:26 -0400
Subject: [PATCH 13/19] ends at #### Failed Example 12

Updated comments in HTML examples to remove unnecessary punctuation.
---
 _rules/heading-descriptive-b49b2e.md | 100 ++++++++++++++-------------
 1 file changed, 51 insertions(+), 49 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 009a56f825..3d47e49511 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -81,21 +81,21 @@ Headings that are compliant under this criterion, while exhibiting no other acce
 This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
 	<h1>Renew Your Passport Online</h1>
-	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application. -->
+	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application -->
 ```
 
 #### Passed Example 2
 This `h1` element provides a relevant heading for the marketing content that follows it.
 ```html
   <h1>Fresh deals just dropped: Printers</h1>
-  <!-- Followed by a carousel displaying newly arrived printers on a shopping website. -->
+  <!-- Followed by a carousel displaying newly arrived printers on a shopping website -->
 ```
 
 #### Passed Example 3
 This `h1` element provides a relevant heading for the informational data that follows it.
 ```html
 	<h1>Current Weather in New York</h1>
-	<!-- Followed by a data table that contains info about the weather forecast. -->
+	<!-- Followed by a data table that contains info about the weather forecast -->
 ```
 
 ### Passed (Situation B)
@@ -108,28 +108,28 @@ Similarly:
 This `h1` element provides a sequential identifier for a major document section. The content that follows makes no difference to the outcome of this test.
 ```html
 	<h1>Chapter 4</h1>
-	<!-- Any content. -->
+	<!-- Any content -->
 ```
 
 #### Passed Example 5
 This `h1` element provides a structural identifier for a section of a musical work. The content that follows makes no difference to the outcome of this test, unless an obvious misplacement is observed.
 ```html
 	<h1>1st movement</h1>
-	<!-- The content that follows describes the mood of the first movement of a symphony. -->
+	<!-- The content that follows describes the mood of the first movement of a symphony -->
 ```
 
 #### Passed Example 6
 This `h1` element is for a standard document section. The content that follows makes no difference unless an obvious error indicates it is not a glossary section.
 ```html
 	<h1>Glossary</h1>
-	<!-- Terms and explanations of them. -->
+	<!-- Terms and explanations of them -->
 ```
 
 #### Passed Example 7
 This `h1` element is a reminder heading. The content that follows makes no difference unless a clear contextual mismatch indicates it belongs on another page.
 ```html
 	<h1>Don't Forget To Bring:</h1>
-	<!-- The content that follows is an items list. -->
+	<!-- The content that follows is an items list -->
 ```
 
 ### Passed (Situation C)
@@ -139,22 +139,22 @@ Headings that are compliant under this criterion, despite exhibiting other acces
 This `h1` element provides a relevant heading that states the purpose of the page content. It passes this rule despite exhibiting other WCAG failures, such as hiding the text from assistive technologies and having a severely low contrast ratio.
 ```html
 	<h1 style="color: darkgrey; background-color: black;" aria-hidden="true">Your Future Starts Here, at Our University</h1>
-	<!-- Followed by the name of the university and some other promotional content. -->
+	<!-- Followed by the name of the university and some other promotional content -->
 ```
 
 #### Passed Example 9
 Because this `p` element looks like a heading, it is perceived as a heading. It passes this rule as its text is relevant, despite failing other WCAG criteria due to using changes in text presentation without using the appropriate markup and utilizing an invalid ARIA role and value.
 ```html
 	<p class="h1" role="headline">A Million Different Journeys</p>
-	<!-- Followed by the home page of a travel website that advertises their services. -->
+	<!-- Followed by the home page of a travel website that advertises their services -->
 ```
 
 #### Passed Example 10
 Because this `img` element is visually presented as a heading, it is perceived as a heading. It passes this rule as its text is relevant, despite failing other WCAG criteria by relying entirely on an image of text and lacking an accessible name.
 ```html
-	<!-- The image of text below is large and reads "Today’s Mortgage Rates at Our Bank". -->
+	<!-- The image of text below is large and reads "Today’s Mortgage Rates at Our Bank" -->
 	<img src="image-of-text.png" style="max-width: 100%; height: auto;" alt="" />
-	<!-- Followed by a data table showing different rates for different amortizations. -->
+	<!-- Followed by a data table showing different rates for different amortizations -->
 ```
 
 ### Passed (Situation D)
@@ -164,14 +164,14 @@ Headings that are compliant under this criterion by remaining meaningful and rel
 This `h1` element provides a relevant heading from which the purpose of the page content can be understood. It passes this rule despite being overly casual and including unnecessary details.
 ```html
 	<h1>Welcome to Our State-of-the-art New Wizard That Will Mail Your Driver's Licence Home</h1>
-	<!-- Followed by a page that has instructions, images, and a form about how to make the driver's licence renewal application. -->
+	<!-- Followed by a page that has instructions, images, and a form about how to make the driver's licence renewal application -->
 ```
 
 #### Passed Example 12
 This `h1` element provides a relevant heading from which the purpose of the page content can be understood. It passes this rule despite containing completely redundant phrasing.
 ```html
 	<h1>Travel Advisories and Travel Advisory Information</h1>
-	<!-- Followed by a page that contains a list of hyperlinks to sections about other countries. -->
+	<!-- Followed by a page that contains a list of hyperlinks to sections about other countries -->
 ```
 
 #### Passed Example 13
@@ -188,7 +188,7 @@ This `h2` element accurately describes the content of the promotional banner tha
 This `h2` element provides a relevant heading that accurately describes the content of the section. It passes this rule despite being editorially unnecessary because the following list of hyperlinks makes the purpose of the section immediately obvious. Although an alternative like "Links to External Resources" would provide better clarity, headings cannot be deemed non-compliant under this rule for merely stating the obvious, as such choices remain strictly within the editorial domain.
 ```html
 	<h2>List of Links</h2>
-	<!-- Followed by a list of links to external resources. -->
+	<!-- Followed by a list of links to external resources -->
 ```
 
 ### Passed (Situation E)
@@ -199,14 +199,14 @@ This `h2` element uses a satirical or metaphorical phrase to introduce the topic
 ```html
 	<h2>Final Day for Savings</h2>
   <p>Everything will be more expensive tomorrow.</p>
-	<!-- Followed by the subsection of an analysis article about inflation that begins with the above paragraph, explaining how long-term economic trends cause prices to rise continuously. -->
+	<!-- Followed by the subsection of an analysis article about inflation that begins with the above paragraph, explaining how long-term economic trends cause prices to rise continuously -->
 ```
 
 #### Passed Example 16
 This `h1` element employs irony to introduce the topic. Although the heading text does not explicitly reference the literal vocabulary of the section, its contextual relevance becomes evident when the primary purpose of the content is determined. Headings that utilize literary or stylistic devices remain compliant under this rule, as the determination of editorial tone falls outside the scope of accessibility evaluation.
 ```html
 	<h1>Nobel's Peace Prize Office is Temporarily Closed Due to Declining Business</h1>
-	<!-- Followed by an opinion piece that provides statistics regarding active global conflicts and advocates for international peace. -->
+	<!-- Followed by an opinion piece that provides statistics regarding active global conflicts and advocates for international peace -->
 ```
 
 #### Passed Example 16
@@ -224,21 +224,21 @@ Headings that are compliant under this criterion, while containing errors in spe
 This `h2` element contains a combination of language errors. Despite the poor linguistic quality of the text, it remains compliant with this rule because the meaning is completely preserved, leaving no room for user misinterpretation or navigational barriers.
 ```html
 	<h2>The Goverment is Planing to Introducing New Regulations!.</h2>
-	<!-- Followed by an opinion piece about the upcoming regulations. -->
+	<!-- Followed by an opinion piece about the upcoming regulations -->
 ```
 
 #### Passed Example 18
 This `h3` element contains a duplicated text fragment and a trailing white space resulting from a mechanical copy-paste or rendering error. It remains compliant because the core descriptive intent remains entirely unambiguous, not introducing a risk for user misunderstanding.
 ```html
 	<h3>Contact Contact Customer Support </h3>
-	<!-- Followed by the contact details for customer support. -->
+	<!-- Followed by the contact details for customer support -->
 ```
 
 #### Passed Example 19
 This `h2` element utilizes an incorrect word substitution resulting from a literal cross-linguistic translation. While the word "command" cannot replace "order" in English here, the heading remains compliant because the immediate operational context allows the action to be unmistakably understood, not introducing a risk for user misunderstanding.
 ```html
-  <h2>Command your food for delivery</h2>
-  <!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button -->
+	<h2>Command your food for delivery</h2>
+	<!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button -->
 ```
 
 ### Failed (Situation A)
@@ -254,14 +254,14 @@ This `h1` element contains unremoved placeholder text from a content template. I
 This `h1` element contains a raw back-end runtime error message injected during server-side execution. It fails this rule because the displayed text is a system-generated message rather than an intentional heading describing the purpose or topic of the page content.
 ```html
 	<h1>Uncaught Error: Call to undefined function get_user_data() in /var/www/html/profile.php on line 42</h1>
-	<!-- Followed by a page with a form that collects user information. -->  
+	<!-- Followed by a page with a form that collects user information -->  
 ```
 
 #### Failed Example 3
 This `h1` element contains only a raw timestamp. Due to a publishing or layout logic failure, this metadata was incorrectly rendered within the primary heading container rather than as a document footer element. It fails this rule because the date and time string do not identify or describe the primary purpose or topic of the page content.
 ```html
-  <h1>2026-06-30 13:46 UTC</h1>
-  <!-- Followed by the list of academic programs available at a college. -->
+	<h1>2026-06-30 13:46 UTC</h1>
+	<!-- Followed by the list of academic programs available at a college -->
 ```
 
 ### Failed (Situation B)
@@ -270,22 +270,22 @@ Headings that consist entirely of generic phrases, sequential locators, or conve
 #### Failed Example 4
 This `h1` element contains a brief, conversational greeting. It fails this rule on its face because the informal text possesses no descriptive value and provides no indication of the highly specific transactional nature of the form that follows.
 ```html
-  <h1>Hi</h1>
-  <!-- Followed by a form that collects personal and financial data for a credit card application. -->
+	<h1>Hi</h1>
+	<!-- Followed by a form that collects personal and financial data for a credit card application -->
 ```
 
 #### Failed Example 5
 This `h1` element consists solely of a sequential placeholder. It fails this rule because the text lacks any topic-specific descriptor to identify the subject of the section, unless the page is part of a multi-volume document or a strictly paginated publication where the sequence itself serves as the primary identifier. A rapid evaluation of the immediate context confirms that this is a standard product listing, meaning the sequential label provides no descriptive utility.
 ```html
-  <h1>Page 1</h1>
-  <!-- Followed by a list of kitchen appliances on sale. -->
+	<h1>Page 1</h1>
+	<!-- Followed by a list of kitchen appliances on sale -->
 ```
 
 #### Failed Example 6
 This `span` element utilizes the `role="heading"` attribute to programmatically identify itself as an `h1` equivalent, but contains a generic operational description of the site structure rather than a descriptive label for the current view. It fails this rule because the text describes the navigational tier instead of identifying the unique topic, aggregate purpose, or functional scope of the content that follows; consequently, it provides no discernable indication whatsoever regarding the actual nature of the articles being presented.
 ```html
-  <span role="heading" aria-level="1">Home Page of Our Newspaper</span>
-  <!-- Followed by several image buttons that open their own articles. -->
+	<span role="heading" aria-level="1">Home Page of Our Newspaper</span>
+	<!-- Followed by several image buttons that open their own articles -->
 ```
 
 ### Failed (Situation C)
@@ -296,8 +296,8 @@ Unlike subjective editorial choices, these failures are characterized by objecti
 This `h2` element misrepresents the operational direction of a financial transaction. The element fails this rule because the heading text explicitly contradicts the functional purpose of the content it introduces.
 By providing an entirely inaccurate label for the transaction, the heading possesses zero descriptive utility and fails to identify the true topic or purpose. When a heading explicitly states an inbound transaction ("Request Money") but the interactive form executes an outbound transaction ("Send Money"), a user may inadvertently authorize an irreversible transfer of funds, resulting in immediate financial loss.
 ```html
-  <h2>Request Money</h2>
-  <!-- Followed by the e-transfer screen for sending out money. -->
+	<h2>Request Money</h2>
+	<!-- Followed by the e-transfer screen for sending out money -->
 ```
 
 #### Failed Example 8
@@ -305,47 +305,49 @@ This `h1` element contains an explicit mismatch regarding the organizational top
 The `h1` element fails this rule because the primary heading text explicitly misidentifies the subject matter of the content it precedes. A rapid evaluation of the heading structure reveals a direct contradiction between the primary title and the functional content sections, meaning the h1 provides zero accurate descriptive value for the document view.
 
 ```html
-<h1>Contact Human Resources</h1>
-<main>
-  <h2>Information Technology (IT) management contact information</h2>
-  <!-- Followed by a list of emails and phones of managers and directors with their job titles clearly posted under their names. -->
-</main>
+	<h1>Contact Human Resources</h1>
+	<main>
+		<h2>Information Technology (IT) management contact information</h2>
+		<!-- Followed by a list of emails and phones of managers and directors with their job titles clearly posted under their names -->
+	</main>
 ```
 
 #### Failed Example 9
 This `h1` element contains an explicitly erroneous transactional label, which is directly refuted by the form labels and input fields immediately following it. This `h1` element fails this rule because the primary heading text provides a completely false description of the page's functional utility.
 
 ```html
-<h1>Apply for Urgent Passport Renewal</h1>
-<main>
-  <label for="dl-number">Enter your 15-digit Driver's Licence Number:</label>
-  <input type="text" id="dl-number" name="dlNumber" required>
-  <!-- Followed by fields for driving restrictions, vision test results, and vehicle class selections. -->
-</main>
+	<h1>Apply for Urgent Passport Renewal</h1>
+	<main>
+		<label for="dl-number">Enter your 15-digit Driver's Licence Number:</label>
+		<input type="text" id="dl-number" name="dlNumber" required>
+		<!-- Followed by fields for driving restrictions, vision test results, and vehicle class selections -->
+	</main>
 ```
 
 ### Failed (Situation D)
-Headings that are non-compliant under this criterion, due to containing errors in spelling, punctuation, capitalization, syntax, vocabulary, or structure. They may also include replicated text fragments resulting from copy-paste errors. These headings are considered failing if the text no longer remains fairly intelligible. This is because the severity of these errors introduces ambiguity, distorts the user's comprehension of the page structure, or causes an adverse material impact on some group of users.
+Headings that contain errors in spelling, punctuation, capitalization, syntax, vocabulary, or structure. They may also include replicated text fragments resulting from copy-paste errors. These headings are considered failing if the text no longer remains fairly intelligible. This is because the severity of these errors introduces ambiguity, distorts the user's comprehension of the page structure, or causes an adverse material impact on some group of users.
 
 #### Failed Example 10
-This `h2` element contains severe mechanical typographical errors that render the phrase meaningless. The linguistic corruption crosses the threshold of fair intelligibility. It fails to comply with this criterion because the structural degradation of the text prevents users from determining the topic or purpose of the subsequent content.
+This `h2` element contains severe mechanical text fragments and truncations, likely caused by an automated find-and-replace or script error. It fails to comply with this criterion because the structural degradation of the words prevents users from determining the topic or purpose of the subsequent content.
+
 ```html
-	<h2>The go ver ings new reguions</h2>
-	<!-- Followed by an opinion piece about the upcoming regulations. -->
+	<h2>The gov regu next year</h2>
+	<!-- Followed by an opinion piece about upcoming government regulations -->
 ```
 
 #### Failed Example 11
 This `h3` element contains fragmented, truncated text resulting from a catastrophic copy-paste or rendering error. It fails to comply with this criterion because the remaining text fragment fails to convey any meaningful topic, leaving it entirely irrelevant to the underlying content.
 ```html
 	<h3>ortcontact Custo</h3>
-	<!-- Followed by the contact details for customer support. -->
+	<!-- Followed by the contact details for customer support -->
 ```
 
 #### Failed Example 12
 This `h2` element utilizes an incorrect word substitution resulting from a literal cross-linguistic translation. While the developer intended to convey "finalize or complete your order," the word "terminate" instead implies canceling or deleting the items. The heading is non-compliant because it introduces severe ambiguity and a risk of user misunderstanding.
 ```html
-  <h2>Terminate your food basket here</h2>
-  <!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button of an online food delivery company. -->
+	<h2>Terminate your food basket here</h2>
+	<!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button of an online food delivery company -->
 ```
 ______________________ CHANGES MADE END HERE _____________________________
 
+

From ed200e1153bb1be1aeac1403fc25e46c7b1713a1 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 17:17:45 -0400
Subject: [PATCH 14/19] Minor edits in Background

Clarified the definition of 'content' in relation to headings and corrected a comment in the passed example.
---
 _rules/heading-descriptive-b49b2e.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 3d47e49511..4ae590b5c0 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -45,7 +45,7 @@ Each heading is relevant to the content on the page where it appears. This conte
 ## Background
 This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all equally applicable under this rule.
 
-To pass, a heading must convey meaning and be relevant to its associated content. Headings consisting purely of non-default placeholder text or uninformative character strings fail this rule inherently. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
+To pass, a heading must convey meaning and be relevant to its associated content. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
 
 ### Assumptions
 This rule assumes that the tester evaluating the content possesses the necessary language proficiency and contextual comprehension required to assess the relationship between the headings and their associated content. 
@@ -81,7 +81,7 @@ Headings that are compliant under this criterion, while exhibiting no other acce
 This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
 	<h1>Renew Your Passport Online</h1>
-	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application -->
+	<!-- Followed by a page that has instructions, images, and a form to make the renewal application -->
 ```
 
 #### Passed Example 2

From c12e930c1dc4c901d4d6dcf822d02d3eb6c05597 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Tue, 30 Jun 2026 23:00:40 -0400
Subject: [PATCH 15/19] Minor language edits and reorganised sections

---
 _rules/heading-descriptive-b49b2e.md | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 4ae590b5c0..e30e4595ce 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -29,12 +29,14 @@ acknowledgments:
 ## Applicability
 This rule applies to any visible content that is perceived as a heading on a given page, as well as to any semantic heading element that is [included in the accessibility tree](included-in-the-accessibility-tree "Definition of included in the accessibility tree") while not visible. In other words, this rule applies to headings and their relation to the content, regardless of their compliance with any other accessibility criteria.
 
-This rule requires that testing be limited to the wording in headings, in plain language.
+This rule requires that testing be limited to the wording in everything that can be perceived or presented as headings.
+
+Because evaluating the relevance and meaning of textual content is non-technical, findings may be subject to varying interpretations by individuals regardless of their technical background. Consequently, this rule is designed as a test-to-pass evaluation, assuming failures are exceptions. Testers should default to a passing or not applicable result, when in doubt.
 
 ### None of the following is within this rule's scope:
 - Complete lack of headings
 - Heading structure and hierarchy (incorrectly nested, skipped, or missing heading levels, or heading elements that do not follow a logical sequence)
-- Source code errors, provided that the heading is visible or exposed to assistive technologies
+- Coding errors, provided that the heading is visible or exposed to assistive technologies
 - Grammar or spelling errors in headings, unless they render the text entirely unintelligible
 - Styling and presentation, unless the styling renders the heading completely illegible
 - Other accessibility failures covered by distinct WCAG success criteria, regardless of their severity
@@ -43,27 +45,29 @@ This rule requires that testing be limited to the wording in headings, in plain
 Each heading is relevant to the content on the page where it appears. This content may encompass the entire page, the section or paragraph immediately following the heading, or elements clustered within its visual or structural scope.
 
 ## Background
-This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all equally applicable under this rule.
+This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all subject to this rule.
 
-To pass, a heading must convey meaning and be relevant to its associated content. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
+To pass, a heading must convey meaning and be relevant to its associated content. Headings consisting purely of non-default placeholder text or uninformative character strings fail this rule inherently. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
 
 ### Assumptions
-This rule assumes that the tester evaluating the content possesses the necessary language proficiency and contextual comprehension required to assess the relationship between the headings and their associated content. 
+This rule assumes that testers evaluating the content possess the necessary language proficiency and contextual comprehension required to assess the relationship between the headings and their associated content. 
 
 #### Limitations
 The following scenarios present inherent limitations to evaluation, and the headings being tested may be deemed out of scope:
 - Multilingual Content: Web pages containing content in multiple languages (e.g., a heading in one language preceding content in another) where the tester does not possess professional working proficiency in all languages present.
 - Rapidly Changing or Real-Time Content Streams: Live, dynamic content fields (e.g., streaming data feeds, live social walls, or active chat interfaces) where the content updates at a rate that prevents static evaluation against its structural headings.
 - Transient Loading States: Temporary layout interfaces, such as skeletal loaders or placeholder templates, where the final text content has not yet completely rendered in the Document Object Model (DOM).
+- This rule is inherently subjective and relies entirely on human judgment; it is not intended for automated testing tools.
 
 #### Exceptions
-The following scenarios constitute exceptions to this rule, as the contextual intent of the author cannot be objectively determined by a general evaluator:
-- Highly Specialized or Technical Domains: Content involving advanced scientific, technical, or academic material (e.g., specialized research documentation) that requires domain-specific expertise.
-- Abstract or Creative Works: Content consisting of creative literary works, poetry, or abstract text where relevance is interpretive or non-linear rather than purely informational.
-- Legally Mandated or Standardized Boilerplate: Documents or user interfaces where the text and structure of headings are rigidly dictated by statutory, regulatory, or legal mandates (e.g., standardized privacy disclosures or government forms) and cannot be altered by the author.
+The following scenarios constitute exceptions to this rule, as the contextual intent of the author cannot be objectively determined by a web accessibility content guidelines specialist:
+- Highly specialized or technical domains: content involving advanced scientific, technical, or academic material (e.g., specialized research documentation) that requires domain-specific expertise.
+- Abstract or creative Works: content consisting of creative literary works, poetry, or abstract text where relevance is interpretive or non-linear rather than purely informational.
+- Legally mundated or standardized statements: documents or user interfaces where the text and structure of headings are rigidly dictated by statutory, regulatory, or legal mandates (e.g., standardized privacy disclosures) that cannot be altered by the author.
 
 ### Accessibility Support
-This rule is inherently subjective and relies entirely on human judgment; it is not intended for automated testing environments. Because evaluating the relevance of textual content is non-technical, findings may be subject to varying interpretations by individuals regardless of their technical background. Consequently, this rule is designed as a test-to-pass evaluation. Testers should default to a passing result unless an irrelevance or lack of meaning is obvious; any identified failure should be immediately apparent and acknowledgeable by the content creators or those familiar with the page context.
+This rule does not rely on the support for particular accessibility features by different assistive technologies and user agents. 
+
 
 ### Other Resources
 - [Understanding Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html)
@@ -81,7 +85,7 @@ Headings that are compliant under this criterion, while exhibiting no other acce
 This `h1` element provides a relevant heading that states the functional purpose of the page content.
 ```html
 	<h1>Renew Your Passport Online</h1>
-	<!-- Followed by a page that has instructions, images, and a form to make the renewal application -->
+	<!-- Followed by a page that has instructions, images, and a form about how to make the renewal application -->
 ```
 
 #### Passed Example 2
@@ -349,5 +353,3 @@ This `h2` element utilizes an incorrect word substitution resulting from a liter
 	<!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button of an online food delivery company -->
 ```
 ______________________ CHANGES MADE END HERE _____________________________
-
-

From c2637a569daf7656095e9acc7bfc9502a169b77f Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Wed, 1 Jul 2026 00:52:32 -0400
Subject: [PATCH 16/19] Changes in the "None of the following is within this
 rule's scope" section

---
 _rules/heading-descriptive-b49b2e.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index e30e4595ce..c69d99db6f 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -35,7 +35,7 @@ Because evaluating the relevance and meaning of textual content is non-technical
 
 ### None of the following is within this rule's scope:
 - Complete lack of headings
-- Heading structure and hierarchy (incorrectly nested, skipped, or missing heading levels, or heading elements that do not follow a logical sequence)
+- Heading structure or hierarchy
 - Coding errors, provided that the heading is visible or exposed to assistive technologies
 - Grammar or spelling errors in headings, unless they render the text entirely unintelligible
 - Styling and presentation, unless the styling renders the heading completely illegible

From eee1e6b1e4bfab6a82f7d850f922fc7a9a19a2d8 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Wed, 1 Jul 2026 02:09:15 -0400
Subject: [PATCH 17/19] Changes in "Expectations"

Updated the wording and structure of the rule to clarify the applicability and expectations regarding headings. Modified limitations and exceptions.
---
 _rules/heading-descriptive-b49b2e.md | 83 ++++++++++++++++++++++++----
 1 file changed, 72 insertions(+), 11 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index c69d99db6f..de6a5ce196 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -29,9 +29,7 @@ acknowledgments:
 ## Applicability
 This rule applies to any visible content that is perceived as a heading on a given page, as well as to any semantic heading element that is [included in the accessibility tree](included-in-the-accessibility-tree "Definition of included in the accessibility tree") while not visible. In other words, this rule applies to headings and their relation to the content, regardless of their compliance with any other accessibility criteria.
 
-This rule requires that testing be limited to the wording in everything that can be perceived or presented as headings.
-
-Because evaluating the relevance and meaning of textual content is non-technical, findings may be subject to varying interpretations by individuals regardless of their technical background. Consequently, this rule is designed as a test-to-pass evaluation, assuming failures are exceptions. Testers should default to a passing or not applicable result, when in doubt.
+The testing scope under this rule is limited exclusively to the wording in elements perceived or presented as headings.
 
 ### None of the following is within this rule's scope:
 - Complete lack of headings
@@ -41,8 +39,9 @@ Because evaluating the relevance and meaning of textual content is non-technical
 - Styling and presentation, unless the styling renders the heading completely illegible
 - Other accessibility failures covered by distinct WCAG success criteria, regardless of their severity
 
-## Expectation
-Each heading is relevant to the content on the page where it appears. This content may encompass the entire page, the section or paragraph immediately following the heading, or elements clustered within its visual or structural scope.
+## Expectations
+- Each heading text is sufficiently intelligible and carries meaning
+- Each heading is relevant to the specific page or section where it appears
 
 ## Background
 This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all subject to this rule.
@@ -53,11 +52,11 @@ To pass, a heading must convey meaning and be relevant to its associated content
 This rule assumes that testers evaluating the content possess the necessary language proficiency and contextual comprehension required to assess the relationship between the headings and their associated content. 
 
 #### Limitations
-The following scenarios present inherent limitations to evaluation, and the headings being tested may be deemed out of scope:
-- Multilingual Content: Web pages containing content in multiple languages (e.g., a heading in one language preceding content in another) where the tester does not possess professional working proficiency in all languages present.
-- Rapidly Changing or Real-Time Content Streams: Live, dynamic content fields (e.g., streaming data feeds, live social walls, or active chat interfaces) where the content updates at a rate that prevents static evaluation against its structural headings.
-- Transient Loading States: Temporary layout interfaces, such as skeletal loaders or placeholder templates, where the final text content has not yet completely rendered in the Document Object Model (DOM).
-- This rule is inherently subjective and relies entirely on human judgment; it is not intended for automated testing tools.
+The following scenarios present inherent limitations to evaluation and the headings being tested may be deemed out of scope:
+- Multilingual content: Web pages containing content in multiple languages (e.g., a heading in one language preceding content in another) where the tester does not possess professional working proficiency in all languages present.
+- Rapidly changing or real-time content streams: Live, dynamic content fields (e.g., streaming data feeds, live social walls, or active chat interfaces) where the content updates at a rate that prevents static evaluation against its structural headings.
+- Use of automated testing tools: This rule is inherently subjective and relies entirely on human judgment; it is not intended for automated testing tools.
+- Exposure to controversies: Because evaluating the relevance and meaning of textual content is non-technical, findings can be contested by anyone regardless of their technical background. Consequently, this rule is designed as a test-to-pass evaluation, meaning failures are exceptions. Testers should default to a passing or not applicable result when in doubt.
 
 #### Exceptions
 The following scenarios constitute exceptions to this rule, as the contextual intent of the author cannot be objectively determined by a web accessibility content guidelines specialist:
@@ -68,7 +67,6 @@ The following scenarios constitute exceptions to this rule, as the contextual in
 ### Accessibility Support
 This rule does not rely on the support for particular accessibility features by different assistive technologies and user agents. 
 
-
 ### Other Resources
 - [Understanding Success Criterion 2.4.6: Headings and Labels](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html)
 - [G130: Providing descriptive headings](https://www.w3.org/WAI/WCAG22/Techniques/general/G130)
@@ -353,3 +351,66 @@ This `h2` element utilizes an incorrect word substitution resulting from a liter
 	<!-- Followed by a digital menu interface, a shopping cart summary, and a checkout button of an online food delivery company -->
 ```
 ______________________ CHANGES MADE END HERE _____________________________
+
+
+
+
+
+#### Failed Example 3
+
+This heading marked up with an [explicit role][] of `heading` does not describe the topic of the following paragraph. The heading is positioned off screen but is [included in the accessibility tree][].
+
+```html
+<html lang="en">
+	<span role="heading" aria-level="1" style="position: absolute; top: -9999px; left: -9999px;">Weather</span>
+	<p>
+		We are open Monday through Friday from 10 to 16
+	</p>
+</html>
+```
+
+#### Failed Example 4
+
+This `h1` heading element does not describe the first [perceivable content][] after it (the first `p` element). The next [perceivable content][] (the second `p` element) is not considered by this rule.
+
+```html
+<html lang="en">
+	<h1>Weather</h1>
+	<p>We are open Monday through Friday from 10 to 16</p>
+	<p>It is going to rain tomorrow</p>
+</html>
+```
+
+### Inapplicable
+
+#### Inapplicable Example 1
+
+There is no heading.
+
+```html
+<html lang="en">
+	<p>We are open Monday through Friday from 10 to 16</p>
+</html>
+```
+
+#### Inapplicable Example 2
+
+This `h1` heading element is not [included in the accessibility tree][].
+
+```html
+<html lang="en">
+	<h1 hidden>Opening Hours</h1>
+	<p>We are open Monday through Friday from 10 to 16</p>
+</html>
+```
+
+[decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure decoration'
+[flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree'
+[included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree'
+[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution'
+[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships ' Success Criterion 1.3.1 Info and Relationships'
+[sc246]: https://www.w3.org/TR/WCAG22/#headings-and-labels 'Success Criterion 2.4.6 Headings and Labels'
+[semantic role]: #semantic-role 'Definition of semantic role'
+[visible]: #visible 'Definition of visible'
+[accessible name]: #accessible-name 'Definition of accessible name'
+[perceivable content]: #perceivable-content 'Definition of perceivable content'

From 0bb437d427de34d7a904ea80e7061b0896b96e88 Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Wed, 1 Jul 2026 02:10:55 -0400
Subject: [PATCH 18/19] Delete mistakenly pasted portion from the old file

---
 _rules/heading-descriptive-b49b2e.md | 62 ----------------------------
 1 file changed, 62 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index de6a5ce196..7730dc4c9f 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -352,65 +352,3 @@ This `h2` element utilizes an incorrect word substitution resulting from a liter
 ```
 ______________________ CHANGES MADE END HERE _____________________________
 
-
-
-
-
-#### Failed Example 3
-
-This heading marked up with an [explicit role][] of `heading` does not describe the topic of the following paragraph. The heading is positioned off screen but is [included in the accessibility tree][].
-
-```html
-<html lang="en">
-	<span role="heading" aria-level="1" style="position: absolute; top: -9999px; left: -9999px;">Weather</span>
-	<p>
-		We are open Monday through Friday from 10 to 16
-	</p>
-</html>
-```
-
-#### Failed Example 4
-
-This `h1` heading element does not describe the first [perceivable content][] after it (the first `p` element). The next [perceivable content][] (the second `p` element) is not considered by this rule.
-
-```html
-<html lang="en">
-	<h1>Weather</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-	<p>It is going to rain tomorrow</p>
-</html>
-```
-
-### Inapplicable
-
-#### Inapplicable Example 1
-
-There is no heading.
-
-```html
-<html lang="en">
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
-```
-
-#### Inapplicable Example 2
-
-This `h1` heading element is not [included in the accessibility tree][].
-
-```html
-<html lang="en">
-	<h1 hidden>Opening Hours</h1>
-	<p>We are open Monday through Friday from 10 to 16</p>
-</html>
-```
-
-[decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration 'WCAG definition of Pure decoration'
-[flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree 'Definition of flat tree'
-[included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of included in the accessibility tree'
-[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution'
-[sc131]: https://www.w3.org/TR/WCAG22/#info-and-relationships ' Success Criterion 1.3.1 Info and Relationships'
-[sc246]: https://www.w3.org/TR/WCAG22/#headings-and-labels 'Success Criterion 2.4.6 Headings and Labels'
-[semantic role]: #semantic-role 'Definition of semantic role'
-[visible]: #visible 'Definition of visible'
-[accessible name]: #accessible-name 'Definition of accessible name'
-[perceivable content]: #perceivable-content 'Definition of perceivable content'

From 57e2265e17e7e9a262ef55ab348e3b3606eba5fd Mon Sep 17 00:00:00 2001
From: Armagan Tekdoner <grifare@users.noreply.github.com>
Date: Wed, 1 Jul 2026 02:20:44 -0400
Subject: [PATCH 19/19] Changes in the "Background" section

---
 _rules/heading-descriptive-b49b2e.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md
index 7730dc4c9f..d2d877d1ef 100755
--- a/_rules/heading-descriptive-b49b2e.md
+++ b/_rules/heading-descriptive-b49b2e.md
@@ -44,9 +44,11 @@ The testing scope under this rule is limited exclusively to the wording in eleme
 - Each heading is relevant to the specific page or section where it appears
 
 ## Background
-This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While these varied implementations may simultaneously trigger failures under other WCAG success criteria, they are all subject to this rule.
+This rule evaluates any element that functions as a heading, including those perceived visually by sighted users or explicitly exposed as headings to assistive technologies. The scope encompasses fully accessible headings (e.g., `<h1>Meaningful and relevant heading</h1>`), visual headings that lack assistive technology support (e.g., `<p class="h1">Meaningful and relevant heading</p>`), and structural headings that are hidden from visual presentation (e.g., `<h1 class="visually-hidden">Meaningful and relevant heading</h1>`). While various implementations may simultaneously trigger failures under other WCAG success criteria, they are all subject to this rule.
 
-To pass, a heading must convey meaning and be relevant to its associated content. Headings consisting purely of non-default placeholder text or uninformative character strings fail this rule inherently. Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
+Under this rule, "content" refers to any textual or non-textual element presented on the web page, including sections, paragraphs, forms, user interface components, media galleries, lists, or hyperlinks.
+
+To pass, a heading must have a meaning and be relevant to its associated content. Headings consisting of placeholder text or uninformative character strings fail this rule inherently.
 
 ### Assumptions
 This rule assumes that testers evaluating the content possess the necessary language proficiency and contextual comprehension required to assess the relationship between the headings and their associated content.