Short answer
For some people, yes; for others, no — which is why the accessible choice is to offer both and respect the user's system setting. People with light sensitivity often find dark themes more comfortable, while some people with astigmatism or certain other conditions find light text on dark harder to read. Either mode must meet WCAG contrast on its own, keep working when users force their own colours, and behave correctly with increased-contrast settings.
The W3C's work on low-vision needs describes light sensitivity as common, with bright screens causing discomfort or making text unreadable, and notes that some people need to switch to a darker background. For them a dark theme can be the difference between using a product and not. The same body of guidance stresses that needs vary, and WCAG's criterion on visual presentation exists because people choose colour combinations that others would find strange. Some readers report that light text on dark backgrounds appears to blur or bleed, a complaint often associated with astigmatism; the evidence for how large this effect is across the population is limited, but it is enough to say that forcing dark mode on everyone is not an accessibility win.
A dark theme is a set of colour pairs like any other, and each must meet the same criteria: 4.5:1 for normal text, 3:1 for large text and for non-text elements needed to identify controls and states. The table checks typical dark-theme text greys. Pure white on pure black reaches the maximum 21:1; the more common off-white on #121212 gives around 13–15:1, comfortably above AAA; mid greys used for secondary text pass AA on the base and first raised surface but lose margin on every lighter one; and dark greys often used for disabled or placeholder text fall below 4.5:1. If a product offers both modes, a conformance claim covers both, because users can reach either.
The prefers-color-scheme media query (Media Queries Level 5) exposes the user's system preference for light or dark, and following it by default is the most respectful behaviour. The same specification defines prefers-contrast, for users who have asked their system for more (or less) contrast, and forced-colors, which reports when the browser is overriding author colours with a user palette. Apple's guidance warns of a specific trap: turning on Increase Contrast in dark mode can reduce the contrast between dark text and a dark background if a design has not been tested that way. A dark theme is accessible when it survives all of these combinations, not just the default dark appearance.
In forced colors mode, such as Windows contrast themes, the browser replaces author colours for text, backgrounds, borders and more with the user's chosen palette, using system colours such as Canvas and CanvasText, and may draw a backplate behind text to keep it readable. A design built on background colours to show state — a selected card that is only a slightly lighter surface, a toggle whose 'on' state is only a fill colour — can lose those states entirely. Use borders, outlines, icons and text to express state, and test in forced colours mode; where a component truly needs its own colours (a colour picker, a chart), the forced-color-adjust property can opt it out, sparingly and with its own high-contrast design.
| Pair | Contrast | Meets |
|---|---|---|
| #FFFFFF on #000000 | 21.00:1 | AAA text |
| #FFFFFF on #121212 | 18.73:1 | AAA text |
| #E0E0E0 on #121212 | 14.19:1 | AAA text |
| #BDBDBD on #121212 | 9.97:1 | AAA text |
| #9E9E9E on #1E1E1E | 6.22:1 | AA text |
| #757575 on #121212 | 4.06:1 | Large text / non-text only |
| #616161 on #121212 | 3.02:1 | Large text / non-text only |
Why: The design assumes dark is universally easier.
Fix: Follow prefers-color-scheme and offer a switch.
Why: Selection was shown by background colour only.
Fix: Add a border, outline or icon for the selected state.
Why: A dark grey used for placeholders falls below 4.5:1 on the dark surface.
Fix: Lighten placeholder text or rely on visible labels.
Each statement is labelled by kind — established fact, a standard’s requirement, observed market data, a convention, or Colourwise’s own interpretation or analysis — with the strength of the evidence behind it.
FactModerate evidence
The W3C's draft on low-vision needs describes light sensitivity in which ordinary screen brightness can be painful or unreadable, leading some people to need a darker background.
Caveat: A 2016 First Public Working Draft; it describes needs rather than prevalence.
Source: Accessibility Requirements for People with Low Vision
StandardStrong evidence
Media Queries Level 5 defines the prefers-color-scheme, prefers-contrast and forced-colors media features for detecting a user's colour-scheme preference, contrast preference and forced colours mode.
Caveat: Media Queries Level 5 is a Working Draft; support varies by feature and browser.
Source: Media Queries Level 5
ConventionModerate evidence
Apple's dark-mode guidance advises testing with Increase Contrast and Reduce Transparency, and warns that Increase Contrast in dark mode can reduce contrast between dark text and a dark background.
Colourwise interpretationLimited evidence
Whether dark mode helps or hinders reading varies between individuals: it can help people with light sensitivity, while some readers, often those with astigmatism, report that light text on dark backgrounds is harder to read.
Based on: Colourwise's reading of W3C low-vision guidance on light sensitivity and of widely reported user experience; no large controlled study is cited for the astigmatism effect.
Caveat: The size and prevalence of the astigmatism effect are not well established.
Reviewed 29 September 2026. Colourwise summarises its sources in its own words and does not reproduce standards text or proprietary colour data. Spotted an error? Tell us.