w3c / wcag

Web Content Accessibility Guidelines
https://w3c.github.io/wcag/guidelines/22/
Other
1.09k stars 242 forks source link

Understanding SC 2.1.2 - broken link #3573

Open jiri-thiemel-te opened 9 months ago

jiri-thiemel-te commented 9 months ago

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 commented 9 months ago

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

patrickhlauke commented 9 months ago

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 commented 9 months ago

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 commented 7 months ago

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

bruce-usab commented 4 months ago

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

fstrr commented 4 months ago

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

iadawn commented 4 months ago

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

patrickhlauke commented 1 month ago

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