Checkout reliability

Checkout text cannot be read in its dark theme

Measure each affected text state against the background it actually appears on. Start with entered values, labels or instructions, error messages and action text. W3C’s WCAG 2.2 Contrast Minimum guidance sets 4.5:1 for ordinary text and lists exceptions, including text that forms part of a logo or brand name. Keep those exceptions separate from functional checkout text. A state-by-state list of measured pairs shows which colors need attention; an attractive dark palette or one readable heading cannot establish that the checkout text is readable throughout.

For: A research-only merchant whose dark checkout makes entered values, instructions or error text difficult to read.

Updated 2026-10-01

Identify the exact text that becomes unreadable

Record the checkout location and the state in which the problem appears. An empty input, an input containing a value, its focused state and an error message are separate observations. Record only states your real checkout presents. If a state has not been observed, leave it unmeasured rather than inventing a result.

Keep the browser, device, theme selection and observation date with the record. Describe whether the store selected a dark theme or you observed some other display setting. The appearance alone does not establish which theme or component controls the color. A localized text problem gives the maintainer a narrower question than a request to redesign the entire page.

Measure the pair that is actually displayed

For each text role, obtain the displayed foreground and the background directly behind it, then record the measured contrast ratio and the tool or method used. The relevant pair for an input is its value text against the input’s background, not automatically the text against the page’s outer background. An error message needs its own pair when it appears on a different surface.

If transparency, an image or a changing background makes the pair uncertain, record the uncertainty and ask the maintainer to measure the rendered state. Do not copy two palette swatches into the worksheet and call them the measured checkout result. A screenshot can locate the problem, but a visual impression alone is not a contrast ratio.

Compare ordinary text with the 4.5:1 value in the cited W3C guidance. Record the measurement rather than rounding a lower value into a pass. If you cannot establish the pair or the measurement, mark it not measured. That row still identifies work; it does not support a conclusion about the criterion.

Keep exceptions separate from the checkout task

The Contrast Minimum guidance includes exceptions and states that text forming part of a logo or brand name has no contrast requirement under this criterion. Put genuine logo text in a separate row if it is part of the review. Do not apply the logo exception to entered values, instructions or ordinary action labels merely because they use the brand’s colors.

For any other claimed exception, retain the specific criterion provision and the facts that make it apply. Do not infer an exception from a field looking muted or a heading looking large. When its classification is unresolved, record that question instead of marking the state acceptable.

This list covers text contrast. It does not assess every aspect of a focus indicator, control outline, error explanation or keyboard interaction. A measured improvement to error text does not establish that the checkout identifies and explains errors adequately; it establishes only the recorded color-pair result.

Request and verify the targeted color correction

Group the affected rows by the component owner and the color setting the maintainer identifies. Ask for a proposed foreground or background change for each failing ordinary-text pair, including the focused or error state when affected. If several rows use the same setting, identify all of them before accepting a shared change. If ownership is unknown, leave it unknown until the component is identified.

After an authorized change, measure the affected pairs again in the same states. Record the new pair, ratio and date next to the earlier result. Close only rows whose measurement and applicable criterion have been resolved. If an input improved but its error message did not, the remaining row supplies a precise next action.

For a Prism checkout-review consultation, provide the website, research-only product context and a summary of the unreadable text states. Confirm the assessment and any implementation responsibilities, fees and terms before work. The public form excludes card details, passwords and customer records; follow-up is by email. It does not book an appointment, purchase work or submit a processing application. A contrast correction does not determine provider eligibility or establish whole-site accessibility conformance.

Text contrast correction list

Use the last column to record the real foreground, actual background, measured ratio, component owner and proposed change for each observed state. Keep before-and-after values together. No measured result is supplied here; an unmeasured or unclassified row stays open.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Text contrast correction list. The last column is for temporary notes.
Text role or statePair to measure and evidence to keepHow to decide the next actionYour measurement and correction
Entered valueVisible value text against the input background, including the observed focused state; omit the actual value.For ordinary text, compare the ratio with 4.5:1 and assign the color setting to its maintainer.
Label and instructionsEach label or instruction against the surface directly behind it.Keep separate pairs when the label and instruction use different colors or surfaces.
Error messageError text against the background present when the message is visible.Measure this state independently; readable ordinary field text does not settle it.
Next-action textThe ordinary text on the action control against that control’s actual fill.Do not infer readability from the surrounding page; record any unresolved exception separately.
Totals and required noticesThe displayed amount text and notice text, with a separate measurement for each differing pair.Retain each result; one prominent readable total does not establish that every notice is readable.
Logo or brand-name textIdentify the exact text that is part of a logo or brand name.Record the stated exception separately; do not extend it to functional text in brand colors.
Owner and proposed changeComponent owner, identified setting, affected rows and proposed foreground or background change.Keep the request targeted; an unknown owner or color source needs identification.
Correction resultNew foreground/background pair, ratio, state, method and observation date.Close the affected measured row only; retain unresolved states without a whole-checkout conformance claim.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.

Limits

  • WCAG 2.2 Contrast Minimum includes exceptions. This page does not determine their application from appearance alone or claim compliance with any law.
  • Text contrast measurements do not constitute a full accessibility assessment or guarantee that a control is operable.
  • Use genuine observed states, omit entered customer or payment values, and do not submit an order or payment to fill this worksheet.

Sources

  • WCAG 2.2 understanding, contrast minimum — checked 2026-09-21. Success criterion 1.4.3 states a 4.5:1 text contrast ratio and lists exceptions, including text that is part of a logo or brand name. This supports a bounded text-pair review, not a whole-checkout conformance claim.
  • Prism solutions — checked 2026-09-21. Published support includes storefront review and help with provider website questions; scope, fees and terms are discussed before work and provider eligibility remains the provider’s decision.
  • Prism contact — checked 2026-09-21. The form asks for the website, products and question and excludes payment-card details, passwords and customer records. Email follow-up is not an appointment, purchase or processing application.

Get help with checkout

Is this happening on your own store?