css.at-rules.media.forced-colors - Maybe add a note about Apple devices?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css
- Domain
- documentation
Research direction
Start with the MDN forced-colors media feature page linked in the issue and inspect its browser compatibility and explanatory content. Add a concise note describing how Safari handles forced-colors mode and Apple accessibility contrast settings, then verify that the page accurately reflects the reported behavior.
Written by the indexing model from the issue text.
Description
What type of issue is this?
Other
What information was incorrect, unhelpful, or incomplete?
Apple devices do have accessibility settings that allow users to have more contrast, or inverted colors, but to my knowledge, these settings do not trigger forced-colors mode on web pages displayed in Safari.
So, saying that Safari fully supports the forced-colors media feature is both correct and a bit incomplete. Yes, it supports the feature in the sense that the browser will do the right thing when it sees the media feature (i.e. the rules within it won't get applied). But perhaps adding a note that says that Safari doesn't actually ever go into forced colors mode, would be nice.
What browsers does this problem apply to, if applicable?
Safari
What did you expect to see?
A note about the fact that Apple devices' color contrast accessibility settings do not trigger forced colors mode in Safari.
Did you test this? If so, how?
I turned on the increased contrast setting on a macBook, and observed that the web content in Safari did not apply CSS rules placed inside a forced-colors rule.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/forced-colors
MDN metadata
MDN page report details
- Query:
css.at-rules.media.forced-colors - Report started: 2025-06-25T14:51:19.820Z
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdn/browser-compat-data
-
data:css needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mdn/browser-compat-data#30560 ·
-
blocked data:webdriver
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdn/browser-compat-data#30540 · 2 comments ·
-
browser:multiple data:css needs collector test p3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mdn/browser-compat-data#30533 · 2 comments ·
-
browser:safari data:css
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mdn/browser-compat-data#30528 · 3 comments ·
-
browser:chrome data:html needs collector test
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mdn/browser-compat-data#30468 · 1 comment ·
All issues in mdn/browser-compat-data
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100