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

Understanding SC 2.1.2 - broken link #3573

Closed
jiri-thiemel-te opened this issue Nov 29, 2023 · 9 comments
Closed

Understanding SC 2.1.2 - broken link #3573

jiri-thiemel-te opened this issue Nov 29, 2023 · 9 comments

Comments

@jiri-thiemel-te
Copy link

On the page https://www.w3.org/WAI/WCAG21/Understanding/no-keyboard-trap.html in the SC Note there's a link called
"Conformance Requirement 5: Non-Interference"
which is broken.

@mbgower
Copy link
Contributor

mbgower commented Dec 1, 2023

I believe this is intended to point to https://www.w3.org/TR/WCAG21/#cc5

@patrickhlauke
Copy link
Member

I believe this is intended to point to https://www.w3.org/TR/WCAG21/#cc5

well yes, but this is another one of those technical problems we have with the way the spec/understanding docs are built. the note in the SC text has a relative link, which then works in the main WCAG spec. however, when the SC is pulled into the understanding document, the relative link doesn't work anymore. I believe the solution here is technical / to be fixed at source in the relevant scripting/xslt that builds understanding docs. /cc @iadawn

@jiri-thiemel-te
Copy link
Author

Shouldn't it rather point to Understanding Conformance page since the link is on Understanding SC 2.1.2 page?
https://www.w3.org/WAI/WCAG21/Understanding/conformance#conf-req5

@patrickhlauke patrickhlauke self-assigned this Jan 19, 2024
@patrickhlauke
Copy link
Member

@alastc this is probably another one of those "how do we make references in light of how WCAG documents get built"

@bruce-usab
Copy link
Contributor

Ping to @iadawn via @avkuo and the wcag2-issues tf. Please advise.

@fstrr
Copy link
Contributor

fstrr commented Apr 15, 2024

@bruce-usab Not sure @avkuo is working on this. Similar avatar to the OP, though.

@iadawn
Copy link
Contributor

iadawn commented Apr 16, 2024

This is related to #3611. I will need to rebuild all the 2.1 docs with the updated XSLT file

@patrickhlauke
Copy link
Member

@kfranqueiro this may be of interest to you as well (as it relates to build process etc)

@kfranqueiro
Copy link
Contributor

This is resolved now that WCAG 2.1 Techniques and Understanding Docs have been republished via the new build system, made possible by #4007.

Shouldn't it rather point to Understanding Conformance page since the link is on Understanding SC 2.1.2 page? https://www.w3.org/WAI/WCAG21/Understanding/conformance#conf-req5

The contents within the SC box are sourced from the guidelines folder contents as-is (i.e. the same content that appears directly in the TR); adjusting links to instead point to Understanding counterparts would require another layer of logic (and might not be entirely straightforward in cases such as this where the URI fragment changes.)

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

No branches or pull requests

8 participants