Skip to content

Add extra (non-normative) note to the definition of "conforming alternate version" - #5236

Open
patrickhlauke wants to merge 3 commits into
mainfrom
patrickhlauke-issue2750-follow-up
Open

Add extra (non-normative) note to the definition of "conforming alternate version"#5236
patrickhlauke wants to merge 3 commits into
mainfrom
patrickhlauke-issue2750-follow-up

Conversation

@patrickhlauke

@patrickhlauke patrickhlauke commented Jul 27, 2026

Copy link
Copy Markdown
Member

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

…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
@github-project-automation github-project-automation Bot moved this to To do in WCAG 2.x Jul 27, 2026
@patrickhlauke patrickhlauke added Errata Erratum to a Recommendation ErratumRaised Potential erratum for a Recommendation and removed Errata Erratum to a Recommendation labels Jul 27, 2026
@netlify

netlify Bot commented Jul 27, 2026

Copy link
Copy Markdown

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit c4be000
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/6a8af8acbdbf1a000809af4b
😎 Deploy Preview https://deploy-preview-5236--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@bruce-usab

Copy link
Copy Markdown
Contributor

Editorial suggestion (as I found “if the content” opener awkward); current:

If the content provides a number of settings or user preferences that, individually, only address one particular aspect of the content (for instance,

Proposed:

Where a number of settings or user preferences are provided that, individually, only address one particular aspect of the content (for example,

@patrickhlauke patrickhlauke moved this from Drafted to Ready for approval in WCAG 2.x Jul 31, 2026
@bruce-usab

Copy link
Copy Markdown
Contributor

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.

@patrickhlauke patrickhlauke moved this from Ready for approval to Sent for WG approval in WCAG 2.x Aug 10, 2026
@awkawk

awkawk commented Aug 10, 2026

Copy link
Copy Markdown
Member

-1 as this can easily be handled in Understanding.

@patrickhlauke

patrickhlauke commented Aug 10, 2026

Copy link
Copy Markdown
Member Author

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...

@awkawk

awkawk commented Aug 10, 2026

Copy link
Copy Markdown
Member

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.

@patrickhlauke

patrickhlauke commented Aug 10, 2026

Copy link
Copy Markdown
Member Author

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"

@patrickhlauke

Copy link
Copy Markdown
Member Author

Noting that this may need to be delayed following the reopening of #2750

@patrickhlauke patrickhlauke moved this from Sent for WG approval to For discussion (WG feedback) in WCAG 2.x Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ErratumRaised Potential erratum for a Recommendation Substantive WCAG 2.3

Projects

Status: For discussion

Development

Successfully merging this pull request may close these issues.

3 participants