Accessible Gift Message and Delivery Instruction Fields at Checkout

Gift message boxes and delivery instructions are small fields with outsized failure rates: character counters nobody announces, tiny text areas, and instructions that vanish before the courier sees them.

The gift message field is where a thoughtful order goes wrong quietly. A shopper writes a note, the character counter ticks down in silence, the text is cut off mid sentence at a limit nobody stated, and the card arrives truncated. For a screen reader user there was never a counter at all, just a field that stopped accepting sense.

Delivery instructions fail in the same direction. A small text area with a placeholder as its only label, no stated limit, and no confirmation that the instructions were saved with the order. WCAG 3.3.2 covers labels and instructions, and 1.3.5 covers the input purpose where these fields map onto standard fields. Small fields, basic criteria, constant failures.

Counters and limits have to be announced

If a field has a character limit, state it before the field, in the label or the hint text, not in a counter that only changes colour as it runs out. Live counters can help if they are handled carefully: an aria-live announcement at sensible intervals, not on every keystroke, so a screen reader user hears characters remaining at 20 and at 0 rather than a running commentary that makes typing impossible.

When the limit cuts text off, say so. Silently truncating a message at 150 characters and showing the shopper their full text in the field is a small deception that produces a broken gift card and a support call. Either prevent further typing and announce the limit, or accept the text and print it whole. Pick one and make the interface honest about which.

Labels that survive the placeholder disappearing

Placeholder text is not a label. It vanishes when typing starts, it is often too low in contrast, and it leaves a shopper with memory or cognitive difficulties staring at a filled field with no idea what it was for. Gift message, delivery instructions, order notes: each needs a permanent visible label and, where it matters, a hint about what the courier or gift recipient will actually see.

Instructions fields also need a purpose the shopper can trust. If instructions go to the courier, say that. If they are read by the packing team and never leave the warehouse, say that instead, because shoppers write gate codes into fields that couriers never see and then blame the driver. Clarity here is not accessibility garnish. It is the field working at all.

Confirm what was saved, in the order summary

After checkout, the gift message and instructions should appear in the order summary and confirmation email as ordinary text, exactly as entered. That read back is how a screen reader user verifies the note survived, and it is how any shopper catches a truncation before the parcel leaves.

Test the whole path once with a keyboard and once with a screen reader: find the field, read its label and limit, type past the limit, submit, and read the confirmation. Four steps. If any step surprises you, it surprises a paying customer every day, in a field that exists purely to make someone elses day better.

Related reading

If this topic is useful, these earlier guides go deeper on connected questions: Accessible Password Creation: Where Signup Forms Lock People Out, Accessible Date Pickers and Delivery Calendars at Checkout, and Accessible Promo Code Entry at Checkout.

Frequently asked questions

Why is a character counter an accessibility issue?

Because if the count is only visual, screen reader users get no warning before text is cut off. State the limit in the label or hint, and if a live counter is used, announce it at intervals rather than on every keystroke.

Is placeholder text enough as a field label?

No. Placeholders disappear when typing starts and often fail contrast expectations. Every field needs a permanent visible label, which WCAG 3.3.2 covers under labels or instructions.

Should gift messages appear in the confirmation email?

Yes, as plain text exactly as entered. That read back lets every shopper, including screen reader users, verify the message survived checkout intact before the order ships.

What should delivery instruction fields explain?

Who reads the instructions, the courier, the packing team, or both, plus any character limit. Shoppers write useful instructions when they know where the text goes, and misleading fields produce gate codes nobody ever sees.