Accessible Order Notes and Delivery Instructions: The Forgotten Cart Fields
2026-10-22
Gift messages, delivery instructions, and order notes are where accessibility quietly breaks: unlabeled textareas, character counters nobody announces, and instructions that vanish between cart and checkout.
These fields look too simple to fail. A box, a prompt, done. But they carry high-stakes content: the gate code, the allergy note, the gift message that must not include a receipt. When the field fails, the order succeeds and the delivery goes wrong, which is the worst failure shape in commerce.
Labels that survive contact with the field
Placeholder text is not a label. It vanishes on typing, it is often too low-contrast to read, and screen readers announce it inconsistently. Every note field needs a persistent label above it that says what the field is for and, just as important, what it is not for, since shoppers routinely put urgent delivery information into gift message fields nobody reads at the warehouse.
One label, one purpose. Stores that merge gift messages and delivery instructions into a single notes box create a routing problem no label can fix. Separate fields, routed to the teams that act on them, are an operations fix that shows up as an accessibility win: the customer can finally predict where her words go.
Character limits without ambush
Gift messages have real limits, usually the card size. Enforce them kindly: show the limit in the label, count down visibly as the customer types, and announce through a live region at twenty characters remaining. The failure to avoid is silent truncation, where the message saves cut mid-sentence and the customer learns about it from the recipient.
Hard stops are better than silent cuts but worse than counters. A field that refuses the 141st character with no explanation feels broken. A field that says '140 characters, 12 remaining' feels like a tool. The difference is a line of text and an aria-live attribute.
Persistence from cart to confirmation
The note typed in the cart drawer should appear, readable, at checkout and on the confirmation, in the customer's own words. Making her retype it at checkout because the drawer and the checkout use different fields is a tax on every customer and a wall for customers whose typing is slow, dictated, or switch-driven.
Confirmation matters for trust. A customer who wrote 'leave at side gate, code 4419' checks the confirmation email for that string. When it is absent, she calls support, not because the note was lost, but because you gave her no way to know it survived. Showing it costs nothing and closes the loop.
A ten-minute audit
Add a note in the cart with the keyboard only. Confirm the label is announced, type past the limit and watch the behavior, then complete checkout and find the note on the confirmation page and in the admin order view. Each hand-off is a place notes die.
Check the warehouse end too. If the note prints on the packing slip in a font and position pickers actually see, the field works. Accessibility of the customer's input is half the system; the other half is whether the humans fulfilling the order can read what she wrote.
Related reading
These earlier guides go deeper on connected questions: Accessible Quantity Controls in the Cart: Steppers, Inputs, and Focus, Accessible Gift Card Flows in the Cart: Codes, Balances, and Error Messages, and Accessible Subscription Controls in the Cart: Pause, Skip, and Cancel Without Traps.
Frequently asked questions
Is placeholder text enough as a field label?
No. Placeholders disappear while typing, often fail contrast requirements, and are announced inconsistently by screen readers. Use a persistent visible label and keep the placeholder, if any, as a short example.
How should character limits be communicated?
State the limit in the label, show a live counter, and announce at a threshold such as twenty characters remaining. Never truncate silently; a cut gift message is worse than a shorter one the customer chose.
Why do order notes disappear between cart and checkout?
Usually because the cart drawer uses a theme field while checkout uses a different attribute, and the two are never synced. Map one field through the whole journey and display it at checkout and confirmation.
Where should delivery instructions live: cart or checkout?
Wherever they are collected, they must reach the packing slip and the carrier notes. Collect them once, show them back at confirmation, and verify they print where fulfillment staff will see them.