Singapore design critiques: keep form-field meaning visible after typing

The problem

A Singapore UX practitioner uses placeholder text to explain every field, but once values are entered the form no longer shows which value belongs to which question or what the expected format was.

Review a filled form first

Populate a safe example with invented values and leave one field incomplete. Ask another person to identify the purpose of each value without clearing it. The filled state exposes information that an empty-screen review can miss. Note which field needs a label, a format instruction or a section heading; these are different kinds of context. Record what identifies the field before entry, while it contains a value and when someone returns to inspect it. A hint that disappears can describe an expected example without supplying persistent identity. A stored value alone may fit several meanings. Write down which question the visible state can answer: what this field is for, which input format it expects or whether submission succeeded. Those are different questions. Check invalid submission and recovery separately; this comparison examines whether the filled state still communicates the purpose of the entry.

Compare field identity and input guidance separately

Use five entries per field: intended purpose; empty-state identity and hint; filled-state identity; supplied value; and missing meaning or format question. Include material origin and assistance. Keep the label’s wording separate from an example format such as a supplied illustration of an input. If the filled view is absent, mark it absent rather than declaring that the empty screenshot proves continued identity. The reusable record helps prepare a critique, not establish which label every real form must use. The project’s actual task, terminology and user research provide the context for that decision.

Separate an example from the question

SGDS v2 guidance recommends visible field labels rather than relying on disappearing placeholder text. A placeholder can show an example, but the person still needs to know what they are being asked to provide. Write the field's purpose in plain words before refining its visual placement. Keep a format hint only where the task actually requires that format. Keep the source’s date and version notice with the design context. The SGDS v2 accessibility page is dated 31 May 2024 and displays a version3 notice; its visible-label guidance is retained historical context. It is not presented here as a current standard or project certification. Use the empty-and-filled comparison to inspect the field meaning that remains visible. Check the actual form’s fields, terminology and valid formats. A persistent label can improve the available meaning while leaving comprehension, error recovery and other accessibility questions unanswered.

• SGDS | Accessibility ↗ · Source checked 8 October 2026

Inspect a wholly invented pair of filled fields

Every screen and value in this case is fictional. A toy form’s empty view uses placeholder text “Contact name” and “Collection title”, with no separately visible labels. Its supplied filled view shows Nora in the first field and Cedar in the second; both placeholders have disappeared. The record does not show another visible indication of either field’s purpose. A viewer who sees only that state has the values but lacks the supplied field identities. Cedar could be a title or another kind of name. The exercise identifies a missing visible-meaning question; it does not report how real users perform.

Test interruption and review

Pause midway through the form, then return to it and ask the person to check their entries. Observe whether they can identify a mistaken value without remembering the original placeholder. Use adjacent fields that could plausibly be confused, such as an organisation contact and an attendee contact. Do not collect real details merely to make the demonstration feel authentic. Ask the reviewer what each filled field appears to mean before explaining your intended schema. Record their answer and the state they saw. An interpretation that differs from your intention can identify a question to investigate, but it is one reviewer’s response under the stated conditions. A spoken explanation may clarify the schema without changing what the screen itself communicates. Confirm whether the actual critique accepts interaction states or only static visual work, and which material may be displayed. Use an invented form when the real entries or project are unsuitable to share.

Keep an owner’s schema answer distinct from the interface

Continue the fictional case. The form owner states that Nora is the contact name and Cedar the collection title. Record that as the supplied intended schema. It clarifies what the two entries mean to the owner, but it does not make those labels appear on the filled screen. The portfolio can now distinguish known intention from the visible-state gap. A critique question is “What identifies these two purposes when the hints have disappeared?” It is different from asking whether the values are valid or whether the form submitted them successfully.

Describe the supplied revised state precisely

A later fictional version shows the persistent headings Contact name and Collection title above the same filled values. That supplied view makes the intended field identities available in the filled state. It still contains no participant comprehension observation, keyboard path, validation result or submission outcome. Keep the revised screenshot’s supplied origin and the earlier state so the actual change is inspectable. A subsequent agreed review could examine whether the intended audience understands the wording; its planned feedback is not a result yet. One clearer pair of labels does not answer every question about the form.

Choose critique that examines information hierarchy

Bring the filled-state observation and a proposed label or hint to the session. Ask what must remain visible, what can be introduced as help and how related fields should be grouped. A portfolio can show the decision and the tested state without claiming universal access. State that the cited SGDS page is v2 guidance and keep later implementation checks separate. Save the empty state, filled state, intended field meaning, reviewer response and any revised state with their origins. Explain which identity question became clearer and which result is still missing. Inspect image or icon task meaning and keyboard focus location separately. A better field label supplies neither by itself. Choose a critique able to examine the relevant filled state, then check its current preparation, participation and access conditions. A useful portfolio note can show a specific design question without promising a completed usability or accessibility assessment.