From 6b7c55088f21739bf86b6a2d2da0135ba1f7ece9 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 13:46:59 -0800 Subject: [PATCH 01/26] first emphasis of quality in 2.2.4 --- understanding/20/headings-and-labels.html | 8 ++++---- understanding/20/labels-or-instructions.html | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 018e2eb24a..8c2c21a4e3 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,16 +31,16 @@

Intent of Headings and Labels

may suffice if it provides an appropriate cue to finding and navigating content.

-

This Success Criterion does not require headings or labels. This Success Criterion +

This Success Criterion does not require headings or labels -- for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or - identified – this aspect is covered separately by + identified –- that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly - marked up or identified), while failing this Success Criterion (if those headings or labels are not - sufficiently clear or descriptive). + marked up or identified), while failing this Success Criterion (if those headings or labels are inaccurate or not + sufficiently clear).

Further, in the case of labels, this Success Criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs has been diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 30eb30ecb2..3b9a7a1f1b 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -57,7 +57,7 @@

Intent of Labels or Instructions

interactive components) that are not associated with data entry.

While this Success Criterion requires that controls and inputs have labels or instructions, whether or - not labels (if used) are sufficiently clear or descriptive is covered separately by + not labels (if used) are accurate, sufficiently clear, or descriptive is covered separately by 2.4.6: Headings and Labels.

From 7bdeee0eb61e493e4e41be2c4e0f90e97b3c9c3c Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 13:48:55 -0800 Subject: [PATCH 02/26] Style update only put Success Criterion lower case except where it specifies a number, as per https://github.com/w3c/wcag/wiki/WCAG-2-style-guide --- understanding/20/headings-and-labels.html | 16 ++++++++-------- understanding/20/labels-or-instructions.html | 16 ++++++++-------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 8c2c21a4e3..0d4dafd3c2 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -20,7 +20,7 @@

In brief

Intent of Headings and Labels

-

The intent of this Success Criterion is to help users understand what information +

The intent of this success criterion is to help users understand what information is contained in Web pages and how that information is organized. When headings are clear and descriptive, users can find the information they seek more easily, and they can understand the relationships between different parts of the content more easily. @@ -31,22 +31,22 @@

Intent of Headings and Labels

may suffice if it provides an appropriate cue to finding and navigating content.

-

This Success Criterion does not require headings or labels -- for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion - requires that if headings or labels are provided, they be descriptive. This Success Criterion also +

This success criterion does not require headings or labels -- for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This success criterion + requires that if headings or labels are provided, they be descriptive. This success criterion also does not require that content acting as a heading or label be correctly marked up or identified –- that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content - to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing + to pass this success criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly - marked up or identified), while failing this Success Criterion (if those headings or labels are inaccurate or not + marked up or identified), while failing this success criterion (if those headings or labels are inaccurate or not sufficiently clear).

-

Further, in the case of labels, this Success Criterion does not take into consideration whether or not +

Further, in the case of labels, this success criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs has been used – this aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") - and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is not + and therefore pass Success Criterion 4.1.2, but to still fail this success criterion (if the label is not sufficiently clear or descriptive).

This success criterion does not require the use of labels; however, it does require that if labels are present, they must be sufficiently clear or descriptive. Please see 3.3.2: Labels or Instructions for more information on the use of labels. @@ -63,7 +63,7 @@

Benefits of Headings and Labels

  • Form input controls with labels that clearly describe the content that is expected to be entered helps users know how to successfully complete the form.
  • When headings and labels are also correctly marked up and identified in accordance with - 1.3.1: Info and Relationships, this Success Criterion + 1.3.1: Info and Relationships, this success criterion helps people who use screen readers by ensuring that labels and headings are clearer when presented in a different format – for example, in an automatically generated list of headings, a table of contents, or when jumping from heading to heading within a page.
    • diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 3b9a7a1f1b..4270e67b4a 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -21,7 +21,7 @@

    In brief

    Intent of Labels or Instructions

    -

    The intent of this Success Criterion is to have content authors present instructions +

    The intent of this success criterion is to have content authors present instructions or labels that identify the controls in a form so that users know what input data is expected. In the case of radio buttons, checkboxes, comboboxes, or similar controls that provide users with options, each option must have an appropriate label so that @@ -33,30 +33,30 @@

    Intent of Labels or Instructions

    verbose.

    -

    The intent of this Success Criterion is not to clutter the page with unnecessary information +

    The intent of this success criterion is not to clutter the page with unnecessary information but to provide important cues and instructions that will benefit people with disabilities. Too much information or instruction can be just as harmful as too little. The goal is to make certain that enough information is provided for the user to accomplish the task without undue confusion or navigation.

    -

    This Success Criterion does not require that labels or instructions be correctly marked up, +

    This success criterion does not require that labels or instructions be correctly marked up, identified, or associated with their respective controls - this aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content - to pass this Success Criterion (providing relevant labels and instructions) while failing + to pass this success criterion (providing relevant labels and instructions) while failing Success Criterion 1.3.1 (if the labels or instructions aren't correctly marked up, identified, or associated).

    -

    Further, this Success Criterion does not take into consideration whether or not alternative methods of +

    Further, this success criterion does not take into consideration whether or not alternative methods of providing an accessible name or description for form controls and inputs has been used - this aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name or description (e.g. using aria-label="...") - and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the labels or instructions + and therefore pass Success Criterion 4.1.2, but to still fail this success criterion (if the labels or instructions aren't presented to all users, not just those using assistive technologies).

    -

    This Success Criterion does not apply to links or other controls (such as an expand/collapse widget, or similar +

    This success criterion does not apply to links or other controls (such as an expand/collapse widget, or similar interactive components) that are not associated with data entry.

    -

    While this Success Criterion requires that controls and inputs have labels or instructions, whether or +

    While this success criterion requires that controls and inputs have labels or instructions, whether or not labels (if used) are accurate, sufficiently clear, or descriptive is covered separately by 2.4.6: Headings and Labels.

    From 6a3307d60e732a4b6191fb734a6b59d7cee6ac8f Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 13:52:05 -0800 Subject: [PATCH 03/26] Revert "Style update only" This reverts commit 7bdeee0eb61e493e4e41be2c4e0f90e97b3c9c3c. --- understanding/20/headings-and-labels.html | 16 ++++++++-------- understanding/20/labels-or-instructions.html | 16 ++++++++-------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 0d4dafd3c2..8c2c21a4e3 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -20,7 +20,7 @@

    In brief

    Intent of Headings and Labels

    -

    The intent of this success criterion is to help users understand what information +

    The intent of this Success Criterion is to help users understand what information is contained in Web pages and how that information is organized. When headings are clear and descriptive, users can find the information they seek more easily, and they can understand the relationships between different parts of the content more easily. @@ -31,22 +31,22 @@

    Intent of Headings and Labels

    may suffice if it provides an appropriate cue to finding and navigating content.

    -

    This success criterion does not require headings or labels -- for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This success criterion - requires that if headings or labels are provided, they be descriptive. This success criterion also +

    This Success Criterion does not require headings or labels -- for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion + requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified –- that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content - to pass this success criterion (providing descriptive content that acts as headings or labels) while failing + to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly - marked up or identified), while failing this success criterion (if those headings or labels are inaccurate or not + marked up or identified), while failing this Success Criterion (if those headings or labels are inaccurate or not sufficiently clear).

    -

    Further, in the case of labels, this success criterion does not take into consideration whether or not +

    Further, in the case of labels, this Success Criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs has been used – this aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") - and therefore pass Success Criterion 4.1.2, but to still fail this success criterion (if the label is not + and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is not sufficiently clear or descriptive).

    This success criterion does not require the use of labels; however, it does require that if labels are present, they must be sufficiently clear or descriptive. Please see 3.3.2: Labels or Instructions for more information on the use of labels. @@ -63,7 +63,7 @@

    Benefits of Headings and Labels

  • Form input controls with labels that clearly describe the content that is expected to be entered helps users know how to successfully complete the form.
  • When headings and labels are also correctly marked up and identified in accordance with - 1.3.1: Info and Relationships, this success criterion + 1.3.1: Info and Relationships, this Success Criterion helps people who use screen readers by ensuring that labels and headings are clearer when presented in a different format – for example, in an automatically generated list of headings, a table of contents, or when jumping from heading to heading within a page.
    • diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 4270e67b4a..3b9a7a1f1b 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -21,7 +21,7 @@

    In brief

    Intent of Labels or Instructions

    -

    The intent of this success criterion is to have content authors present instructions +

    The intent of this Success Criterion is to have content authors present instructions or labels that identify the controls in a form so that users know what input data is expected. In the case of radio buttons, checkboxes, comboboxes, or similar controls that provide users with options, each option must have an appropriate label so that @@ -33,30 +33,30 @@

    Intent of Labels or Instructions

    verbose.

    -

    The intent of this success criterion is not to clutter the page with unnecessary information +

    The intent of this Success Criterion is not to clutter the page with unnecessary information but to provide important cues and instructions that will benefit people with disabilities. Too much information or instruction can be just as harmful as too little. The goal is to make certain that enough information is provided for the user to accomplish the task without undue confusion or navigation.

    -

    This success criterion does not require that labels or instructions be correctly marked up, +

    This Success Criterion does not require that labels or instructions be correctly marked up, identified, or associated with their respective controls - this aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content - to pass this success criterion (providing relevant labels and instructions) while failing + to pass this Success Criterion (providing relevant labels and instructions) while failing Success Criterion 1.3.1 (if the labels or instructions aren't correctly marked up, identified, or associated).

    -

    Further, this success criterion does not take into consideration whether or not alternative methods of +

    Further, this Success Criterion does not take into consideration whether or not alternative methods of providing an accessible name or description for form controls and inputs has been used - this aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name or description (e.g. using aria-label="...") - and therefore pass Success Criterion 4.1.2, but to still fail this success criterion (if the labels or instructions + and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the labels or instructions aren't presented to all users, not just those using assistive technologies).

    -

    This success criterion does not apply to links or other controls (such as an expand/collapse widget, or similar +

    This Success Criterion does not apply to links or other controls (such as an expand/collapse widget, or similar interactive components) that are not associated with data entry.

    -

    While this success criterion requires that controls and inputs have labels or instructions, whether or +

    While this Success Criterion requires that controls and inputs have labels or instructions, whether or not labels (if used) are accurate, sufficiently clear, or descriptive is covered separately by 2.4.6: Headings and Labels.

    From 4d562e3388b7a8cadb31467914db35df4ec6d977 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 14:10:37 -0800 Subject: [PATCH 04/26] trivial editorial updates for consistency change "this" to "that"; made dashes be em dashes (without spaces) --- understanding/20/headings-and-labels.html | 16 +++++++--------- understanding/20/labels-or-instructions.html | 10 +++++----- 2 files changed, 12 insertions(+), 14 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 8c2c21a4e3..c441697080 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,25 +31,23 @@

    Intent of Headings and Labels

    may suffice if it provides an appropriate cue to finding and navigating content.

    -

    This Success Criterion does not require headings or labels -- for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion +

    This Success Criterion does not require headings or labels— for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or - identified –- that aspect is covered separately by + identified that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly - marked up or identified), while failing this Success Criterion (if those headings or labels are inaccurate or not - sufficiently clear). + marked up or identified), while failing this Success Criterion (if those headings or labels are inaccurate or insufficiently clear).

    Further, in the case of labels, this Success Criterion does not take into consideration whether or not - alternative methods of providing an accessible name for form controls and inputs has been - used – this aspect is covered separately by 4.1.2: Name, Role and Value. It is possible + alternative methods of providing an accessible name for form controls and inputs have been + used— that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") - and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is not - sufficiently clear or descriptive). + and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is not accurate or sufficiently clear or descriptive).

    -

    This success criterion does not require the use of labels; however, it does require that if labels are present, they must be sufficiently clear or descriptive. Please see 3.3.2: Labels or Instructions for more information on the use of labels. +

    This success criterion does not require the use of labels; however, it does require that if labels are present, they must be accurate and sufficiently clear or descriptive. Please see 3.3.2: Labels or Instructions for more information on the use of labels.

    diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 3b9a7a1f1b..51c4cf08fe 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -41,13 +41,13 @@

    Intent of Labels or Instructions

    This Success Criterion does not require that labels or instructions be correctly marked up, - identified, or associated with their respective controls - this aspect is covered separately by + identified, or associated with their respective controls—that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing relevant labels and instructions) while failing Success Criterion 1.3.1 (if the labels or instructions aren't correctly marked up, identified, or associated).

    Further, this Success Criterion does not take into consideration whether or not alternative methods of - providing an accessible name or description for form controls and inputs has been used - this aspect is + providing an accessible name or description for form controls and inputs has been used—this aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name or description (e.g. using aria-label="...") and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the labels or instructions @@ -69,8 +69,8 @@

    Benefits of Labels or Instructions

    • Providing labels and instructions (including examples of expected - data formats) helps all users - but particularly those with cognitive, language, and learning - disabilities - to enter information correctly. + data formats) helps all users—but particularly those with cognitive, language, and learning + disabilities—to enter information correctly.
    • Providing labels and instructions (including identification of required @@ -109,7 +109,7 @@

      Examples of Labels or Instructions

    • To enter their name, users are provided with two separate text fields. Rather than having a single label "Name" (which would appear to leave the second text field unlabelled), - each field is given an explicit label - "Given Name" and "Family Name". + each field is given an explicit label—"Given Name" and "Family Name".
    • A U.S. phone number separates the area code, exchange, and number into three fields. From 0410198e9b6be7bf81b4bc278e99775eff1fea49 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 14:12:05 -0800 Subject: [PATCH 05/26] Update headings-and-labels.html --- understanding/20/headings-and-labels.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index c441697080..c99902d137 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -34,7 +34,7 @@

      Intent of Headings and Labels

      This Success Criterion does not require headings or labels— for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or - identified that aspect is covered separately by + identified—that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, @@ -43,7 +43,7 @@

      Intent of Headings and Labels

      Further, in the case of labels, this Success Criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs have been - used— that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible + used—that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is not accurate or sufficiently clear or descriptive).

      From 6e9d7230789f9cc3404c1019d7ac19cf3a7e08aa Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 14:14:47 -0800 Subject: [PATCH 06/26] Update labels-or-instructions.html --- understanding/20/labels-or-instructions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 51c4cf08fe..446cf89fbc 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -47,7 +47,7 @@

      Intent of Labels or Instructions

      Success Criterion 1.3.1 (if the labels or instructions aren't correctly marked up, identified, or associated).

      Further, this Success Criterion does not take into consideration whether or not alternative methods of - providing an accessible name or description for form controls and inputs has been used—this aspect is + providing an accessible name or description for form controls and inputs has been used—that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name or description (e.g. using aria-label="...") and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the labels or instructions From 81461ebd382f26a054c4d83c6621617af6ccb5d0 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 14:23:30 -0800 Subject: [PATCH 07/26] Update headings-and-labels.html added "accuracy" to several examples and passages --- understanding/20/headings-and-labels.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index c99902d137..df2fbe786a 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -58,12 +58,12 @@

      Benefits of Headings and Labels

    • Descriptive headings are especially helpful for users who have disabilities that make reading slow and for people with limited short-term memory. These people benefit when section titles make it possible to predict what each section contains.
      • -
    • Form input controls with labels that clearly describe the content that is expected to be +
    • Form input controls with labels that clearly and accurately describe the content that is expected to be entered helps users know how to successfully complete the form.
    • When headings and labels are also correctly marked up and identified in accordance with 1.3.1: Info and Relationships, this Success Criterion helps people who use screen readers by ensuring that labels and headings are clearer when - presented in a different format – for example, in an automatically generated list of + presented in a different format—for example, in an automatically generated list of headings, a table of contents, or when jumping from heading to heading within a page.
    @@ -76,12 +76,12 @@

    Examples of Headings and Labels

    A news site
    The home page of a news site lists the headlines for the top stories of the hour. Under each heading are the first 35 words of the story and a link to the full article. - Each headline gives a clear idea of the article's subject.
    + Each headline gives a clear and accurate idea of the article's subject.
    A guide on how to write well
    A guide on writing contains the following section titles: How To Write Well, Cut Out Useless Words, Identify Unnecessary Words, and so on. The section headings are clear and concise and the structure of the information is - reflected in the structure of the headings.
    + accurately reflected in the structure of the headings.
    Consistent headings in different articles
    A Web site contains papers from a conference. Submissions to the conference are required to have the following organization: Summary, Introduction, [other sections unique From 3454e363f4b682761f51b4d023eaacd0d2cda37e Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 29 Jan 2025 14:31:35 -0800 Subject: [PATCH 08/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index df2fbe786a..52a0cbb1af 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -45,7 +45,7 @@

    Intent of Headings and Labels

    alternative methods of providing an accessible name for form controls and inputs have been used—that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") - and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is not accurate or sufficiently clear or descriptive). + and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is inaccurate or insufficiently clear or descriptive).

    This success criterion does not require the use of labels; however, it does require that if labels are present, they must be accurate and sufficiently clear or descriptive. Please see 3.3.2: Labels or Instructions for more information on the use of labels.

    From 93504bee2111d7fd362a4073da17b6b36643b0ef Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Tue, 25 Feb 2025 13:42:25 -0800 Subject: [PATCH 09/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 52a0cbb1af..4d8e1b4015 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,7 +31,7 @@

    Intent of Headings and Labels

    may suffice if it provides an appropriate cue to finding and navigating content.

    -

    This Success Criterion does not require headings or labels— for input labels, that consideration is covered separately by 3.3.2 Labels or Instructions. This Success Criterion +

    This Success Criterion does not require headings or labels—for inputs, consideration for labels are covered separately by 3.3.2 Labels or Instructions. This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified—that aspect is covered separately by From 9f8d47c1b2c6a3ca17c77998b11b11c422e7d45b Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Tue, 25 Feb 2025 13:43:26 -0800 Subject: [PATCH 10/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 4d8e1b4015..e1d8038ec8 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,7 +31,7 @@

    Intent of Headings and Labels

    may suffice if it provides an appropriate cue to finding and navigating content.

    -

    This Success Criterion does not require headings or labels—for inputs, consideration for labels are covered separately by 3.3.2 Labels or Instructions. This Success Criterion +

    This Success Criterion does not require headings or labels—for inputs, considerations for labels is covered separately by 3.3.2 Labels or Instructions. This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified—that aspect is covered separately by From 367c265d685743683411e8ce3efd01034004af43 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Tue, 25 Feb 2025 13:45:51 -0800 Subject: [PATCH 11/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index e1d8038ec8..42834aa270 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,7 +31,7 @@

    Intent of Headings and Labels

    may suffice if it provides an appropriate cue to finding and navigating content.

    -

    This Success Criterion does not require headings or labels—for inputs, considerations for labels is covered separately by 3.3.2 Labels or Instructions. This Success Criterion +

    This Success Criterion does not require headings or labels—labels for inputs are covered separately by 3.3.2 Labels or Instructions. This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified—that aspect is covered separately by From dd5220b2922fe8a06f7af5f48cca03ba9b95b8a1 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 28 Feb 2025 07:46:41 -0800 Subject: [PATCH 12/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 42834aa270..d40890b1e1 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,7 +31,7 @@

    Intent of Headings and Labels

    may suffice if it provides an appropriate cue to finding and navigating content.

    -

    This Success Criterion does not require headings or labels—labels for inputs are covered separately by 3.3.2 Labels or Instructions. This Success Criterion +

    This Success Criterion does not require headings or labels. (Labels for inputs are covered separately by 3.3.2 Labels or Instructions). This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified—that aspect is covered separately by From 34711d9670d82416bd2190ca2c4e07c1e66281a2 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 16:18:27 +0000 Subject: [PATCH 13/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index d40890b1e1..0a22823815 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -43,7 +43,7 @@

    Intent of Headings and Labels

    Further, in the case of labels, this Success Criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs have been - used—that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible + used — that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is inaccurate or insufficiently clear or descriptive).

    From fa4df1be75c71bfc43745559fd67d0867f67a934 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 16:18:50 +0000 Subject: [PATCH 14/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 0a22823815..065579345c 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -63,7 +63,7 @@

    Benefits of Headings and Labels

  • When headings and labels are also correctly marked up and identified in accordance with 1.3.1: Info and Relationships, this Success Criterion helps people who use screen readers by ensuring that labels and headings are clearer when - presented in a different format—for example, in an automatically generated list of + presented in a different format — for example, in an automatically generated list of headings, a table of contents, or when jumping from heading to heading within a page.
    • From 29414d829affbdec80790b18600d9f2711c0c158 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 16:19:24 +0000 Subject: [PATCH 15/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 065579345c..9ae89047a2 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -34,7 +34,7 @@

    Intent of Headings and Labels

    This Success Criterion does not require headings or labels. (Labels for inputs are covered separately by 3.3.2 Labels or Instructions). This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or - identified—that aspect is covered separately by + identified — that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, From f8a40d079a1a1e0bf6c410819742c7278f9d6bca Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 16:19:55 +0000 Subject: [PATCH 16/26] Update understanding/20/labels-or-instructions.html --- understanding/20/labels-or-instructions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 446cf89fbc..7c7dbdabf1 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -41,7 +41,7 @@

    Intent of Labels or Instructions

    This Success Criterion does not require that labels or instructions be correctly marked up, - identified, or associated with their respective controls—that aspect is covered separately by + identified, or associated with their respective controls — that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing relevant labels and instructions) while failing Success Criterion 1.3.1 (if the labels or instructions aren't correctly marked up, identified, or associated). From dd5868f8f4937ff2f9c42fbe9ca6f0e9b6194bff Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 22:04:38 +0000 Subject: [PATCH 17/26] Update understanding/20/labels-or-instructions.html --- understanding/20/labels-or-instructions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 7c7dbdabf1..032290fba6 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -70,7 +70,7 @@

    Benefits of Labels or Instructions

  • Providing labels and instructions (including examples of expected data formats) helps all users—but particularly those with cognitive, language, and learning - disabilities—to enter information correctly. + disabilities — to enter information correctly.
  • Providing labels and instructions (including identification of required From 6135b44fb9dbb066cf9ef08e30ab1affa3c7f0fa Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 22:04:55 +0000 Subject: [PATCH 18/26] Update understanding/20/labels-or-instructions.html --- understanding/20/labels-or-instructions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 032290fba6..d5e51724a2 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -69,7 +69,7 @@

    Benefits of Labels or Instructions

    • Providing labels and instructions (including examples of expected - data formats) helps all users—but particularly those with cognitive, language, and learning + data formats) helps all users — but particularly those with cognitive, language, and learning disabilities — to enter information correctly.
      • From 841baf358d62546a23ff50a322148773fe608823 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 22:05:19 +0000 Subject: [PATCH 19/26] Update understanding/20/labels-or-instructions.html --- understanding/20/labels-or-instructions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index d5e51724a2..11ddea97b4 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -109,7 +109,7 @@

      Examples of Labels or Instructions

    • To enter their name, users are provided with two separate text fields. Rather than having a single label "Name" (which would appear to leave the second text field unlabelled), - each field is given an explicit label—"Given Name" and "Family Name". + each field is given an explicit label — "Given Name" and "Family Name".
    • A U.S. phone number separates the area code, exchange, and number into three fields. From 84e65674b51dd0a1c800a58e8ae961c125b5d197 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 28 Feb 2025 22:05:45 +0000 Subject: [PATCH 20/26] Update understanding/20/labels-or-instructions.html --- understanding/20/labels-or-instructions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/labels-or-instructions.html b/understanding/20/labels-or-instructions.html index 11ddea97b4..cc75c1b557 100644 --- a/understanding/20/labels-or-instructions.html +++ b/understanding/20/labels-or-instructions.html @@ -47,7 +47,7 @@

      Intent of Labels or Instructions

      Success Criterion 1.3.1 (if the labels or instructions aren't correctly marked up, identified, or associated).

      Further, this Success Criterion does not take into consideration whether or not alternative methods of - providing an accessible name or description for form controls and inputs has been used—that aspect is + providing an accessible name or description for form controls and inputs has been used — that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name or description (e.g. using aria-label="...") and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the labels or instructions From 2f6acb69618ba54f5f059aba5512174b2c588e21 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 7 Mar 2025 10:11:20 -0800 Subject: [PATCH 21/26] Update headings-and-labels.html Update to swap out sentences in second paragraph, as discussed on TF call --- understanding/20/headings-and-labels.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 9ae89047a2..b6be2aaa89 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,8 +31,7 @@

      Intent of Headings and Labels

      may suffice if it provides an appropriate cue to finding and navigating content.

      -

      This Success Criterion does not require headings or labels. (Labels for inputs are covered separately by 3.3.2 Labels or Instructions). This Success Criterion - requires that if headings or labels are provided, they be descriptive. This Success Criterion also +

      This Success Criterion requires that if headings or labels are provided, they be descriptive.This Success Criterion does not require headings or labels; labels for inputs are covered separately by 3.3.2 Labels or Instructions. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified — that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content From 4bb1c38388781b1e15924e0ed9a8655b30b4c9de Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 7 Mar 2025 10:12:01 -0800 Subject: [PATCH 22/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index b6be2aaa89..72a321affb 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,7 +31,7 @@

      Intent of Headings and Labels

      may suffice if it provides an appropriate cue to finding and navigating content.

      -

      This Success Criterion requires that if headings or labels are provided, they be descriptive.This Success Criterion does not require headings or labels; labels for inputs are covered separately by 3.3.2 Labels or Instructions. This Success Criterion also +

      This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion does not require headings or labels; labels for inputs are covered separately by 3.3.2 Labels or Instructions. This Success Criterion also does not require that content acting as a heading or label be correctly marked up or identified — that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content From c33944c180d3d885e315a1ad418d0bf7c2610a61 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 21 Apr 2025 09:39:03 -0700 Subject: [PATCH 23/26] Apply suggestions from code review putting "success criterion" lower case where it does not directly precede a number --- understanding/20/headings-and-labels.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index 72a321affb..a6b9bc3991 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -31,14 +31,14 @@

      Intent of Headings and Labels

      may suffice if it provides an appropriate cue to finding and navigating content.

      -

      This Success Criterion requires that if headings or labels are provided, they be descriptive. This Success Criterion does not require headings or labels; labels for inputs are covered separately by 3.3.2 Labels or Instructions. This Success Criterion also +

      This success criterion requires that if headings or labels are provided, they be descriptive. This success criterion does not require headings or labels; labels for inputs are covered separately by 3.3.2 Labels or Instructions. This success criterion also does not require that content acting as a heading or label be correctly marked up or identified — that aspect is covered separately by 1.3.1: Info and Relationships. It is possible for content to pass this Success Criterion (providing descriptive content that acts as headings or labels) while failing Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely, it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly - marked up or identified), while failing this Success Criterion (if those headings or labels are inaccurate or insufficiently clear). + marked up or identified), while failing this success criterion (if those headings or labels are inaccurate or insufficiently clear).

      Further, in the case of labels, this Success Criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs have been From 3fee6034c8af0b0c7f50042d08bf216d4d8e43d2 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 21 Apr 2025 09:39:34 -0700 Subject: [PATCH 24/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index a6b9bc3991..f6c68dd583 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -60,7 +60,7 @@

      Benefits of Headings and Labels

    • Form input controls with labels that clearly and accurately describe the content that is expected to be entered helps users know how to successfully complete the form.
    • When headings and labels are also correctly marked up and identified in accordance with - 1.3.1: Info and Relationships, this Success Criterion + 1.3.1: Info and Relationships, this success criterion helps people who use screen readers by ensuring that labels and headings are clearer when presented in a different format — for example, in an automatically generated list of headings, a table of contents, or when jumping from heading to heading within a page.
      • From 06bb0f9bb14b6fbc35e884aaad2ebda177539655 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 21 Apr 2025 09:41:04 -0700 Subject: [PATCH 25/26] Update understanding/20/headings-and-labels.html --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index f6c68dd583..1ca4c116e5 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -44,7 +44,7 @@

      Intent of Headings and Labels

      alternative methods of providing an accessible name for form controls and inputs have been used — that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…") - and therefore pass Success Criterion 4.1.2, but to still fail this Success Criterion (if the label is inaccurate or insufficiently clear or descriptive). + and therefore pass Success Criterion 4.1.2, but to still fail this success criterion (if the label is inaccurate or insufficiently clear or descriptive).

      This success criterion does not require the use of labels; however, it does require that if labels are present, they must be accurate and sufficiently clear or descriptive. Please see 3.3.2: Labels or Instructions for more information on the use of labels.

      From 2969c3c6dac5bbcebe356fb85e9f1396a9ba51d7 Mon Sep 17 00:00:00 2001 From: "Kenneth G. Franqueiro" Date: Mon, 21 Apr 2025 13:04:19 -0400 Subject: [PATCH 26/26] Correct one missed merge conflict --- understanding/20/headings-and-labels.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html index d2d40cc3fb..38bfaf0a6b 100644 --- a/understanding/20/headings-and-labels.html +++ b/understanding/20/headings-and-labels.html @@ -40,7 +40,7 @@

      Intent of Headings and Labels

      it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly marked up or identified), while failing this success criterion (if those headings or labels are inaccurate or insufficiently clear).

      -

      Further, in the case of labels, this Success Criterion does not take into consideration whether or not +

      Further, in the case of labels, this success criterion does not take into consideration whether or not alternative methods of providing an accessible name for form controls and inputs have been used — that aspect is covered separately by 4.1.2: Name, Role and Value. It is possible for controls and inputs to have an appropriate accessible name (e.g. using aria-label="…")