The Forgotten Page: Making Order Confirmation and Tracking Accessible

2026-10-17

Accessibility audits stop at the payment button, as if the purchase were the end of the journey. For shoppers it is the middle. The confirmation page, the tracking page, and the returns flow get visited repeatedly, often anxiously, and they are built with the least care of any templates on the site.

Disabled shoppers feel that neglect directly: order numbers rendered as images, delivery status shown only as a colored progress bar, return buttons that exist only inside a hover menu. A focused pass on the post purchase pages fixes the part of the journey with the highest emotional stakes.

Structure the confirmation like a document

The confirmation page should read like a receipt a person can scan with any tool: a clear heading announcing success, the order number as text in the first screenful, then items, totals, delivery estimate, and what happens next, each under its own heading. Screen reader users navigate by headings, so that structure is the page's table of contents.

Avoid conveying status by layout alone. A timeline graphic that shows shipped as a filled dot means nothing without text. Every visual state on the page, confirmed, shipped, out for delivery, needs a text equivalent adjacent to it.

Announce success, do not just show it

When the confirmation loads after payment, the success message should be programmatically announced, with focus moved to the confirmation heading. A screen reader user who hears nothing after pressing pay is left wondering whether they have bought the item twice or not at all, which is a real and common anxiety.

The confirmation email carries the same duty and the same faults. Order details locked in images or PDFs that read as gibberish help no one. Plain text structure in the email, with the order number early, mirrors the page and covers shoppers who never return to the site.

Tracking and returns in one keyboard step

From the confirmation, tracking and returns should each be reachable in one obvious step, as real links or buttons with descriptive names. Track package and start a return beat a generic manage order that hides both behind another login wall, especially when the shopper checked out as a guest.

Status pages linked from emails must not demand information the shopper cannot retrieve accessibly. If viewing a delivery window requires the order number, say where it appears in the email, in text, not go check your confirmation screenshot.

Test the anxious journeys, not just the happy path

Audit the moments that go wrong: the delayed parcel, the return label, the exchange form, the where is my refund page. These are the journeys disabled shoppers take most and teams test least, because they sit outside the conversion funnel metrics.

Include them in the regression set. A tracking page that breaks in a redesign generates support calls, chargebacks, and lost repeat buyers. Post purchase accessibility is retention work disguised as compliance work.

Frequently asked questions

Why audit confirmation pages if checkout already passes?

Because shoppers return to confirmation, tracking, and returns pages repeatedly and under stress. Faults there, like image only order numbers or color only status, strand disabled shoppers after the sale, when support is their only recourse.

What should a confirmation page announce?

That the order succeeded, the order number as real text, what was bought, the delivery estimate, and the next steps, structured under headings so screen reader users can navigate straight to the part they need.

How should delivery status be shown accessibly?

Every visual state needs adjacent text: confirmed, shipped, out for delivery, delivered, with dates. A progress bar or colored dot can supplement the words but never replace them.

Are confirmation emails part of accessibility scope?

Yes. For many shoppers the email is the record of the order. Its key facts should be structured plain text, readable by screen readers, not locked inside images or inaccessible attachments.