Skip to content

Updates to flashing#628

Draft
alastc wants to merge 8 commits into
mainfrom
flashing-updates-survey-01
Draft

Updates to flashing#628
alastc wants to merge 8 commits into
mainfrom
flashing-updates-survey-01

Conversation

@alastc

@alastc alastc commented Mar 30, 2026

Copy link
Copy Markdown
Contributor

From the comments on the document, and the survey.

@netlify

netlify Bot commented Mar 30, 2026

Copy link
Copy Markdown

Deploy Preview for wcag3 ready!

Name Link
🔨 Latest commit b660780
🔍 Latest deploy log https://app.netlify.com/projects/wcag3/deploys/6a19fdbb77b40f0008c6c321
😎 Deploy Preview https://deploy-preview-628--wcag3.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.

@alastc alastc marked this pull request as draft March 30, 2026 10:14
@alastc

alastc commented Mar 30, 2026

Copy link
Copy Markdown
Contributor Author

@kfranqueiro I noticed that with a rename (of the shortname), it breaks the links to the github issues, where do I fix that?

@kfranqueiro

kfranqueiro commented Mar 30, 2026

Copy link
Copy Markdown
Contributor

@kfranqueiro I noticed that with a rename (of the shortname), it breaks the links to the github issues, where do I fix that?

(Edit: this has been resolved) It looks like you already renamed the labels in GitHub, which will break the links in the existing Working Draft. Instead, revert the labels to their original names in GitHub, and instead set issueLabel in the two requirement files under guidelines in this PR to the title as it appeared in the current Working Draft. The idea is that we would perform a label-renaming pass when we're close to republishing.

References:

(Edit: this has been resolved) Meanwhile, I would point out that despite "over threshold" being added to both titles, the "no exceptions" requirement text still says "Content does not include flashing", with no reference to the threshold. (Even within the definition of flashing, the threshold seems to only be brought up within a note, i.e. non-normative text.)

issueLabel: No flashing (no exceptions)
---

All :term[flashes] are below the :term[general flash and red flash thresholds] without a minimum size.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure the latter part of this is clear. What is 'without a minimum size'?

:::

:::note
If there is an :term[accessibility supported] method of setting a user-preference to prevent flashing, the content can be considered to avoid flashing if that preference is respected.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a method or a note?

type: foundational
---

Content does not include a change of contrast (over 4.5:1) going from light to dark (or dark to light) of more than 30% of the visible content area (viewport).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Content does not include a change of contrast (over 4.5:1) going from light to dark (or dark to light) of more than 30% of the visible content area (viewport).
Content does not include a single :term[flash] of more than 30% of the visible content area.

The original includes some ambiguity:

  • How quick a change of contrast?
  • Contrast between what and what?

Also, note sure 'viewport' is needed. If it is then it would just be '30% of the viewport' if that isn't clear enough then the existing text (without viewport) would be ok.

Finally, having looked at the definition for 'flash' I think it might need some attention in light of this but also, I suspect, from the no-flashing provisions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And I note the 'ednote' now!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants