# Form labels and instructions Shopify shoppers can follow Source: https://storefrontaccess.com/blog/2026-10-19-shopify-form-labels-instructions-accessible.html Reviewed October 19, 2026 Unlabeled fields, placeholder only forms, and instructions that vanish are quiet conversion killers with accessibility consequences. A practical guide to labels, hints, and required field marking on Shopify forms. ## Labels are the form's user interface Every input needs a persistent, programmatically connected label that names its purpose. Placeholder text is not a label: it vanishes the moment typing starts, often fails contrast requirements, and leaves the shopper who returns to correct an error staring at anonymous boxes. Screen reader users get placeholders announced inconsistently at best, which makes placeholder only forms a lottery. This applies across the store: newsletter signup, contact form, account registration, gift card balance checks, and the form fields apps inject. Checkout itself is platform controlled, which makes the forms you do control the place where your store either respects the pattern shoppers learned at checkout or confuses them with improvisation. ## Instructions belong before the field, in text Format requirements, a phone number's expected pattern, a password's rules, the date format for a delivery picker, must appear as text before or beside the field, connected to it so screen readers announce them together. Instructions delivered only after an error are a punishment system: the shopper did everything asked and still failed a hidden test. Keep instructions short and concrete. Passwords need a rule list users can check while typing, not a riddle revealed one error at a time. If a field is optional in a sea of required ones, or required among optional ones, say so in the label text itself, because color and asterisks alone do not survive every way of reading a page. ## Required marking and error language Asterisks are a convention, not a communication. Pair the symbol with a note at the form's top explaining it, and include the word required in the accessible name of each required field. Better still, mark optional fields as optional when they are the minority, which modern usability guidance favors because it removes guessing entirely. Error messages should name the field, state the problem, and suggest the fix in plain words: enter a ten digit phone number, not invalid input. Focus should move to an error summary after a failed submission, with links to each problem field, and everything the shopper entered correctly must survive the round trip. Re typing a whole form is an accessibility failure wearing a usability costume. ## Auditing forms you did not build Apps add forms constantly: reviews, wishlists, loyalty, quizzes, back in stock alerts. Each arrives with its own label quality, and your store's accessibility is the sum of the worst of them. Inventory every form on the site, including the ones in popups and slide out panels, and run each with a keyboard and with labels hidden from your own sighted habits. Fix order matters. Prioritize forms tied to revenue and accounts first, then contact and signup forms, then the long tail. Where an app's form cannot be fixed by settings or light code, that is a legitimate reason to replace the app; vendors respond to churn reasons, and form accessibility improves across the market when merchants name it as one. ## Related reading If this topic is useful, these earlier guides go deeper on connected questions: [Checkout error messages shoppers can actually act on](https://storefrontaccess.com/blog/2026-10-18-shopify-checkout-error-messages-accessibility.md), [Gift card flows that work for every shopper](https://storefrontaccess.com/blog/2026-10-18-accessible-shopify-gift-card-flows.md), and [Making your Shopify store locator and map accessible](https://storefrontaccess.com/blog/2026-10-17-shopify-store-locator-map-accessibility.md). ## Frequently asked questions ### Is a floating label pattern accessible? It can be, if a real label element remains programmatically attached, stays visible or recoverable once the field is filled, and meets contrast in both positions. Many implementations fail on the second point: once typing starts, the label shrinks into low contrast micro text. Test the filled and error states, not just the pretty empty form in the demo. ### Why not rely on autocomplete instead of labels? Autocomplete attributes are valuable and should be set correctly for name, email, address, and payment adjacent fields, since they power autofill that helps everyone, including shoppers with memory or motor difficulties. They complement labels rather than replacing them, because the shopper still needs to verify what each filled field claims to be. ### How do I test form labels quickly? Click each visible label: focus should jump into its field. Then tab through the form watching whether every field announces a clear name, and submit it empty to read the error experience. Finally, fill it using only autofill and check each value landed in the right place. Fifteen minutes reveals most label defects. ### Should optional fields just be removed instead? Often, yes. The most accessible field is the one the form does not ask for. Every optional field still costs labeling, testing, and shopper attention. If marketing wants the data, weigh it honestly against completion rates. Shorter forms with perfect labels beat long forms with perfect labels, and both beat the forms most stores actually ship.