Accessible Returns Portals: Starting and Tracking a Return
Returns portals are often third party tools with their own forms and status pages. How to keep starting, posting, and tracking a return open to everyone.
A return is a moment of already low goodwill, and the portal that handles it is frequently the least accessible part of a store's operation. Order lookup forms with unlabelled fields, reason dropdowns that need a mouse, and status pages conveyed as coloured dots all appear regularly.
The store chose the portal, so its barriers belong to the store. Checking the returns journey with the same care as checkout is what being ready actually means here.
Starting a return without friction
Order lookup should accept the details a customer realistically has, an order number and email, with each field labelled and the format explained. Requiring an account creation at return stage adds a barrier exactly when a frustrated customer has least patience.
Reason selection shapes refunds and exchanges, so every option must be reachable and understandable by keyboard and screen reader, with a free text option for cases the list does not cover. A return that cannot be started is a purchase risk customers remember.
Labels, timelines, and status in words
The portal should produce a return label or clear posting instructions in a form the customer can actually use, and state the timeline in text: when the refund lands, how they will be told, and what to do if the date passes.
Tracking status must be words, not a progress graphic alone. Received, inspected, refund issued, with dates, is information. A row of circles turning green is decoration.
Hold the vendor to the standard
Put accessibility acceptance tests in the returns contract and run them: start a return by keyboard, read every status by screen reader, download the label on a phone. Log failures with the vendor and track them like checkout defects.
Until the portal is sound, offer an assisted route with equal terms, email or phone returns handled by staff, and say so on the returns page so customers are not stranded with the tool.
Measure returns like checkout
Put numbers on the returns journey: how many customers start a return, how many finish without contacting support, and how many support contacts mention the portal. A portal quietly failing disabled customers shows up as assisted contacts and abandoned returns long before anyone files a formal complaint, and those figures give the vendor conversation the weight a single anecdote cannot.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Making Size and Colour Swatches Accessible, Accessible Gift Cards: Buying, Sending, and Redeeming, and Accessible Product Bundles and Gift Sets.
Frequently asked questions
Why do returns portals get overlooked in accessibility work?
Because they are third party tools bolted on after the main site, often owned by operations rather than the web team. Audits stop at checkout, and the returns journey is tested least where customers are already unhappy.
What does an accessible return status look like?
Plain text stages with dates: parcel received, item inspected, refund issued, and the amount. A graphic timeline can accompany that text but cannot replace it.
Should customers need an account to return something?
No. Order number plus email or postcode is enough to verify a purchase and is what guest shoppers have. Forcing account creation at returns stage blocks exactly the customers guest checkout served.
What if the returns vendor cannot fix barriers quickly?
Offer a staff assisted returns route on the same terms and publish it on the returns page, while tracking the vendor defects to closure. The alternative keeps customers served and pressure on the fix.