-
Notifications
You must be signed in to change notification settings - Fork 7
Say 2.4.2 is not applicable #626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Update comments-by-guideline-and-success-criterion.md
✅ Deploy Preview for wcag2ict ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
stronger emphasis
|
||
<div class="note wcag2ict"> | ||
|
||
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.</div> | ||
As described in the WCAG intent, the product name of a [non-web software application](#software) is a sufficient title if it provides descriptive identification.</div> | ||
<div class="note wcag2ict"> | ||
|
||
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.</div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry but this proposed change solves nothing. True there are a few products that have descriptive identification or name -- but most names are not descriptive. If this is meant to be double-speak for "any name is considered descriptive of a software product because it is the name of the product" then the requirement becomes "The name of the product must be the name of the product" and it is impossible to not meet the SC. So why have it. This is a twisting of the meaning of the SC to solve the problem but only ends up with a nonsense SC that cannot be failed.
During call 5/8, per our conversation, I changed the short names (handles) for the two use cases. As I described during the call, this PR aims to change as little as possible from the 15 November 2024 Group Note. For example, the notes have not been updated (regardless that they discuss title, and not name) because (while they might be improved) they are not incorrect. |
|
||
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”. | ||
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”. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we also are replacing "Page" with "Document" in the short name, we should also describe this.
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”. | |
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 "Document" in the short name and “Web pages” with “non-web documents”. |
|
||
This should **not** be applied directly as written to 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 <INS>[Software Named]</INS>:** <INS>**[[Non-web software](#software)]**</INS> have names that provide description identification. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to show the replacement markup on all of the text. This also gives us liberty to make the verbiage singular rather than plural.
**2.4.2 <INS>[Software Named]</INS>:** <INS>**[[Non-web software](#software)]**</INS> have names that provide description identification. | |
**2.4.2 <INS>[Software Named]:** [Non-web software](#software) has a name that provides description identification.]**</INS> |
|
||
###### Applying SC 2.4.2 Page Titled to Non-Web Software | ||
|
||
This should **not** be applied directly as written to non-web software. For software, direct application of 2.4.2 Page Titled is problematic. The following criterion is recommended as a substitute: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should **not** be applied directly as written to non-web software. For software, direct application of 2.4.2 Page Titled is problematic. The following criterion is recommended as a substitute: | |
This cannot apply directly as written to non-web software. The following criterion is recommended as a substitute: |
I am uncomfortable with this strong statement here and would advocate for softer language. For rationale, see #639.
As a global thought, I would agree that if we know why something is problematic or cannot apply directly as written we should explain it.
Update guidance for 2.4.2 saying it is not applicable to software and to recommend an alternate requirement better fitting to window titles, per minutes 4/10, 4/17, and 4/24.
Link to anchor of section in deploy preview.
For convenient reference, a few lines from the work statement:
This PR is offered as an alternative to PR #624 which asserts that 2.4.2 is fine as-is.
Updated following 5/1 meeting, keeping as much phrasing from 2.4.2 of November 2024 as possible.