From 3ccea1130bd5df40db03abd7b9707a21f0fc319f Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 13 May 2025 18:03:26 -0500 Subject: [PATCH 01/13] Proposal 2 for 2.4.2 Page Titled This was Proposal 3 in the Google doc. --- comments-by-guideline-and-success-criterion.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 9e293ff6..da6abe57 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -566,19 +566,23 @@ See also the [Comments on Closed Functionality](#comments-on-closed-functionalit ###### Applying SC 2.4.2 Page Titled to Non-Web Documents and Software -This applies directly as written, and as described in [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent) replacing “Web pages” with “non-web documents or software”. +(for non-web documents) -With this substitution, it would read: +This applies directly as written, and as described in [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent) replacing "Page" with "Non-web document" and “Web pages” with “non-web documents”. -**2.4.2 Page Titled:** **[[Non-web documents](#document) or [software](#software)]** have titles that describe topic or purpose. +With this substitution, it would read: +**2.4.2 [Non-Web Document] Titled:** **[[Non-web documents](#document)]** have titles that describe topic or purpose.
-As described in the WCAG intent, the name of a [non-web software application](#software) or [non-web document](#document) (e.g. document, media file, etc.) is a sufficient title if it describes the topic or purpose.
-
- -Although not required by this success criterion, ensuring that individual windows or screens have a title (where that title describes the topic or purpose) addresses the user needs identified in the Understanding Success Criterion 2.4.2 Intent section, and is generally considered a best practice.
+As described in the WCAG intent, the name of a [non-web document](#document) (e.g. document, media file, etc.) is a sufficient title if it describes the topic or purpose. + +(for non-web software) + +For software, direct application of 2.4.2 Page Titled is problematic. The following criterion is recommended as a substitute: +[2.4.2 Non-web Software Name: “Where [software](#software) is in an environment that supports windows or pages/screens (as in mobile apps), has more than one window or page/screen, and there is a way to provide a programmatically determinable unique name for each, each window or page/screen is provided with a unique and meaningful name that can be used to distinguish them from each other.] +
Considering how the above substitute requirement is phrased, would there need to be a bullet in the Comments on Closed Functionality section?
See also the [Comments on Closed Functionality](#comments-on-closed-functionality).
From 66876b8e079575c03419a28b6b2a1eaf498e8f6e Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 13 May 2025 18:40:41 -0500 Subject: [PATCH 02/13] Add in bold text --- comments-by-guideline-and-success-criterion.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index da6abe57..e8124a46 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -579,9 +579,9 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. (for non-web software) -For software, direct application of 2.4.2 Page Titled is problematic. The following criterion is recommended as a substitute: +For non-web software, direct application of 2.4.2 Page Titled is problematic. The following criterion is recommended as a substitute: -[2.4.2 Non-web Software Name: “Where [software](#software) is in an environment that supports windows or pages/screens (as in mobile apps), has more than one window or page/screen, and there is a way to provide a programmatically determinable unique name for each, each window or page/screen is provided with a unique and meaningful name that can be used to distinguish them from each other.] +**[2.4.2 Non-web Software Name:** “Where [software](#software) is in an environment that supports windows or pages/screens (as in mobile apps), has more than one window or page/screen, and there is a way to provide a programmatically determinable unique name for each, each window or page/screen is provided with a unique and meaningful name that can be used to distinguish them from each other.]
Considering how the above substitute requirement is phrased, would there need to be a bullet in the Comments on Closed Functionality section?
From 282e66abda8f3df8c3e67cb83c17eabbe05abea2 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 13 May 2025 20:22:01 -0500 Subject: [PATCH 03/13] Incorporate the essence of language proposed in the 8 May meeting --- comments-by-guideline-and-success-criterion.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index e8124a46..62c5140e 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -579,13 +579,9 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. (for non-web software) -For non-web software, direct application of 2.4.2 Page Titled is problematic. The following criterion is recommended as a substitute: +This does not apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: -**[2.4.2 Non-web Software Name:** “Where [software](#software) is in an environment that supports windows or pages/screens (as in mobile apps), has more than one window or page/screen, and there is a way to provide a programmatically determinable unique name for each, each window or page/screen is provided with a unique and meaningful name that can be used to distinguish them from each other.] -
Considering how the above substitute requirement is phrased, would there need to be a bullet in the Comments on Closed Functionality section?
-
- -See also the [Comments on Closed Functionality](#comments-on-closed-functionality).
+**2.4.2 Non-web Software Name:** “In [software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. ##### focus-order From 8234d1cc9ca2b7c8a1204242126c575def26191c Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 13 May 2025 20:24:52 -0500 Subject: [PATCH 04/13] Remove extraneous quotation mark --- comments-by-guideline-and-success-criterion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 62c5140e..12985bd6 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -581,7 +581,7 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. This does not apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: -**2.4.2 Non-web Software Name:** “In [software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. +**2.4.2 Non-web Software Name:** In [software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. ##### focus-order From e742b651a89f849fa18cf6fe5a67b202289c3e8c Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 13 May 2025 20:26:52 -0500 Subject: [PATCH 05/13] Needed to add "non-web" to software --- comments-by-guideline-and-success-criterion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 12985bd6..fd6e98ee 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -581,7 +581,7 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. This does not apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: -**2.4.2 Non-web Software Name:** In [software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. +**2.4.2 Non-web Software Name:** In [non-web software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. ##### focus-order From b84440c2d7098c94596a9caf7b07833154e8cb72 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 13 May 2025 20:29:52 -0500 Subject: [PATCH 06/13] Change "non-web software name" to "non-web software named" --- comments-by-guideline-and-success-criterion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index fd6e98ee..68966f35 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -581,7 +581,7 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. This does not apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: -**2.4.2 Non-web Software Name:** In [non-web software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. +**2.4.2 Non-web Software Named:** In [non-web software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. ##### focus-order From 51ecdb19de805d724d963f79804a21c13b7c5a11 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 22 May 2025 10:18:55 -0500 Subject: [PATCH 07/13] use "success criterion is problematic to apply" --- comments-by-guideline-and-success-criterion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 68966f35..d6e2b898 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -579,7 +579,7 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. (for non-web software) -This does not apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: +This success criterion is problematic to apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: **2.4.2 Non-web Software Named:** In [non-web software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. From 583ffd6ec05c498f851b2b9f1ac97d2a3ba5a6a2 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 22 May 2025 10:21:43 -0500 Subject: [PATCH 08/13] Update short name per TF resolution to use "Titled" --- comments-by-guideline-and-success-criterion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index d6e2b898..cd10b1ac 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -581,7 +581,7 @@ As described in the WCAG intent, the name of a [non-web document](#document) (e. This success criterion is problematic to apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: -**2.4.2 Non-web Software Named:** In [non-web software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. +**2.4.2 Non-web Software Titled:** In [non-web software](#software) implemented on a platform that supports title attributes for windows or screens, titles are provided that are unique or differentiable within the software. ##### focus-order From 0df579ad19ce5838a8104ba6e446306b65b85cac Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 22 May 2025 10:58:54 -0500 Subject: [PATCH 09/13] Make first subheading cover only documents --- comments-by-guideline-and-success-criterion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index cd10b1ac..3b3b3ffd 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -564,7 +564,7 @@ See also the [Comments on Closed Functionality](#comments-on-closed-functionalit ##### page-titled -###### Applying SC 2.4.2 Page Titled to Non-Web Documents and Software +###### Applying SC 2.4.2 Page Titled to Non-Web Documents (for non-web documents) From a41d71fc02ac66447581322c5874a9459959a34f Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 22 May 2025 10:59:21 -0500 Subject: [PATCH 10/13] Remove parenthetic statement for non-web documents --- comments-by-guideline-and-success-criterion.md | 1 - 1 file changed, 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 3b3b3ffd..8f0326ab 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -566,7 +566,6 @@ See also the [Comments on Closed Functionality](#comments-on-closed-functionalit ###### Applying SC 2.4.2 Page Titled to Non-Web Documents -(for non-web documents) This applies directly as written, and as described in [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent) replacing "Page" with "Non-web document" and “Web pages” with “non-web documents”. From 42f073dff22564083d1521b6716fd044a250726c Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 22 May 2025 10:59:42 -0500 Subject: [PATCH 11/13] Remove parenthetic statement for non-web software --- comments-by-guideline-and-success-criterion.md | 1 - 1 file changed, 1 deletion(-) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 8f0326ab..004fa2aa 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -576,7 +576,6 @@ With this substitution, it would read: As described in the WCAG intent, the name of a [non-web document](#document) (e.g. document, media file, etc.) is a sufficient title if it describes the topic or purpose.
-(for non-web software) This success criterion is problematic to apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: From cb74415bf791033edff427010263b4deb4037167 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 22 May 2025 11:00:04 -0500 Subject: [PATCH 12/13] Add heading for applying to non-web software --- comments-by-guideline-and-success-criterion.md | 1 + 1 file changed, 1 insertion(+) diff --git a/comments-by-guideline-and-success-criterion.md b/comments-by-guideline-and-success-criterion.md index 004fa2aa..7dd8110f 100644 --- a/comments-by-guideline-and-success-criterion.md +++ b/comments-by-guideline-and-success-criterion.md @@ -576,6 +576,7 @@ With this substitution, it would read: As described in the WCAG intent, the name of a [non-web document](#document) (e.g. document, media file, etc.) is a sufficient title if it describes the topic or purpose. +###### Applying SC 2.4.2 Page Titled to Non-Web Software This success criterion is problematic to apply directly to non-web software through simple word substitution because application titles rarely describe the topic or purpose of the software. However, where the platform supports a programmatic title or name for a software window or screen, when a software application utilizes that feature to provide a unique title or name for each window or screen, the user can more easily find it or understand its purpose. This would address the user needs identified in the [Intent from Understanding Success Criterion 2.4.2](https://www.w3.org/WAI/WCAG22/Understanding/page-titled#intent). The following criterion is recommended as a substitute for the WCAG language: From bd3ba5ae1647fa1b28c394159d818b3578736653 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 29 May 2025 11:12:07 -0500 Subject: [PATCH 13/13] Remove bullet for 2.4.2 Page Titled from SC Problematic for Closed Per TF resolution on 29 May. --- success-criteria-problematic-for-closed-functionality.md | 1 - 1 file changed, 1 deletion(-) diff --git a/success-criteria-problematic-for-closed-functionality.md b/success-criteria-problematic-for-closed-functionality.md index c30f0257..113ae2b1 100644 --- a/success-criteria-problematic-for-closed-functionality.md +++ b/success-criteria-problematic-for-closed-functionality.md @@ -41,7 +41,6 @@ For non-web software on products with closed functionality, those who implement
  • 2.1.2 No Keyboard Trap — This criterion applies when focus can be moved using a keyboard interface. In some closed systems, tactile input like numeric keypads or other functional groups of keys may be available, but there is no mechanism for onscreen focus; for example, the keys are mapped directly to functions without moving focus between on-screen controls. In this case, there is no concept of focus, and therefore keyboard traps cannot exist and this success criterion would be satisfied.
  • 2.1.4 Character Key Shortcuts — Certain closed systems lack a mechanism for keyboard shortcuts because their mode of operation revolves around a single key performing a single function. For such systems, this success criterion is satisfied.
  • 2.4.1 Bypass Blocks — The WCAG2ICT interpretation of this success criterion replaces "sets of Web pages" with "sets of software programs" which are extremely rare - especially for closed functionality software. However, being able to bypass blocks of content that are repeated within software is generally considered best practice.
    • -
  • 2.4.2 Page Titled — Where the software is part of a product that provides a single function, or has a menu-driven interface, the intent of this success criterion would be met without needing an explicit title.
  • 2.4.4 Link Purpose (In Context) — This success criterion relies upon text and context being made available in a programmatically determinable form.
  • 2.4.5 Multiple Ways — The WCAG2ICT interpretation of this success criterion replaces "set of Web pages" with "set of software programs". Such sets, particularly in the context of closed functionality software, are exceedingly rare. There are a number of notes in the section Applying SC 2.4.5 Multiple Ways to Non-Web Documents and Software that are applicable to closed functionality software.
  • 2.4.7 Focus Visible — Presumes that there is a mode of operation where focus can be moved and controlled by keyboard. Some closed systems may offer tactilely discernible input such as a numeric keypad or other functional groups of keys, but do not offer any mechanism for conveying focus because the user interface is designed not to need that. For example, the keys are used to select options from a spoken menu rather than to move an onscreen focus element between multiple options. In this case, there is no concept of focus, thus there is no need for a visible indicator and this success criterion would be satisfied.