Why your returns form is generating support tickets you never see
An unclear custom-order or returns form doesn't just lose sales, it creates the confused emails and phone calls your support team spends all week clearing up. Fixing the form fixes both problems at once.
Every retailer knows the pattern: a customer starts filling in a returns form or a custom order request, gets stuck or confused halfway through, gives up, and emails instead. Now what should have been one clean, structured submission is a back-and-forth thread, and someone on your team is manually extracting the same information the form was supposed to capture in the first place.
The form didn't fail loudly. It just quietly pushed the work somewhere more expensive: your inbox.
The support ticket that started as a form
Think about what actually happens when a returns form is unclear about which fields are required, or a custom order form's dropdown doesn't work with a keyboard. The customer doesn't just stop, most of the time. They email you instead, describing the problem in their own words, missing half the details you actually need. Someone replies asking for an order number. The customer replies with the wrong one. Three emails later you have what a working form would have captured in one submission.
It's not just accessibility, it's clarity
Every one of these failure modes, an unclear label, a confusing multi-step layout, a required field that isn't marked as required, affects disabled and non-disabled customers alike. Fixing accessibility issues tends to fix general usability at the same time.
Where retail forms usually go wrong
The old way
A returns form with no clear indication of which fields are required, a custom order form where the size/colour options are colour-coded with no text label, and a support inbox full of customers asking what information to send.
With FormGenius
Clearly labelled required fields, accessible dropdowns and radio groups, and a colour contrast check before anything goes live. Customers submit once, with everything you need, first time.
Rebuild the form around what you actually need
List the fields your support team currently has to chase by email — order number, item, reason, preferred outcome — and put them directly in the form as clearly labelled, appropriately required fields.
Check it with the Accessibility Wizard
FormGenius checks heading structure, field labels, tab order, and colour contrast, and flags anything that would trip up a screen reader or keyboard-only customer before you publish.
Embed it where customers already are
Add it to product pages or your returns portal with one line of code. It auto-resizes to fit, no separate page required.
The customers you're not seeing at all
Beyond the ones who give up and email, there's a group who just leave. 16.8 million disabled people in the UK shop online (Family Resources Survey, DWP, 2023–24 (opens in new tab)), and 69% say they'll abandon a website altogether if they find it difficult to use (Click-Away Pound Survey, Purple/Extend, 2019 (opens in new tab)). Some of those are customers who wanted to buy from you specifically, a custom order, a bespoke request, and simply couldn't get the form to work.
Reasonable adjustment, not a redesign
The Equality Act 2010 applies to any retailer selling to the public, in-store or online. Using an accessible form tool for the parts of your business that collect customer information is exactly the kind of reasonable adjustment the law describes, not a specialist project.
Create an accessible feedback, custom order, or returns form in minutes, no account needed to start.
Build a customer form free
