Skip to content

Port "author choice" for logo contrast exception to (text) contrast; add cross-reference from text to non-text for graphic/symbol use - #5297

Merged
patrickhlauke merged 17 commits into
mainfrom
patrickhlauke-text-contrast-logos
Sep 6, 2026
Merged

Port "author choice" for logo contrast exception to (text) contrast; add cross-reference from text to non-text for graphic/symbol use#5297
patrickhlauke merged 17 commits into
mainfrom
patrickhlauke-text-contrast-logos

Conversation

@patrickhlauke

@patrickhlauke patrickhlauke commented Aug 9, 2026

Copy link
Copy Markdown
Member

This is a follow-up to #4402

  • Remove the sentence about "text alternatives" in Contrast (Minimum) and Contrast (Enhanced) - this has nothing to do with understanding contrast
  • Add the "author choice" considerations for logos to the text contrast requirements as well
  • Split out the clarification about CI/brand not being a valid excuse for non-logo text to have insufficient contrast into its own separate point
  • Add cross-reference to text contrast understandings about stylised/symbolic text use counting as non-text content
  • Tweak stylised/symbolic text section in non-text contrast understanding
  • Tweak the "author choice" explanation (to be about logos that normally have sufficient contrast)
  • Add visual example of stylized text

Previews:

Diffs:

@netlify

netlify Bot commented Aug 9, 2026

Copy link
Copy Markdown

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 64c9ed4
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/6a9dd30a8dd0a20008656db1
😎 Deploy Preview https://deploy-preview-5297--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.

@patrickhlauke
patrickhlauke marked this pull request as ready for review August 9, 2026 16:29
@github-project-automation github-project-automation Bot moved this to To do in WCAG 2.x Aug 9, 2026
@patrickhlauke
patrickhlauke force-pushed the patrickhlauke-text-contrast-logos branch from f13f3ea to f07e6e0 Compare August 9, 2026 21:19
@fstrr

fstrr commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@bruce-usab

Copy link
Copy Markdown
Contributor

I don't think the [ X ] [ > ] buttons example belongs in Understanding Contrast Enhanced (unless you up the contrast to 4.5:1).

@patrickhlauke

patrickhlauke commented Aug 20, 2026

Copy link
Copy Markdown
Member Author

I don't think the [ X ] [ > ] buttons example belongs in Understanding Contrast Enhanced (unless you up the contrast to 4.5:1).

actually, the whole point there is that those buttons don't count as text (enhanced or otherwise), so 3:1 IS correct for them. the wording needs to make it clear that they fall under 1.4.11 and THERE they pass the requirements

Comment thread understanding/20/contrast-enhanced.html Outdated
@patrickhlauke
patrickhlauke force-pushed the patrickhlauke-text-contrast-logos branch from f0b1fce to b078a68 Compare August 21, 2026 13:40
…example of text characters acting as graphical symbols
@patrickhlauke
patrickhlauke force-pushed the patrickhlauke-text-contrast-logos branch from 61a2e19 to 8369935 Compare August 21, 2026 13:45
Comment thread understanding/20/contrast-enhanced.html
Comment thread understanding/20/contrast-enhanced.html Outdated
Comment thread understanding/20/contrast-minimum.html Outdated
Comment thread understanding/20/contrast-minimum.html Outdated
Comment thread understanding/21/non-text-contrast.html Outdated
Comment thread understanding/20/contrast-minimum.html
Comment thread understanding/21/non-text-contrast.html
@patrickhlauke patrickhlauke moved this from Drafted to Ready for approval in WCAG 2.x Aug 21, 2026
patrickhlauke and others added 3 commits August 21, 2026 22:56
Co-authored-by: Adam Page <adamfpage@gmail.com>
Co-authored-by: Adam Page <adamfpage@gmail.com>
Co-authored-by: Adam Page <adamfpage@gmail.com>
@patrickhlauke patrickhlauke moved this from Ready for approval to Sent for WG approval in WCAG 2.x Aug 24, 2026
Comment thread understanding/20/contrast-enhanced.html Outdated
Comment thread understanding/20/contrast-minimum.html Outdated
@patrickhlauke
patrickhlauke merged commit 13fb133 into main Sep 6, 2026
8 checks passed
@patrickhlauke
patrickhlauke deleted the patrickhlauke-text-contrast-logos branch September 6, 2026 20:57
@github-project-automation github-project-automation Bot moved this from Sent for WG approval to Done in WCAG 2.x Sep 6, 2026
contrast requirements.</p>
</div>
<p>If logos normally have sufficient contrast but are presented with an insufficient contrast as an author choice,
rather than because of corporate identity or brand guidelines, then that particular low contrast

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.

just to play devil's advocate, how would we treat cases where the CI brand guidelines demonstrably say, "In the footer or our product pages, the corporate logo is to be rendered in a muted grey with a contrast of 2:1"?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

then that's set by the CI which is exempted (because poor web devs can't go against the wishes of their silly branding team)

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

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants