Repository navigation
Replies: 3 comments 1 reply
|
Let's consider some examples:
|
0 replies
|
@innoticFR you might be interested in reviewing #5373 |
1 reply
|
Since this discussion is mainly opinion-based and hasn't attracted much interest, I'll go ahead and close it unless anyone has anything else to add? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Looking at "Understanding Conforming Alternate Versions":
This non-normative reference states that:
This is consistent with EN 301 549 requirements (12.3), though the latter also references the WCAG glossary for the definition of a "conforming alternate version".
Techniques such as G136 and F19 also address this concern.
Looking at the related ticket (#5373), my understanding is that from a strictly normative perspective, WCAG does not mandate specific wording or explicit labeling, as long as a conforming version exists and can be reached, even if its accessibility features are undocumented or not explicitly described as "more accessible." For instance, a link simply labeled "Plain HTML version" might be sufficient from a strict normative standpoint, or even a generic overlay tool where some/many options might make no actual difference.
My question is therefore more practical/opinion-based than purely normative: what would you expect from a non-conforming web page to satisfy the intent of the non-normative Understanding guidance?
The objective of my question is to define precise rules in the context of implementing the European standard.
All reactions