Skip to content
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.

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

Notes missing numbers when drawn into understanding docs #4229

Closed
alastc opened this issue Feb 12, 2025 · 1 comment · Fixed by #4231
Closed

Notes missing numbers when drawn into understanding docs #4229

alastc opened this issue Feb 12, 2025 · 1 comment · Fixed by #4231
Assignees

Comments

@alastc
Copy link
Contributor

alastc commented Feb 12, 2025

From Mike Tschudi on email:

On the page https://www.w3.org/WAI/WCAG22/Understanding/three-flashes-or-below-threshold.html in the “general flash and red flash thresholds” section, there is the sentence “Content automatically passes (see #1 and #2 above).”, but I don’t see what these numbers refer to. Might these number labels be added in the document, or the numbers become links to the sections that they refer to?

You need to open the "Key terms", and that text is at the end of the last note.

In the Spec version of that definition, the notes are numbered, which makes sense.

In the understanding doc version, they are not.

Given the phaff of updating the spec version, could the notes be updated with numbers in the understanding doc version?

@kfranqueiro
Copy link
Contributor

kfranqueiro commented Feb 12, 2025

Notes with regard to scope:

  • This issue occurs not only within term definitions, but also within SC content (e.g. 3.3.8)
  • This issue also occurs for examples (only within term definitions)
  • Notes/examples are only numbered when there is more than one in the applicable section

Currently, markup for notes and examples is handled in a single pass for each. Numbering them correctly will require at minimum checking how many are under a particular parent (section for SC, dd for term definition).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants