Skip to content

content(accessibility): add Forced colours mode page#50

Merged
jdevalk merged 2 commits into
mainfrom
standards-scan/forced-colors-2026-06-21
Jun 22, 2026
Merged

content(accessibility): add Forced colours mode page#50
jdevalk merged 2 commits into
mainfrom
standards-scan/forced-colors-2026-06-21

Conversation

@jdevalk

@jdevalk jdevalk commented Jun 22, 2026

Copy link
Copy Markdown
Owner

What changed

New spec page: Forced colours mode under accessibility. Documents the forced-colors media feature and forced-color-adjust property — how to repair UI that a forced palette (Windows High Contrast and similar) flattens, using CSS system colour keywords, without overriding the user's choice.

  • Wires relatedSlugs on color-contrast, reduced-motion, and color-scheme.
  • Adds a changelog entry (added).
  • Regenerates the count-driven OG images + the new per-page OG image (deterministic; no unrelated drift).
  • npm run build passes (146 pages indexed). SKILL.md uses a soft "140+ pages" figure that's still accurate, so no digest change.

Why now

Found by the daily standards scan. It's a genuine coverage gap: we cover prefers-reduced-motion, colour contrast, and color-scheme, but nothing on forced colours — the mode some low-vision and light-sensitive users depend on.

Primary sources

Status: recommended

Forced colours works automatically for semantic markup; this page is about not breaking it and repairing the few places a palette erases a colour-only distinction. The platform contract doesn't break without it, so it's recommended, not required. Baseline: widely available since Sept 2022 (verified via MDN — the MDN MCP server was not connected this run, so this was checked via MDN directly).

🤖 Generated with Claude Code

New page documenting the `forced-colors` media feature (CSS Media
Queries Level 5) and `forced-color-adjust` (CSS Color Adjustment
Module Level 1) — how to repair UI that Windows High Contrast and
similar palettes flatten, without overriding the user's choice.

Status: recommended (forced colours works automatically for semantic
markup; this is about not breaking it, so the platform contract does
not break without it). Baseline: widely available since Sept 2022.

Wires relatedSlugs on colour-contrast, reduced-motion, and
color-scheme; adds changelog entry and count-driven OG images.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 22, 2026

Copy link
Copy Markdown

Deploying specification-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: e7a9876
Status: ✅  Deploy successful!
Preview URL: https://3cd93b86.specification-website.pages.dev
Branch Preview URL: https://standards-scan-forced-colors.specification-website.pages.dev

View logs

The og:image/twitter:image base was hardcoded to site.url
(specification.website). On a Cloudflare Pages preview deployment a brand-new
page's OG image only exists on the preview origin, not yet on production, so the
card 404'd and no social image rendered for the page under review.

Point the social image at CF_PAGES_URL when CF_PAGES_BRANCH is set and isn't
main; production and local builds keep site.url. Canonical and og:url are
untouched, so preview pages still self-canonicalise to the production domain.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jdevalk jdevalk marked this pull request as ready for review June 22, 2026 14:34
@jdevalk jdevalk merged commit 94095a5 into main Jun 22, 2026
8 checks passed
@jdevalk jdevalk deleted the standards-scan/forced-colors-2026-06-21 branch June 22, 2026 14:34
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.

1 participant