Contrast, schemes, and Islands

Start with an exact variant#

Choose the complete registered name in Appearance → Theme. A family such as Arc or Black & Gold can contain multiple choices, and the suffix can materially change the surface. Confirm the matching Editor → Color Scheme before comparing.

Evaluate the special-purpose choices#

Use HC, Colorblind, or OLED variants according to the actual states you need to read. Inspect ordinary text, muted comments, warning/error marks, diff backgrounds, tree selection, and completion selection. A label communicates a palette’s intent; your language plugins and custom overrides still affect the result.

Use diagnostic symbols/text as well as color when interpreting a finding. A custom scheme that removes distinctions can undermine the supplied palette’s readable semantic states.

Customize one scheme#

Duplicate the matching scheme before changing language-specific colors. Adjust one category at a time and check a second file type. Fonts and line spacing belong under Editor → Font or an intentional scheme override, so keep them fixed while comparing palette contrast.

Inspect Islands separately#

Choose Bearded Theme Islands Moonstone for its explicitly registered treatment on a supported platform. UI scale, compact mode, tab placement, and IDE geometry are separate from syntax highlighting.

Restore independently#

Reapply the supplied theme/scheme for color. Toggle Bearded file icons on its settings page for icons. Keeping these operations distinct helps identify which provider or override controls the mismatch.

For a visual report, include the full variant name, scheme, icon setting, IDE version, language, and affected selected/focused state. This is especially useful in a family with many closely related names.