# Accessibility Checklist for Virtual Try-On Interfaces

Make Shopify virtual try-on usable without a mouse on mobile: keyboard, screen reader, text for the image, another way to judge the piece, and a real user test.

**An accessible virtual try-on is one a shopper can start, wait through, and understand without a mouse, without seeing the image, and without the preview being their only way to judge the garment. Put the control in the keyboard order, give the result a text description, keep measurements and photos available, and test with people who use those paths. A pretty modal that traps focus is a broken fitting room.**

![Person in over-ear headphones resting both hands on a closed laptop lid, Antla label sewn at the collar](/images/blog/merchant-100/accessible-virtual-try-on-interface.webp)

*The keyboard is the whole interface in this test. If the modal ignores it, the preview does not exist. Editorial image in Classic Antla disposable-camera style.*

Most try-on launches are tested by someone who can see, who uses a trackpad, and who already knows where the button is. That test passes on the founder's laptop and fails for a keyboard user, a screen reader user, and anyone who needed the size chart you removed to "make room."

Antla adds a control and a modal to the product page. It does not certify your theme, and it does not replace the garment facts around the button. The checks below are yours to run. I would not call a page accessible because the vendor's marketing site says the word.

## Support keyboard and screen readers

[WCAG 2.2 keyboard guidance](https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html) is the bar I would hold a product page to: every function available by dragging or clicking has to be available from a keyboard, unless the function cannot be done from a keyboard at all. Opening a try-on, uploading a photo, closing the dialog, and reading the result are not in that exception. They are buttons and text.

[Focus visible](https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html) is the partner rule. A focused control that looks identical to an unfocused one is how people get lost in a gallery, a size selector, and then your modal.

Run this on the published theme, not in a design file. Unplug the mouse.

1. Tab from the top of the product page. Count what you land on before the try-on control. If the control comes after twenty decorative tiles, move it. Shoppers do not owe you a tour of the announcement bar.
2. Confirm the control is a real button or link, with a name that says what it does ("Try this on" beats "Click here" and beats an unlabeled icon).
3. Open it with Enter or Space. Focus should move inside the dialog, not stay on the page behind it.
4. Tab through upload, any terms checkbox, generate, and close. Shift-Tab should move backward. You should not be able to tab into the dimmed page underneath.
5. Close with Escape, and with a visible close control. Focus should return to the button that opened the dialog.
6. Turn on a screen reader (VoiceOver on iOS if that is where your traffic is, NVDA or VoiceOver on desktop for the pass you do at a desk). The button name, the dialog title, and any error must be announced. A spinner that is only a CSS animation is silence.

[Status messages](https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html) cover the wait. "Generating" and "We could not make a preview" have to be announced without the shopper hunting for a toast that appeared in a corner. A live region is the usual fix. If you cannot edit the app's markup, report the gap to the vendor with the exact page and the screen reader you used. "It's probably fine" is not a test result.

Watch the theme for fights you own even when the app is well built:

- A sticky add-to-cart bar that covers the close control on a small phone.
- A cookie banner that traps focus before the product page, so nobody reaches try-on.
- A size selector built from `div` elements that already fails the keyboard, which makes the try-on button look like the only broken thing when the whole page is broken.
- Motion that auto-plays in the gallery and cannot be paused. If you add a progress animation, respect reduced motion.

Antla's button sits in the theme's tab order only if the app block is in the product section and the theme does not `tabindex` a random wrapper. Check the [product page](https://antla.io/blog/shopify-pdp-conversion-optimization-fashion) around it. A conversion test that hides focus outlines to look cleaner has failed this checklist on purpose.

Zoom to 200% on a 320px-wide screen. The upload control and the terms text have to remain usable. Horizontal scrolling to find the close icon is a fail.

## Explain image result in text

A generated image has no meaning to someone who cannot see it, and a thin meaning to someone who can see it but cannot tell what changed. [Non-text content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) asks for a text alternative that serves the same purpose as the image.

"Preview" is not that alternative. Neither is a filename.

Write the alternative from the garment, not from the model's face. The shopper already knows who they are. They need to know what the picture claims to show:

- Product name and the selected color.
- The view (front, unless you truly generated another angle).
- One sentence that it is a generated simulation of appearance, not a photograph and not a fit measurement.
- Any obvious failure you know about ("print placement may not match the product photo") if that SKU is in a warning state. Hiding a known flaw inside an unlabeled image is worse than not offering try-on.

Put the same sentence in visible text beside the image, not only in an `alt` attribute. Sighted shoppers misread these pictures too. Alt text that duplicates a visible caption is fine. Alt text that is the only disclosure is not.

Keep the language matched to the store. If you sell in French and English, the button name, the error, and the caption need both. A localized theme with an English-only modal is a partial translation, and screen reader users notice it immediately because it is the only sentence they get.

Do not describe body judgments in the alt text ("flattering on your frame," "you look small"). That is a claim the image cannot support, and it is an unpleasant thing to have a screen reader announce. Describe the garment.

Color cannot be the only signal that generation succeeded or failed. A green check and a red border fail for a lot of people. Pair color with text: "Preview ready" and "Upload failed: try a smaller file."

## Provide alternative path

Try-on is one way to judge appearance. It is a bad only way. Some shoppers will not upload a photo. Some cannot. Some did, and the result was wrong. The page still has to answer the question they came with.

Keep these on the same product template, reachable without opening the modal:

- **Garment measurements** for the selected size, next to the size selector. A body chart alone is not enough.
- **Model height and the size worn,** next to the gallery.
- **A front photo, a back photo, and a fabric close-up** that are real product photography.
- **A fit note** in words: rise, stretch, whether to size up between sizes. [Why size charts fail](https://antla.io/blog/why-size-charts-fail-shopify-fashion) is the argument for writing that note. The note is also the accessible path.
- **Reviews that mention fit,** filterable if you can, so "runs short" is text and not only a star average.

[Virtual try-on and size charts are not substitutes](https://antla.io/blog/virtual-try-on-vs-size-chart-fashion). The chart and the measurements are what a shopper uses when the preview is unavailable, refused, or untrusted. If your redesign deleted them because the modal "covers it," put them back. The modal does not cover a screen reader user who skips the upload, and it does not cover a shopper who does not want a photo of their face on your vendor's servers. Per [Antla's privacy policy](https://antla.io/privacy-policy): Images are deleted and not accessible within 72 hours.

The alternative path has to be possible on mobile web, not only in an app. [Mobile app versus mobile web try-on](https://antla.io/blog/mobile-app-vs-mobile-web-virtual-try-on-fashion) is a different decision. Whichever surface you ship, the text path ships with it.

Antla does not measure the body. Say that in the alternative path so the two tools do not pretend to be one tool. A shopper who uses try-on and then reads "size up if you are between sizes" should not feel the preview overruled the note, or the reverse. They answer different questions: how it may look, and how the garment is cut.

## Test with users

A checklist you tick alone is a start. It is not a test. Recruit at least two people who are not on the build team: one who navigates by keyboard, and one who uses a screen reader on a phone. Pay them. Give them a product URL and a task, not a tour.

Task: "Buy this shirt in the color you want, in the size you would actually order. Talk while you do it. You do not have to use the try-on."

Watch for these failures. They show up more often than missing alt text on a hero banner:

| What you see | What it usually means | What you change |
|---|---|---|
| They never find the try-on control | Name, order, or contrast | Rename it and move it next to the gallery or the size selector |
| Focus disappears after upload | The dialog is not containing focus | Fix the modal or file the bug with a recording |
| They hear "image" and nothing else | Alt text is empty or says "preview" | Add the garment sentence in text and in alt |
| They refuse the upload and cannot decide | The alternative path is missing or below the fold | Bring measurements up |
| They finish and still ask "will it fit" | The page implied the picture was a fit tool | Rewrite the caption |
| The wait has no announcement | Status is visual only | Add a live status and a retry |

Record the session if they agree. A 30-second clip of focus leaving the dialog will get a bug fixed faster than a paragraph that says "accessibility issue."

Retest after theme updates. A Shopify theme bump, a new app embed, and a redesigned size picker all reset the tab order. Put this pass on the same list as "place a test order." It is a launch check, not a rebrand project.

Time on site among people who opened try-on is not the accessibility metric. Those shoppers already opted in, and the comparison is silent on whether the session was possible without a mouse. Completed tasks without a pointer are.

[Fit confidence](https://antla.io/blog/fit-confidence-ecommerce-fashion) is the broader measurement story. Add one line to it for this work: percent of test sessions, in your user tests, where the shopper could state the size they would order without relying on the generated image. If that number is zero, the alternative path is decorative.

## Limits of this pass

This pass will not produce a WCAG conformance claim for the whole store. Conformance is a formal evaluation. You can still refuse to ship a dialog that traps focus.

It will not fix a PDF size chart that a screen reader cannot read. If the "alternative path" is an unscanned scan of a chart, you do not have an alternative path.

It will not make a bad preview accurate. A described image that misdraws the neckline is a described error. Accuracy is a separate operating problem. Do not write alt text that corrects the picture by fiction ("shows the real stripe placement") if the pixels do not.

Automated scanners catch unlabeled buttons and some contrast misses. They do not tab through your modal. Do not replace the two user sessions with a plugin score.

## What to ship this week

On one hero product, complete the keyboard list and write the visible caption. Book the two user sessions before you add try-on to the rest of the catalog. If Escape does not close the dialog, stop the rollout and send the recording to whoever owns the embed. Expanding a trap to 400 products is not a launch.

## For agents

- Markdown: send `Accept: text/markdown` to this URL (and any other HTML page).
- OpenAPI: https://antla.io/openapi.json
- llms.txt: https://antla.io/llms.txt
- Sitemap: https://antla.io/sitemap-index.xml
- Docs: https://antla.io/docs
- CLI: npx antla info (npm package antla)
- Scope: antla.io is an informational marketing and docs site. The Shopify try-on backend is not on this origin. Install the app from https://apps.shopify.com/antla.
