Readability

Color puzzle readability: a five-minute check before a long session
Check whether essential states remain distinguishable using labels, position, shape, and ordinary screen settings.
A reader-run usability checklist and constructed symbol examples. No specific game is certified accessible, and this is not a clinical test of color vision.
On this page
Ask what information the color carries
Color can decorate a board, identify a match group, show the active selection, or warn about failure. These roles require different checks. Missing a decorative gradient may not affect play. Confusing two match groups can make a correct decision impossible.
List the decisions you must make: select a source, distinguish its type, choose a destination, and tell whether the move was accepted. Then ask which of those decisions depends exclusively on a color difference. This identifies the practical problem more precisely than describing a game as bright or colorful.
Compare three representations of the same board
Consider two containers that look similar at your chosen brightness. In one design their only labels are different hues. In a second design they have letters A and B. In a third they also carry distinct patterns. If the hues are difficult to separate, the lettered or patterned board preserves information that the hue-only board loses.
Position can help you track an item temporarily, but it is not a reliable identity cue when pieces move or the board shuffles. A label that travels with the piece remains useful. The following constructed example represents identical logic with redundant symbols; it is not a screenshot or an accessibility claim about a title.
Type identity: A = stripes B = dots Tube 1 bottom→top: [A, B] Tube 2 bottom→top: [B, A] Spare tube: [] If hue becomes unclear, letters still identify the legal match.
Check the board at the size you will actually use
Open an early, low-stakes board and use your normal device, viewing distance, and brightness. Inspect small counters and selection outlines as well as the large pieces. A crisp promotional image does not establish that the running interface is legible.
- Can I identify all match types without leaning closer or repeatedly guessing?
- When a piece is selected, does a border, marker, movement, or label show the state?
- Can I tell an illegal move from an accepted move without depending on sound alone?
- Are timers and remaining-move counters readable without covering the board?
- If I zoom or rotate the device, do essential controls remain available?
Change one condition at a time
If two types are hard to distinguish, first look for an in-game palette, symbol, or pattern setting. Then try a comfortable brightness change. Change one condition at a time so you can tell what helped. Avoid assuming that a phone-wide color filter will improve every pair of colors in a board.
A grayscale preview may reveal that two hues have similar brightness, but it does not simulate every person’s perception. Passing that check is not proof of accessibility. Likewise, increasing saturation can make a screen look stronger without adding a usable cue for a player who cannot distinguish the relevant hues.
Record a specific problem that someone can reproduce
“Colors are bad” gives little direction. A useful note identifies the stage, the two confusable types, the action affected, your device or viewport, and the setting that changed the result. For example: “On the opening tube board at my normal phone brightness, the top layers in tubes 2 and 4 are indistinguishable; there are no letters or patterns.”
If you send a screenshot for a correction, crop unrelated personal information. Explain what you saw rather than inferring how everyone will see it. A report can be accurate for your setup without proving that every visitor encounters the same difficulty.
Choose another mechanic when the information stays unclear
If essential match types remain ambiguous, forcing more attempts is unlikely to make the rules clearer. Consider a puzzle that encodes identity with numbers, shapes, or labeled connections. Check those alternatives too: small numerals and thin paths can introduce their own readability problems.
The aim of this check is a practical choice for your session. It does not replace a full accessibility evaluation, test keyboard operation, establish screen-reader support, or prove mobile compatibility. It helps answer a narrower question before you invest time: can I reliably perceive the information this board asks me to use?

