ManYue colour cues: cross-check identity and state with shape and text

Red lights, blue clothes and coloured frames can carry important cues, but illumination and distinguishability complicate colour judgements. Check one colour-based inference in ManYue against same-scene shape, wording and action. This offers no colour-vision diagnosis and assumes no colour-blindness simulator or automatic palette repair; the aim is not to rest a conclusion solely on an unchecked colour name.

Choose a place where colour carries information

Choose an authorised completed signal, team uniform or designated prop and record edition, chapter, panel, object and initial colour judgement. Determine whether colour decorates or encodes identity, action or state instead of turning every palette into a puzzle. Inspect the whole page and seek a legend or dialogue, not an isolated swatch. Check one question such as whether a light means stop. If a hue is unclear, use a positional label rather than forcing a colour name.

Fix the file and viewing conditions

Record identical file, orientation, fitted/enlarged view and current light/dark theme without changing source simultaneously. A surrounding-background change does not establish altered image pixels. Check the same-edition source for suspected copy differences rather than relying on cover or filename. Compressed or forwarded screenshots need not preserve original colour evidence. Report actual differences without claiming calibrated screens or identical rendering everywhere, and carry these conditions into interpretation.

Find a second cue beyond colour

Check fixed signal positions, labels, badges, shapes or explicit dialogue against the colour inference. In an invented case, differently coloured lights also have circle and triangle marks; those can cross-check state only if their meanings are established. Do not invent universal red-means-stop or blue-means-allowed rules. Shapes may also blur or repeat, so state which cue is reliable and which remains uncertain. A second cue is a check, not another unsupported guess masking colour uncertainty.

Separate lighting change from identity change

Compare contours, marks and illumination across appearances. Night, coloured light or shade may alter appearance without a different prop or team. Blue-looking clothes turning purple do not automatically change character identity; inspect action continuity and names. Retain explicit colour-change state rules where established. Separate object identity, actual state and displayed appearance, allowing unknowns. Log recolouring revisions by edition rather than merging them with in-story illumination.

Check what remains knowable without a clear hue

Without altering the source, temporarily omit colour names from your log and explain state through position, shape and text. If distinction then fails, note the need for a reliable legend or clearer edition instead of guessing. Do not claim a greyscale test without doing one, and do not substitute this method for accessibility checks for all users. The principle of additional cues can inform the exercise, but the report concerns this comic, not compliance certification for app or work.

Leave, return and test cue correspondence

Save supported references or external locations for target and explicit explanation, including object, shape, label and uncertain hue. Leave and return to the same object, reading the label before colour and testing agreement. Add position for adjacent identical lights. Give tall images landmarks and favourites chapter references; a swatch alone is inadequate evidence. Recheck palette and legend after edition changes, manually relocating references where needed without assuming automatic state recognition.

Preserve disagreement between cues

If colour seems to mean stop while text says continue, verify the same object, time and edition legend before logging disagreement. Do not rename a cue for certainty or treat a possible character mistake as proven. Check adjacent pages for faulty signals, deception or illumination explanations; otherwise leave state unresolved. Compare the identical source at the same location externally if useful. A difference there establishes different paths, not a particular algorithmic cause. Keep the conflict as an evidence question rather than letting the easiest cue overrule other information.

Finish a conditional colour judgement

Finish with initial judgement, conditions, second cue, agreement and unknowns. Illumination may change colour without identity, and a clear legend still requires correct object matching. Leave a difficult colour-only conclusion unconfirmed rather than forcing a guess. Explain usable non-colour cues with lawful references instead of distributing pages. Honest limits are more useful than pretending all hues are clear, and personal difficulty alone diagnoses neither vision nor software.

Related guides and sources

ManYue character identity checks: evidence through disguise and style changes; ManYue appearance: dark mode, backgrounds and screen display.

Checked on November 6, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.

For the design principle, see W3C: Use of Color. Its principle of additional cues does not mean this article has completed accessibility compliance checks for the app or comic.