You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
patrickhlauke
changed the title
WCAG 2.2 understanding documents: notes for SCs are not indicated as notes
WCAG 2.2 understanding documents: notes for SCs are not indicated as notes (fails 1.3.1 Info and Relationships)
Jul 31, 2023
I would also prefer if we don't solve this with pseudo content as well as sometimes that can't be searched and may be used by people who customize style sheets.
I have just updated a change to the formatting of notes in the Understanding documents. Main changes:
Included the word 'Note' - as proper content, no pseudo-content here
removed the box styling - when in SC this box styling visually dominated quite a bit. I can easily put it back.
removed the role="heading" from the word 'Note' - as present in the Understanding documents, I am not 100% that these are headings. Open to any debate on that one though.
Note that these changes will also be reflected in the Notes in other areas of the Understanding document. Most particularly the Key Terms section.
Take for instance https://w3c.github.io/wcag/understanding/focus-not-obscured-minimum.html
The second and third paragraph in the boxout for the SC wording are notes, but this is not indicated in the understanding document.
In https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html notes are at least "boxed-out", but this is only a visual style, and the word "Note" is not present. As such, the fact that these are notes is not conveyed (failing 1.3.1 Info and Relationships in the process)
Notes are currently identified (in the main spec) using CSS and generated content. This here demonstrates why that may not actually be a good idea.
Suggest that:
The text was updated successfully, but these errors were encountered: