2.4.2 Page Titled - Not all non-web docs and SW have titles that describe the topic or purpose #793
Conversation
This is a reimplementation of PR #633 using the current main branch as the original source which was approved by the TF back in May but not incorporated because we hadn't solved non-web documents yet. This new PR is to address issue #627 - for both non-web documents and software since there are problems applying this SC in both cases.
✅ Deploy Preview for wcag2ict ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
daniel-montalvo
left a comment
There was a problem hiding this comment.
see my suggestions
above
Gregg, Mike, and I had an email thread to develop potential language. The alternate requirement isn't exactly as Gregg had it but the note is what was proposed. I'm trying to keep this more closely aligned to WCAG2ICT's writing style which doesn't use the precondition style used in the EN 301 549.
|
@maryjom Thanks for putting this together. Just a minor comment that I put in one of our Pevious discussions
|
This is an editorial change that should not affect the CfC.
|
@daniel-montalvo I cannot merge this until you re-review. |
|
Hi @maryjom When re-reviewing this for approval I still found an occurrence of "page-oriented", which I assumed we agreed to remove completely from all WCAG2ICT prose. At a minimum, I would suggest:
And ideally, to make this cohesive with the below word substitution, I would suggest:
|
|
@daniel-montalvo I'll ask the group today what their understanding was. I think it was most important to remove from the suggested replacement requirement - which we did. The above sentence is only to provide some examples so page-oriented may still be OK in that context. |
+1 for double checking with the group about this. |
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
|
@daniel-montalvo I've incorporated your changes to this PR, please re-review so I can merge. Thanks! |
|
@daniel-montalvo Don't forget to review this PR for 2.4.2 Page Titled. |
| <div class="note wcag2ict software"> | ||
| See also the [Comments on Closed Functionality](#comments-on-closed-functionality).</div> | ||
| 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: |
There was a problem hiding this comment.
| 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: | |
| 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, and/or 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: |
Purely editorial.
I think this one is missing "and/or" as we have in the documents part. In the case of software, we only have two subordinates so I think we need the connector.
There was a problem hiding this comment.
@daniel-montalvo Non-web documents have the "and/or" on a different phrase that is not in the non-web software explanation. For non-web documents it is used on the phrase "and/or when a meaningful file name can be supplied" which is an alternate to utilizing the document technology's capability to supply a title or name inside of the document. So I don't think this change to use "and/or" should be made for non-web software.
daniel-montalvo
left a comment
There was a problem hiding this comment.
Approving, just a minor editorial tweak for software on a suggestion above.
|
@daniel-montalvo I am merging without the suggested editorial change because using "and/or" in the non-web software guidance changes the meaning of that sentence - unlike where it is used in the non-web document guidance. (Detailed reasoning is in my previous comment.) |
SHA: 80da10e Reason: push, by maryjom Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This is a reimplementation of PR #633 using the current main branch as the original source which was approved by the TF back in May but not incorporated because we hadn't solved non-web documents yet. This new PR is to address issue #627 - for both non-web documents and software since there are problems applying this SC in both cases.