How to make a website form easier to finish
Try your own checkout or contact form with a missing entry. See whether you can tell what happened and how to fix it.
Suppose a customer orders flowers for pickup. They enter the message for the card and then skip their email by mistake. When they press Continue, a red border appears. The customer has to hunt for the field before they can move on.
That is a useful test because it starts with a realistic mistake. Use a test order, keep your browser settings ordinary at first, and follow the entire route. You want to see the order number or a clear confirmation at the end.
Keep a visible label on each field
Put a short label beside the input and connect that label to the control in the page code. The W3C guide to accessible forms shows how an associated label identifies the purpose of a field to users of assistive technology. If you use temporary text inside an empty input, keep the visible label available after the customer starts typing.
Try this with two fields that sound alike. Label the number used for a pickup alert separately from the number that belongs to the person receiving a gift. If you ask for only one, explain who should give their number. Make that decision while writing the field label so customers can see it in context.
Put the answer to a field's likely question beside the label. A designer may know what "contact number" means, while a customer ordering a gift may expect the recipient to receive the message.

Explain requirements before customers submit
Use an instruction that tells people what to enter. If a coupon has a special format, give a harmless example beside the box. Explain whether the customer needs an account before they start placing the order. The W3C guide to form instructions describes how to present directions and identify required inputs.
Review each question with the person who processes submissions. Ask what they do with the answer and what happens if they lack it. If it makes no difference to the order, consider making the input optional. Try typing a name with a space or an apostrophe so a rule intended for fake data does not catch a real name.
Try leaving only a single field blank so you can tell whether its message points you to the right place.
Put helpful words in the error
Say which field needs attention and how the customer can repair it. For example, "Enter an email address like name@example.com" gives a person a next move. The W3C guide to form notifications describes identifying errors in text and ways to connect messages to their controls. Keep the wording close to the field it refers to.
On a longer form, discuss an error summary with your developer. A customer can use it to move to the field and correct the entry. Try submitting with two errors at once. Fix the first, navigate to the second and check that the original answers stay where you entered them when you retry.
Test success and failure at checkout
Use test details and stop short of spending money on a real order. On a safe test checkout, try a payment failure and then a successful attempt. A customer needs a clear result from each attempt. The W3C guide to form notifications includes guidance on communicating completion and errors.
If your site goes to a payment provider, include that hop in the test. Ask whether the customer returns to a page with an order number. Try opening the feedback message with a screen reader and confirm it can be found. On mobile, check whether the keyboard hides the button or a message that appears just above it.
For a second test, enter both contacts and check how the confirmation names the person who receives each message.

Check the route with the keyboard
Start at the top of the form and use Tab and Shift+Tab to move through it. Track where the focus indicator appears. Try every menu or date selector that needs a choice. The U.S. Department of Justice web accessibility guidance describes keyboard navigation as part of accessible web design.
Then test with a second person. Ask them to place the test order without coaching. When they ask which date format to use or where to correct a field, write down their question. Reuse their wording if it is clearer than your existing instruction. Repeat the same test after changing the form, including the actual submission.
Make a repeatable test order
Save a short test script with one valid order, one deliberately missing input and one correction. Use invented customer details. Put the script next to the form settings so an editor can find it before they change the field order or install a new payment step.
Write the expected outcome for each version. For the bad email, say which error you expect to read. For successful checkout, name the page and confirmation you expect to see. Check that your staff receives the right message or order record as well. That gives people on both sides of the form a specific result to check.
After a design update, repeat the test using the phone keyboard and verify you can still reach the final control.
Access Heroes may earn a commission if you buy a tool we recommend. You pay the tool's maker directly, and we always tell you before you sign up. This article is general information, not legal or tax advice.
Sources
Bring a link to your contact form or checkout. TJ can help you choose where to start your accessibility review.




Comments