Issue Details
|
|
| Source Issue ID |
87921 |
| Checkpoint |
1.3 Adaptable › Lists (1.3.1.f) |
| Impact |
Moderate |
| Standards |
wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22a, wcag22aa |
| Test Area |
06 Alerts |
| Test Case Name |
AP Trust Registry (Demo) |
| URL |
https://demo.aptrust.org/alerts |
| Environment |
Production |
| Platform |
Windows |
| Assistive Technology |
JAWS |
| Method |
Manual |
| Digital Asset Type |
Desktop Web |
| Release |
4.2026 |
| Product |
Website |
| Date Reported |
05/17/26 at 1:42 pm |
| Unit Type |
Page |
| Issue Type |
Accessibility |
| Reported By |
kim.casey@ablr360.com |
Description
Content is not a list but it is marked as such.
When you select the Mark as Read button, a dialog launches and all the content (i.e. To, Subject, Content) is marked up as a list and shouldn't be.
Recommendation
Rule :
Semantic HTML elements MUST be used according to their semantic meaning, not to create a visual effect.
How To Fix:
Fix this issue by removing the list markup or adding role="none" to the
or element.
Reference:
W3C-WAI tutorial: https://www.w3.org/WAI/tutorials/page-structure/content/#lists
Background:
People who can see are able to look at a list and get a sense that it is a list, how large it is, and its structure - whether there are multiple lists, nested lists, etc. People who are blind do not have this ability if the list is not marked with semantic list markup. Lists must be marked semantically in a way that correctly identifies the list structure and type: unordered, ordered, or definition/description. When list markup is correctly applied, screen readers are able to notify users when they come to a list and tell them how many items are in a list.
Source Code
<dt class="text-label text-xs is-grey-dark">To</dt>
Screenshots
Issue Details
Description
Content is not a list but it is marked as such.
When you select the Mark as Read button, a dialog launches and all the content (i.e. To, Subject, Content) is marked up as a list and shouldn't be.
Recommendation
Rule :
Semantic HTML elements MUST be used according to their semantic meaning, not to create a visual effect.
How To Fix:
Fix this issue by removing the list markup or adding role="none" to the
or
element.
Reference:
W3C-WAI tutorial: https://www.w3.org/WAI/tutorials/page-structure/content/#lists
Background:
People who can see are able to look at a list and get a sense that it is a list, how large it is, and its structure - whether there are multiple lists, nested lists, etc. People who are blind do not have this ability if the list is not marked with semantic list markup. Lists must be marked semantically in a way that correctly identifies the list structure and type: unordered, ordered, or definition/description. When list markup is correctly applied, screen readers are able to notify users when they come to a list and tell them how many items are in a list.
Source Code
Screenshots