2.4.2 Page Titled - Not all non-web docs and SW have titles that describe the topic or purpose

[maryjom]

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.

[netlify]

✅ Deploy Preview for wcag2ict ready!

Name	Link
🔨 Latest commit	cf401db
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2ict/deploys/68efd65a3cc9df00080496b4
😎 Deploy Preview	https://deploy-preview-793--wcag2ict.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[daniel-montalvo]

Further edits to my original proposal based on 9 Oct minutes.

Suggested change

	This success criterion is problematic to apply directly to non-web documents through simple word substitution because not all document formats provide support for a title attribute, and document titles don't always describe the topic or purpose of the document. File names, as the WCAG 2.2 Understanding document allows, also rarely describe the topic or purpose of the document – especially where the document names are not under the author’s control. However, where the document authoring tool or technology provides the capability to supply a semantic title style or name for a document, when the non-web document utilizes that feature to provide a unique title or name inside of each document, and/or when a meaningful file name can be supplied, the user can more easily find it or understand its purpose. This would address the user needs identified in the WCAG 2.2 Intent from Understanding Success Criterion 2.4.2.
	This success criterion is problematic to apply directly to non-web documents through simple word substitution because not all document formats provide support for a semantic title style, and document titles don't always describe the topic or purpose of the document. File names, as the WCAG 2.2 Understanding document allows, also rarely describe the topic or purpose of the document – especially where the document names are not under the author’s control. However, where the document authoring tool or technology provides the capability to supply a semantic title style or name for a document, when the non-web document utilizes that feature to provide a unique title or name inside of each document, and/or when a meaningful file name can be supplied, the user can more easily find it or understand its purpose. This would address the user needs identified in the WCAG 2.2 Intent from Understanding Success Criterion 2.4.2. The following criterion is recommended as a substitute for the WCAG language:
	**2.4.2 Non-web Document Titled:** In non-web documents created using an authoring tool that supports semantic title styles for documents, titles are provided that describe the topic or purpose of the non-web document.

• "title attribute" may be easily confused with the functionality provided by the HTML title attribute, which is not the same as the title element. I suggest "semantic title" or "semantic title style" as you have later
• The Understanding documents don't "allow", they may "specify" or "explain" or similar, but "allow" is beyond what Understanding documents do.
• We are missing a word substitution alternative for this, similarly to what we have for non-web software.
  • To address Gregg's concerns, I am restricting the alternative language to "created using an authoring tool that supports semantic title styles for documents".

[daniel-montalvo]

see my suggestions
above