forced-colors Adjustments Lookup
Supported forced-colors observations; forced-color-adjust:none opt-out is not a universal accessibility improvement. Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.
Description
Forced-color mode can substitute a user agent's selected colors.
Forced-color mode can substitute a user agent's selected colors.1
A status explanation does not evaluate the readability of an actual page. Use forced-colors Adjustments Lookup to look up a supported term.
When to use forced-colors Adjustments Lookup
Use forced-colors Adjustments Lookup to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.
How to use forced-colors Adjustments Lookup and understand its results
- Choose the exact supported token from the table; preserve its punctuation and capitalization.
- Enter Forced colors using the field table and validation rules below, then run the tool.
- Read Meaning and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| forcedColors | Forced colors | string | Required; constraints below |
Enter one of the exact supported forcedColors tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.
meaning = storedTable[exactSupportedToken] Field order, units and branch conditions follow the implementation explanation above.
| Exact supported token | Stored meaning |
|---|---|
| active | UA may substitute colors; use system colors and preserve visible boundaries |
| none | forced-color mode not active |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"forcedColors": "active"
},
"output": {
"meaning": "UA may substitute colors; use system colors and preserve visible boundaries"
}
}Limitations and assumptions
A status explanation does not evaluate the readability of an actual page. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use accent-color Native Control Tint for a related task: Accent-color can tint supported native controls.
Use prefers-color-scheme Query Pattern for a related task: Preferred color-scheme queries express a reported light or dark preference.
References
-
forced-colors Adjustments Lookup — tool.io
Similar or alternative tools
- accent-color Native Control Tint
Accent-color can tint supported native controls.
- prefers-color-scheme Query Pattern
Preferred color-scheme queries express a reported light or dark preference.