Add extra (non-normative) note to the definition of "conforming alternate version" - #5236
Add extra (non-normative) note to the definition of "conforming alternate version"#5236patrickhlauke wants to merge 3 commits into
Conversation
…nate version" The point of this new note is already implicit in note 4 and note 7, but this makes it even more explicit. Relates to #2750
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Editorial suggestion (as I found “if the content” opener awkward); current:
Proposed:
|
|
Approved by TF on backlog call 7/31. Bruce flagged that Understanding Conformance should probably be lightly refreshed to say something about author provided settings/preferences. |
|
-1 as this can easily be handled in Understanding. |
|
so we'd have 7 existing notes that clarify the concept, but the 8th one would be better migrated somewhere completely different where readers might not even look? hmmm... that seems a very weak rationale... |
|
So we should move anything that anyone thinks is easier to find into the normative document? The understanding document can be changed today. Even if this is accepted it won't be seen by the people who need it until, and if, there is an update to WCAG 2.x. |
|
we could do both of course :) (though it would still feel extremely weird to have 7 notes, and then one that is similar but new offshored somewhere completely separately...) unless the MO is of course "let's never change the face of the spec ever again" |
|
Noting that this may need to be delayed following the reopening of #2750 |
This is a proposed normative (but backwards-compatible) change for a potential WCAG 2.3
The point of this new note is already implicit in note 4 and note 7, but this makes it even more explicit.
Relates to #2750
Preview: Note 8 in https://deploy-preview-5236--wcag2.netlify.app/guidelines/#dfn-conforming-alternate-versions