Checkout labels disappear when buyers start typing
Compare each field while empty with the same field after entry and after focus moves away. If the remaining value has no visible label that explains its purpose, record that loss of meaning. Preserve a readable label and any necessary format guidance while the buyer reviews or edits the value. Ask the component owner to check programmatic association separately; visible wording alone does not establish that association.
For: An owner or checkout maintainer of a research-only store reviewing fields whose only visible instruction appears inside the empty input.
The useful observation is the instruction that remains when the buyer needs to review the answer. Record the empty field’s visible wording, whether it sits inside the input, and what remains in the entered state. A field can look clear before typing and become ambiguous once its only instruction disappears.
Include the state after focus leaves the field. A label that appears only while the cursor is inside does not help the buyer scan completed fields. If the text moves above the value as a floating label and remains readable, record that behavior rather than classifying every inside-field label as a defect. The decision depends on what is actually visible.
Use the checkout’s existing state and genuine, authorized observations. You do not need to place an order or enter payment credentials for this review. Where a populated state is not available without doing that, mark it unobserved and give the maintainer the exact field to investigate. Keep entered personal values out of screenshots and notes.
Distinguish the field’s purpose from its format
W3C’s understanding page for WCAG 2.2 criterion 3.3.2 says labels or instructions are provided when content requires input. Its focus is that people can understand what information is expected. For this review, record the visible purpose of the field independently from any hint about how to enter the value.
A purpose label can remain present while necessary format information vanishes. Conversely, a format hint can remain without identifying what the value represents. Compare each instruction with the store’s actual required input. Do not add an assumed format, make an optional field sound mandatory, or carry a country-specific instruction onto every address path.
When a heading serves a group of fields, record the individual field whose purpose is still unclear. A general billing or delivery heading may establish context without distinguishing each input beneath it. The repair request should name the missing distinction, using the merchant’s real field names rather than asking for more text everywhere.
Keep visible and programmatic labeling as separate findings
The same W3C understanding page explains that programmatic association belongs to a separate criterion. A visible label is therefore evidence about what a reader sees; it does not by itself establish how the field is identified to assistive technology. Likewise, an unseen accessible name does not answer the observation that the visible purpose disappears after entry.
Send the form owner two clear questions: what label and guidance will remain visible in the populated state, and how will that wording be associated with the actual control? Record the component involved, such as a store field or a provider-controlled payment component, only when the installed configuration establishes ownership. If ownership is unknown, leave it open instead of assigning the fault to the theme.
This review does not prescribe one markup change for every checkout. The owner needs the real component, version and rendering behavior to select an implementation. Changes to a hosted field may require that component’s supported controls; the merchant should not infer its editability from its visual position on the page.
Make the repair request observable
State the requested result in terms of the affected field: its purpose remains readable while empty, populated and revisited, and any necessary format guidance remains available when editing. Preserve the distinction between billing and delivery fields, required and optional inputs, and the real purposes of any merchant-added fields.
After a change, compare the same field states that exposed the original loss. Record any remaining ambiguity and keep an unobserved state open. A clearer populated field supports closing that specific finding; it does not establish full accessibility conformance, correct order data or a successful payment.
For a Prism checkout consultation, supply the public checkout location, field name, observed states and the help requested in ordinary language. Confirm review or implementation scope, responsibilities, fees and terms before work. Do not send filled checkout captures, customer records or payment information through the public form.
Persistent-field-label review
Use a separate copy for each affected input. Record wording and state, never the buyer’s entered value. Missing and unobserved are different findings: request a persistent label for an observed loss, and ask the owner to inspect a state you could not safely view.
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.
Persistent-field-label review. The last column is for temporary notes.
Review point
Evidence to record
Decision it supports
Your observation
Input purpose
Evidence to recordThe intended information from the actual field configuration and surrounding checkout context.
Decision it supportsDecide whether the wording distinguishes this field from similar inputs.
Empty-state instruction
Evidence to recordExact visible label or instruction, its position and whether it exists only inside the empty field.
Decision it supportsIdentify which meaning could be lost when the value replaces the instruction.
Entered-state label
Evidence to recordThe label that remains after entry, with the value itself omitted from the record.
Decision it supportsRecord whether the field can still be identified without clearing its value.
Label after focus leaves
Evidence to recordWhat remains when the buyer moves to another field and later returns.
Decision it supportsDistinguish a persistent label from a temporary focus-only cue.
Required format guidance
Evidence to recordThe instruction actually needed by the configured field and where it remains visible.
Decision it supportsRequest missing guidance without inventing a format or requirement.
Affected checkout step
Evidence to recordPublic page, step, billing or delivery context, language and observed device/browser.
Decision it supportsGive the owner the location and conditions of the specific finding.
Programmatic association and owner
Evidence to recordThe maintainer’s separate association finding and the component responsible, or unknown.
Decision it supportsDo not mark association resolved merely because a visible label was added.
Correction result
Evidence to recordThe agreed wording and observations of the same empty, entered and revisited states after correction.
Decision it supportsClose only the loss of meaning that the observed change actually resolves.
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
This field-state review is not a WCAG conformance audit, legal conclusion or certification.
Do not place an order, submit a payment or collect card numbers, authentication codes or private checkout values to fill the worksheet.
A visible improvement does not establish correct data storage, provider eligibility or successful payment processing.
WCAG 2.2 understanding, labels or instructions — checked 2026-09-21. Criterion 3.3.2 requires labels or instructions when input is required; the understanding page distinguishes this from the separate requirement for programmatic association. It does not certify a particular checkout or prescribe this worksheet.
Prism solutions — checked 2026-09-21. Published help includes storefront review and processing preparation within an agreed scope; provider eligibility and account terms remain provider decisions.