User tests: Successful: Unsuccessful:
Pull Request resolves #48394.
The tags in any Cassiopeia article are unrelated links without a clear relationship. This PR adds a navigation landmark to the tags. It is a translatable label "Tags", which is conveyed to assistive technology. This is applied to the shared content tag list layout, providing tag group context wherever that layout is used, including article, category, contact, newsfeed, and article-module displays.
Below is an image depicting the speech output of the NVDA speech viewer indicating the navigation region is added and has a name of "Tags":
The list of tags is merely conveyed as a list without any contextual relationship indicated. Sighted users may recognize that they are tags, but blind, low vision, or users with cognitive disabilities may not.
The list of tags has its purpose conveyed via a translatable label within a navigation region. Now, screen reader users will be able to understand the context of this list of links.
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | Layout |
Yeah that's a good idea.
Is changing JTAG to "Article tags" sufficient in all contexts? If so, I can add the < nav > and change the JTAG value in the next commit.
No you absolutely can not change the string in that way
Tags are horizontal and can be used in any supported component eg you can tag your contacts as you already identified
No you absolutely can not change the string in that way
Tags are horizontal and can be used in any supported component eg you can tag your contacts as you already identified
My fault in the suggested pseud code in my comment where i should have just written
<nav aria-label="Tags">
<ul>
<li><a href="/tag/joomla">Joomla</a></li>
<li><a href="/tag/accessibility">Accessibility</a></li>
<li><a href="/tag/web-development">Web Development</a></li>
</ul>
</nav>
You could maybe add a new string but it would need to be generic eg "Tagged Items" but I think for me "Tags" is enough
Yeah that's why I asked. Thanks for clarifying.
I'll add a labelled < nav >; that was a good suggestion, Brian.
| Labels |
Added:
a11y
PR-6.2-dev
|
||
| Title |
|
||||||
I have tested this item ✅ successfully on 606d42b
I have tested this item ✅ successfully on 606d42b
I have tested this item ✅ successfully on 606d42b
I have tested this item ✅ successfully on 606d42b
| Status | Pending | ⇒ | Ready to Commit |
RTC
RTC
| Labels |
Added:
RTC
|
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-10-30 11:11:09 |
| Closed_By | ⇒ | drmenzelit |
Thank you
The tags act as links to other articles with the same tag so wouldnt it be better (more semantic) if they were presented inside a a nav landmark. Just adding the label tags doesnt really have any semantic meaning does it?