From aa767f97b8ac03ba4de3dedadb297fdc2672377a Mon Sep 17 00:00:00 2001 From: Daniel Date: Mon, 8 Sep 2025 15:55:16 +0200 Subject: [PATCH 1/2] Accessibility support note on empty headings being exposed --- _rules/heading-descriptive-b49b2e.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_rules/heading-descriptive-b49b2e.md b/_rules/heading-descriptive-b49b2e.md index ab7f69a2a4..fe4f861c3f 100755 --- a/_rules/heading-descriptive-b49b2e.md +++ b/_rules/heading-descriptive-b49b2e.md @@ -42,7 +42,7 @@ Headings that are visible but not in the accessibility tree are a failure of [Su ### Assumptions -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 Label][sc246] is still satisfied. +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. 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 Label][sc246] is still satisfied. @@ -50,6 +50,8 @@ This rule also assumes that the content the heading is intended to describe is [ 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. +There is currently a screen reader / browser combination which actively exposes empty headings `` or `` when querying the sccreen reader for the list of page headings. These constructs are not applicable for this rule but can still cause accessibility issues if relying exclusively on that particular combination. + ### Bibliography - [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html) From d5bdbbf6faa8f4e6e5b7c6dcdcd224ec68155a90 Mon Sep 17 00:00:00 2001 From: Daniel Date: Tue, 9 Sep 2025 13:46:23 +0200 Subject: [PATCH 2/2] Fix typo --- _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 fe4f861c3f..9dab7146eb 100755 --- a/_rules/heading-descriptive-b49b2e.md +++ b/_rules/heading-descriptive-b49b2e.md @@ -50,7 +50,7 @@ This rule also assumes that the content the heading is intended to describe is [ 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. -There is currently a screen reader / browser combination which actively exposes empty headings `` or `` when querying the sccreen reader for the list of page headings. These constructs are not applicable for this rule but can still cause accessibility issues if relying exclusively on that particular combination. +There is currently a screen reader / browser combination which actively exposes empty headings `` or `` when querying the screen reader for the list of page headings. These constructs are not applicable for this rule but can still cause accessibility issues if relying exclusively on that particular combination. ### Bibliography