Skip to content

Conversation

@patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Dec 23, 2025

Whether or not a text alternative is visually/visibly presented to users when CSS is disabled/unavailable is beyond the scope of 1.1.1. Rewording the last failure check to make the original intention clearer.

x-ref #4660 (comment)

EDIT: after some further consideration, this PR also:

  • changes the wording throughout from "important information" to "relevant information"
  • in the tests, it adds the caveat that the "relevant information" conveyed by the image is only of interest if it is not already conveyed elsewhere on the page

Whether or not a text alternative is visually/visibly presented to users when CSS is disabled/unavailable is beyond the scope of 1.1.1. Rewording the last failure check to make the original intention clearer.

x-ref #4660 (comment)
@netlify
Copy link

netlify bot commented Dec 23, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 521f1e4
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/694c723b5ae4150008802076
😎 Deploy Preview https://deploy-preview-4814--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@juliemoynat
Copy link

Can we also fix the points 2 and 3 speaking of images conveying "important information"? It should be just "information" no matter the importance, right?

@patrickhlauke
Copy link
Member Author

patrickhlauke commented Dec 23, 2025

@juliemoynat that point is a bit trickier. because intrinsically, any image will "convey information" depending on how you define "information" (at the very least, they convey "visual information"). it's a potentially slippery slope.

@patrickhlauke patrickhlauke changed the title Update F3 check Update F3 Dec 24, 2025
@patrickhlauke
Copy link
Member Author

@juliemoynat revisited this tonight and did come up with a further tweak that hopefully works to address your concern, while not going down the slippery slope of ambiguity i feared... see 521f1e4

@juliemoynat
Copy link

@patrickhlauke oh! I like it! I think there is no ambiguity anymore with "relevant" instead of "important". Thankyou!

@patrickhlauke patrickhlauke self-assigned this Dec 25, 2025
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