
A selected-photo cue can disappear in Windows High Contrast when the gallery relies on a shadow or color treatment that the browser replaces. Check the actual selected state under forced colors before changing the picture. The fix belongs to the website control, not to the photograph's pixels. A targeted border or other persistent state cue may be appropriate, but the visitor's chosen palette should remain useful.
Key Takeaways
- Forced colors and an ordinary dark theme are different rendering conditions.
- A shadow-only selection cue can disappear even when the image loads correctly.
- Inspect selection and keyboard focus separately on the implemented gallery.
Identify which cue disappeared
Start with a gallery containing a few clearly different photographs. Record how the ordinary layout distinguishes selected from unselected items: a border, shadow, background, check control or visible wording. Keep this record separate from the photo's own colors. A bright frame baked into the artwork is not necessarily a working selection indicator.
If the problem occurs only in an ordinary light or dark theme, the SVG color-inheritance guide addresses a different mechanism. Do not assume that correcting currentColor also repairs forced-color behavior. Identify the operating-system preference and browser used in the report.
Understand what forced colors changes
MDN's forced-colors reference explains that browsers enforce a limited user-selected palette. Among other changes, box-shadow and text-shadow become none, and background images that are not URL-based are removed. Border, text and other colors can be replaced with system colors.
This means a component can lose a distinction without losing its underlying selected value. Ask the implementer to inspect the control's state and computed presentation together. Re-exporting the artwork at a higher resolution cannot restore a CSS shadow the browser deliberately omits.
MDN also notes that native element semantics influence the system colors chosen. Adding an ARIA button role to a generic element does not make its forced-color painting identical to a native button. The implementation should be assessed as a working component, rather than repaired by adding a role name alone.
Compare the relevant states
| State | Proposed receiving check | Record separately |
|---|---|---|
| Unselected photo | Can the visitor identify the available item? | Its visible label or image description |
| Selected photo | Does an understandable selection cue remain? | The actual selection state |
| Keyboard-focused photo | Can the visitor locate the current keyboard position? | Focus versus selection |
| Selected and focused | Are both facts still understandable? | Whether one cue hides the other |
Run this proposed matrix after enabling the intended system setting. Use the real thumbnails and labels, including any descriptions for images. Record a reproducible example using the same image identifiers as the review notes. A generic screenshot of an empty gallery is weak evidence for the actual selection task.
Request a narrow repair and repeat the task
MDN shows a targeted border using an appropriate system color as an alternative when a button's shadow disappears. That is an example to adapt to the actual control, not a universal color value for every gallery state. Ask the implementer to retain the needed distinction within the user's palette.
Avoid globally disabling forced-color adjustment just to preserve brand appearance. MDN explains that these adjustments can be essential for reading. After repair, repeat selecting, deselecting and keyboard navigation in both ordinary and forced-color modes. Accept the gallery when the intended states remain understandable, rather than when it merely resembles the designer's default screenshot.
Related tasks
- Why Does My SVG Change Color or Disappear in Dark Mode?
- Should I Use My Generation Prompt as Alt Text for an AI Image?
- How Do I Tell a Photo Editor Exactly Which Area Needs Changing?
Sources and scope
- MDN: forced-colors CSS media feature: Forced colors uses a limited user palette, removes box shadows and some backgrounds, and chooses system colors using native semantics. Targeted system-color borders can restore lost affordances; broad opt-out can defeat needed user adjustments.
Based on the supplied complete MDN forced-colors reference, reviewed October 29, 2026. No Windows device or gallery was tested. The thumbnail-state matrix is a proposed implementation review, not a claim of accessibility conformance.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.