Skip to content

Updated "A document collection" example since obsolete - SC 2.4.2 #4631

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.

Sign up for GitHub

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Updated "A document collection" example since obsolete - SC 2.4.2 #4631

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3787629
Updated "A document collection" example since obsolete - SC 2.4.2
giacomo-petri Sep 22, 2025
06e999d
Update page-titled.html
giacomo-petri Sep 22, 2025
8f94166
Merge branch 'main' into giacomo-petri-2_4_2-example
patrickhlauke Sep 26, 2025
c348dbc
Merge branch 'main' into giacomo-petri-2_4_2-example
bruce-usab Oct 2, 2025
f87b910
Merge branch 'main' into giacomo-petri-2_4_2-example
patrickhlauke Oct 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 15 additions & 7 deletions understanding/20/page-titled.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,15 +96,23 @@ <h2>Examples of Page Titled</h2>
<dt>An HTML web page</dt>
<dd>The descriptive title of an HTML web page is marked up with the &lt;title&gt; element so
that it will be displayed in the title bar of the user agent.</dd>
<dt>A document collection</dt>
<dt>A guide on authoring practices</dt>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<dt>A guide on authoring practices</dt>
<dt>A multi-page guide on authoring practices</dt>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still need the simple titular category of "a document collection" or "set of web pages"

<dd>
<p>The title of <a href="./">Understanding WCAG 2.2</a> is "Understanding WCAG 2.2".</p>
<p>The title of the landing page is "ARIA Authoring Practices Guide | APG | WAI | W3C"</p>
<ul>
<li>The <a href="../Understanding/intro">Introduction to Understanding WCAG</a> page has the title "Introduction to Understanding WCAG".</li>
<li>Major sections of the document collection are pages titled "Understanding Guideline X" and "Understanding Success Criterion X."</li>
<li>Appendix A has the title "Glossary."</li>
<li>Appendix B has the title "Acknowledgements."</li>
<li>Appendix C has the title "References."</li>
<li>
The patterns list page has the title "Patterns | APG | WAI | W3C"
<ul>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's unnecessary and confusing to use nested (and then nested again, 3 levels) bullet points here. I get that the intention here is to also show hierarchy, but a simple straightforward set of bullet points will work best here I'd say

<li>
Specific patterns are pages titled "X Pattern | APG | WAI | W3C" (e.g., "Alert and Message Dialogs Pattern | APG | WAI | W3C")
<ul>
<li>Specific examples for each pattern are pages titled "X Example | APG | WAI | W3C" (e.g., "Alert Dialog Example | APG | WAI | W3C")</li>
</ul>
</li>
</ul>
</li>
<li>Practices page has the title "Practices | APG | WAI | W3C"</li>
<li>Index page has the title "Index | APG | WAI | W3C"</li>
</ul>
</dd>
<dt>A web application</dt>
Expand Down