Description
About Forced Colors Test
Introduction
The DeviceHub Forced Colors Test is a free online forced-colors / Windows High Contrast style media checker, without claiming identical behavior on every OS, without rewriting your production CSS, and without presenting high-contrast usage as a medical diagnosis. Windows users who rely on Contrast themes, engineers implementing forced-colors media queries and system color keywords, QA reproducing “icons vanished in High Contrast,” educators teaching forced-color-adjust, and support teams proving the browser sees active forced colors all open one HTTPS page after enabling the OS theme and read the media feature. DeviceHub states limits plainly: forced-colors varies by platform; prefers-* and related features reflect OS/browser settings, not all AT configurations; this is not a full page audit; and it never replaces WAVE, axe, or professional audits. Pair with Accessibility Preferences for prefers-contrast. Pair with Color Contrast Checker for author hex math outside forced modes. Pair with Keyboard Focus Test because high-contrast themes must still show focus. Pair with Accessibility Preferences for a hub. Permissions stay none. Never claim clinical outcomes from a media query. Forced colors mode is one of the sharpest platform-specific edges in web accessibility: Windows Contrast themes commonly activate forced-colors, while many macOS and mobile configurations never present the same media state even when users enable other contrast enhancements. DeviceHub Forced Colors Test exists so engineers stop guessing from screenshots taken on the wrong OS. Product designers who authored delicate gradients, QA who only own MacBooks, and agencies shipping SVG icon systems that vanish under system remapping all need an honest active versus none signal plus educational preview, not a promise that DeviceHub rewrote their CDN assets. Limits stay explicit: forced-colors varies by platform; prefers-* reflect OS/browser settings, not all AT; Color Contrast Checker hex math describes authored sRGB pairs outside forced remapping; text-spacing and speech tools elsewhere have their own limits; nothing replaces WAVE, axe, or professional audits; and no result here is a medical or clinical diagnosis. Pair with Keyboard Focus Test because remapped chrome must still reveal focus. Pair with Accessibility Preferences for hub context. Permissions stay none.
What this tool does
Forced Colors Test reports whether forced-colors is active, previews how sample UI may remap to system colors, and explains authoring tips at a high level (system colors, preserving focus, avoiding critical information in color alone). It does not enable High Contrast on Mac for you, does not upload theme choice for ads, and does not crawl your site. Guidance stresses platform variance, Windows is the common forced-colors laboratory; other OSes differ. Typed permissions remain none. Side notes link Accessibility Preferences and Color Contrast Checker. Closing the tab ends the session. Informational only, not clinical. The tool reports forced-colors media state, shows how sample buttons, links, and surfaces may adopt system colors, and summarizes authoring themes such as using system color keywords, avoiding information encoded only in decorative color, and testing forced-color-adjust. It will not flip Windows themes for you, will not install High Contrast, and will not crawl your staging site for every SVG fill. Guidance highlights back-compat aliases some engines historically exposed and why documentation should always include OS name. Side notes send you to Accessibility Preferences when the user enabled a milder contrast option without a full Contrast theme. Closing the tab ends previews. Results remain informational accessibility diagnostics, not clinical vision scores and not conformance certificates.
When to use it
Use when shipping Windows High Contrast support, when SVGs disappear under Contrast themes, when testing forced-color-adjust, when QA needs media evidence, and when teaching system color keywords. Prefer Color Contrast Checker for normal theme AA math. Prefer Keyboard Focus Test for tab stops under remapped chrome. Prefer Accessibility Preferences for multi-signal captures. Avoid medical claims. Avoid assuming macOS mirrors Windows forced-colors. Use before Windows release certifications for public-sector or enterprise customers who mandate Contrast themes, when icons disappear only for those customers, when researching forced-color-adjust: none hazards, when teaching system colors Canvas, LinkText, ButtonFace, and friends, and when Mac-only teams need a reminder to borrow a Windows VM. Prefer Color Contrast Checker for everyday AA token work in non-forced themes. Prefer Color Scheme Preference when the issue is dark mode rather than forced remapping. Prefer Reduced Motion Check when Contrast themes also change animation budgets indirectly through performance. Avoid medical claims. Avoid assuming Linux desktop contrast utilities equal Windows forced-colors.
How it works
The forced-colors media feature indicates when the user agent enforces a limited color palette, commonly associated with Windows High Contrast / Contrast themes. DeviceHub reads the feature and shows educational previews. Behavior and back-compat aliases can differ by engine and OS, document platform. Typed permissions stay none. Authors should not rely on decorative gradients in forced-colors mode and should verify focus indicators remain visible. Not a crawler audit. Not WAVE/axe. Not clinical. Local display only; no advertising upload of the mode from this page. When forced-colors is active, user agents limit the page’s color palette and map many declarations to a small system set. Authors detect the mode with CSS media and adapt. DeviceHub reads that media feature and renders an educational sample; it does not guarantee pixel parity with every Windows Contrast theme skin. Platform variance is expected: treat none on macOS as common, not as a failed test harness. Typed permissions stay none. Secure HTTPS applies. Keyboard focus, link distinction, and non-text indicators remain author responsibilities this sample only illustrates. Professional AT testing with real high-contrast users still matters. DeviceHub will not claim to replace those sessions or automated axe/WAVE runs. Local only, no advertising upload of theme choice from viewing the page. Fingerprinting via forced-colors is low entropy; still minimize unnecessary public dumps of enterprise desktop policies.
Step-by-step instructions
- Enable a Windows Contrast / High Contrast theme when testing forced-colors; note if your OS cannot activate the same mode.
- Open Forced Colors Test over HTTPS and record active versus none with browser and OS names.
- Review the sample remapped UI and note focus visibility.
- Cross-check Accessibility Preferences.
- Validate non-forced theme tokens separately with Color Contrast Checker.
- Label results as platform-varying media signals, not medical diagnoses and not full site audits.
Common problems
Expecting macOS to match Windows forced-colors. Icons and backgrounds vanishing because authors used bitmaps without system colors. Confusing forced-colors with prefers-contrast. Treating DeviceHub as a sitewide fixer. Skipping focus checks. Claiming clinical vision results. Assuming AAA hex math still applies unchanged under system palettes. WebView differences. Replacing professional audits with a media screenshot. Ignoring keyboard users in High Contrast. Mac screenshots used to “prove” Windows High Contrast bugs. Bitmap icons without alternative system-colored versions. Removing outlines and losing focus under remapping. Confusing prefers-contrast more with forced-colors active. Claiming DeviceHub diagnosed low vision clinically. Expecting AAA hex ratios to describe system palettes. WebView differences inside Microsoft Edge modes. Replacing professional audits with a media badge. Ignoring button borders that collapse. Assuming forced-colors always equals a specific named Windows theme. Shipping background images that hide text when colors force. Forgetting print and PDF export paths. Mixing Color Blindness Test into clinical forms. Believing DeviceHub patches production SVGs remotely.
Privacy explanation
Forced Colors Test reads media features available to CSS and shows previews locally. DeviceHub does not upload your contrast theme for advertising when you use this page. Permissions stay none. Informational, not medical or clinical. Restore shared lab PCs to default themes after class. Forced Colors Test reads CSS media and paints local previews. DeviceHub does not upload your Contrast theme selection for advertising when you use this page. Permissions stay none. Informational, not medical or clinical. Restore shared Windows lab themes after class so the next student does not inherit High Contrast unexpectedly.