Can shoppers use your Shopify survey without seeing the screen?

A beauty store asks “How was your checkout?” and offers five faces ranging from a frown to a grin. To the person who designed the poll, the order seems obvious. A buyer hearing “button, button, button” has five controls and no way to tell the store what happened. Their missing answer is easy to mistake for disinterest in a weekly report.

You can catch defects like this on a Shopify thank-you page without editing checkout code. Use a test order, the keyboard you already own and a screen reader familiar to someone on your team. If possible, include a shopper who regularly uses assistive technology. They may navigate very differently from a sighted colleague hearing a screen reader for the first time.

Give the question and each answer a readable name

Try the example again as “How easy was it to place your order?” Use “Very easy,” “Somewhat easy,” “Neither easy nor difficult,” “Somewhat difficult” and “Very difficult.” A follow-up for either difficult answer could ask “What made checkout difficult?” Mention whether writing an answer is optional. Avoid wording that makes answering sound like a condition of confirming the purchase.

In the browser, listen first to the question and then move directly between choices. Can the listener tell which question the options belong to? Can they hear the label, the type of control and whether their choice is selected? W3C describes how form controls acquire names and how related options can share a question. These are useful references when a developer needs to reproduce a problem. W3C on labeling controls and grouping related controls.

Run the path in both directions

1. Starting above the poll, move through the confirmation by keyboard. Check that the current control is visibly identifiable and that you can proceed to order details without answering.
2. Navigate the choices using the controls' expected keys. Select an answer, change your mind and select another. Verify which option is announced as selected and which answer reaches the dashboard.
3. Trigger the optional follow-up. Listen for its question, enter a short answer and submit. Can the shopper tell their response was received after the page changes?
4. Repeat with the follow-up skipped. Move forward and backward through nearby order links. Record any point where focus disappears, jumps somewhere unexpected or gets stuck.

For the physical experience on a narrow screen, run the separate one-handed mobile audit. Someone may be able to tap a visible label easily while a keyboard user cannot tell where focus went.

Write a report another person can reproduce

Suppose a keyboard tester chooses “Somewhat difficult,” and the next press takes them straight to “Send” while a new text field appears higher on the page. Capture the browser, operating system, assistive technology, survey version, page and exact keystrokes. State the shopper's task and what they heard. For example, “The next announcement was ‘Send, button.’ I discovered the follow-up only after tabbing backward.” Share a test configuration or a cropped recording with customer details removed.

A merchant can change unclear choices today. The app provider may need to address a control's announced name or the order in which focus moves. After a fix, repeat the original task and check a second answer path, including the option that bypasses the follow-up. These checks cover one poll in one configuration. A broader accessibility review includes other pages, input methods and shoppers.

To try the exercise with a real survey block, add OrderSurvey from the Shopify App Store. The thank-you page setup guide covers placement so the tester can start from a complete receipt.

Frequently asked questions