Text Color Adjustable
Group: text-and-wording • Guideline: text-appearance
Summary in Plain English
The foreground and background colour of text can be changed without losing content or functionality. The exceptions mirror the contrast requirement: text also present elsewhere in a conforming form, text in an inactive control, pure decoration, invisible text, text within a substantive picture, and logos.
Why It Matters
Many people read only with a specific colour combination - light text on dark, or a tinted background for scotopic sensitivity. Content that resists recolouring blocks the adaptation they depend on.
Scope: When This Applies
The draft's own conditions, quoted from guidelines/groups/text-and-wording/text-appearance/text-color-adjustable.md.
Applies when
- text is presented, including text embedded in an image format.
Except when
- the text is:
- also present elsewhere in the page/view which meets the requirement
- part of an inactive interactive element
- pure decoration
- not visible to anyone
- part of a picture that includes significant other visual content
- part of a logo
Notes in the draft
The requirement is that the text is manipulable and the colors can be overridden. That could be achieved by the user-agent (including operating system, browser, and assistive technology), or provided by the content author.
Test Procedure from the W3C Draft
Quoted from the provision's informative document, informative/guidelines/text-and-wording/text-appearance/text-color-adjustable.md. It is the group's own procedure, not an editorial testing guide.
Procedure
For each block of text:
- Adjust the foreground and background color to a high-contrast light-on-dark theme.
- Check that content and functionality is not lost.
- Adjust the foreground and background color to a high-contrast dark-on-light theme.
- Check that content and functionality is not lost.
Expected results
- #2 and #4 are true.
W3C Working Group Status
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
4 GitHub threads carrying 7 comments, fetched from w3c/wcag3 by the tracker. Titles, numbers and states are the threads' own.
What the Argument Is About
Whether a maximum contrast ratio should exist, or whether the real variable is screen luminance and the answer is user adjustability instead.
Positions taken in the thread
cawa-93 opens #171 with white text on black at a 21:1 ratio, which passes 1.4.6 Contrast (Enhanced) at AAA and is, in their words, absolutely not readable, and proposes a maximum alongside the minimum. NathanInnes offers Twitter's branding revamp as a case in point: it passed beyond the standard and a lot of users found it difficult to read and straining on the eyes.
JAWS-test finds high-contrast text readable in itself, accepts that some people struggle with it, and argues the fix is for colour adaptation to user needs to work well and for WCAG to support that adaptability via custom styles, Windows High Contrast Mode and similar. mraccess77 says a contrast maximum would negatively affect them personally while acknowledging others need low contrast, and concedes specific bad combinations exist โ small white text on black being one โ before asking whether a better calculation than current contrast could isolate those cases, pointing at Myndex's work.
Myndex's objection in #171 is that WCAG 2 contrast math is not perceptually accurate โ it already overstates minimum contrast for dark colours โ so building a cap on it would produce more unreadable pages, not fewer, and entrench the misunderstanding of how contrast and readability work. Reframes the problem as excess luminance rather than excess ratio: users crank screen brightness to cope with all the low-contrast content in the wild, then get blasted by a site with good contrast. Also notes the OP's own example is too small and too crowded to be evidence. bruce-usab agrees white on black is a common barrier but cannot see how to address it in WCAG 2.x even at AAA, since the same rule would flag plain black-on-white body text, and points to APCA as the WCAG 3 route.
The 2023 status update separates the cases: no maximum contrast in light mode, only a maximum luminance, which is a user display control rather than an author one, with paper-emulation best practice of keeping body-text background at about 85 percent of the adaptation state. Dark mode is different โ excessively bright text on dark backgrounds causes halation and glare โ and names interim experimental values under study of Lc -90 maximum for body text and Lc -85 for larger text, using APCA 0.0.98G4g. Adds that there is room for at least two dark schemes, day and night, and that daltonised, photophobia and Meares-Irlen schemes will likely need their own maxima.
Reports from a calibrated setup โ displays at 150 cd/m2 white luminance, room illuminance around 100 lx, IPS LCD at roughly 1000:1 static contrast โ that black on white is comfortable while white on black remains practically unreadable, partly from halation due to astigmatism. Finds Lc -90 uncomfortable and would want something nearer Lc -50 for light-on-dark. Also warns the fix cuts both ways: in a properly calibrated environment, an author lowering contrast for dark text on light backgrounds reduces readability, comparing blue on brown to printing on kraft paper rather than white.
emanser869's #178 proposes adding to 1.4.8 that foreground and background colours can be adjusted by the user to apply uniformity of contrast.
utkudyn-a11y's #618 asks that captions carry at least 4.5:1 between caption text and its background as a core requirement, in addition to the supplemental captions-adjustable requirement, because caption legibility directly affects partially sighted and low-vision users.
Agreed
- Some specific high-ratio combinations genuinely are hard to read โ small white text on black is named by cawa-93, mraccess77 and bruce-usab alike. The dispute is over the remedy, not the symptom.
- Users need a way to adapt foreground and background colours to their own needs; JAWS-test, mraccess77 and emanser869 all land here.
- Screen brightness set too high is a real contributing cause. kepstin agrees with Myndex on this even while disagreeing about the threshold.
- WCAG 2.x contrast math is the wrong instrument for a maximum; Myndex's objection went unrebutted, though cawa-93 and NathanInnes had earlier proposed a maximum on the existing ratio.
Still open
- Whether a maximum contrast value should be normative at all, and for which modes. Myndex's dark-mode-only framing is the most developed answer and has drawn one substantive response.
- Where the dark-mode maximum sits. kepstin's lived report of Lc -50 is roughly 40 Lc away from the Lc -90 under study, and nobody has reconciled the two.
- How to raise readability for users on too-bright displays without cutting contrast below what users with correctly calibrated displays need โ kepstin states this as an unsolved trade-off.
- Whether peak-luminance choice for a given dark scheme is a user display responsibility or an author one, which Myndex flags as open and complicated by ambient light and device output range.
- What "high-contrast" means in the provision's own tests, which reference a high-contrast light-on-dark theme and a high-contrast dark-on-light theme without defining the term. julierawe asked this in #501.
- utkudyn-a11y's proposal to make a 4.5:1 caption-background ratio a core requirement.
Note
The discussion is almost entirely #171, and much of it is old โ the substantive exchange runs 2021 to 2023 with a single 2025 reply from kepstin. #178, #501 and #618 are unanswered issue bodies; julierawe's definitional question in #501 is short, central to testing this provision, and has no response at all.
- #171 Proposal to introduce maximum contrast ratio open 7 comments · updated 2026-05-02
- #178 Proposed addition to Success Criterion 1.4.8 Visual Presentation open 0 comments · updated 2026-05-02
- #501 What counts as "high-contrast" in Adjustable text color? open 0 comments · updated 2026-03-27
- #618 2.1.4 Captions - Core Requirement Suggestion open 0 comments · updated 2026-03-27
WCAG 2.2 Criteria That Map Here
From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is an interpretation, not a W3C mapping: W3C has not published one yet.
W3C Raw Source Text
Verbatim from guidelines/groups/text-and-wording/text-appearance/text-color-adjustable.md · informative document: informative/guidelines/text-and-wording/text-appearance/text-color-adjustable.md
The foreground and background color of text can be adjusted without losing content or functionality. :::note The requirement is that the text is manipulable and the colors can be overridden. That could be achieved by the user-agent (including operating system, browser, and assistive technology), or provided by the content author. ::: :::applies-when * text is presented, including text embedded in an image format. ::: :::except-when * the text is: * also present elsewhere in the page/view which meets the requirement * part of an inactive interactive element * pure decoration * not visible to anyone * part of a picture that includes significant other visual content * part of a logo :::