Storefront page
One page for your links, menu and prices. Visitors add items, see the total and pay you in Venmo, Cash App, PayPal or Zelle.
Learn more about Storefront pageLaunch offer7 days of Pro, freeClaim it
UtilicaFeaturesAccessibility
Accessibility shouldn't be something a small shop learns about from a demand letter. Utilica builds the basics in from the first page you make: words for every photo, colors people can read, a site that works with a keyboard, and a check that scores your store before it goes live. It's how to lower your ADA lawsuit risk without an overlay widget or a promise nobody can keep.
A photo in the editor with its description and a Suggest a description button; a hard-to-read color with a Fix contrast button; and the check before publishing, scoring the site 94 out of 100.
The problem
And the same handful of problems turn up again and again. That's what makes them easy to fix, and easy to be sued over.
WebAIM tests the home pages of the top million websites every year. Almost every error it finds is one of these six.[1] They're also the first things Utilica takes care of.
Why small shops get targeted
What Utilica does by default
Nothing to install and nothing to switch on. Every store and website made with Utilica gets all of this, on every plan.
Every photo you add to your store or website asks for a short description, with a Suggest a description button that writes a first one from the photo. A photo that only sets the mood can be marked decorative instead.
Choose a text or button color that's hard to read and the editor says so right under the picker, against the WCAG AA ratios (4.5:1 for text, 3:1 for large text and buttons), with a one-click Fix contrast.
The check before publishing scores your website out of 100 and lists what to fix: photos with no description, buttons and links with no words, hard-to-read colors, pages with no headings. If something must be fixed, Publish shows it to you first.
Buttons and links are real buttons and links, so the Tab key reaches each one, with a clear outline showing where you are. Websites start with a Skip to content link.
Checkout, booking, sign-up and contact forms have a label tied to each field, so a screen reader says what goes where, and the label stays put while people type.
Each page tells browsers and screen readers what it's called and what language it's in, so the right voice reads it.
Pages never switch off pinch to zoom, and the layout still works when someone makes the text twice as big.
Animations and scrolling text stop for people who've asked their device for less motion.
Each store has a statement at /accessibility, linked from its footer: how it's built to work, where it may fall short, and how to reach you. A website can add a note of its own.
Utilica doesn't put an accessibility toolbar or overlay script on your store. The page itself is built to work, so the screen readers, zoom and settings people already use work with it.
Free store scan
Type a Utilica store's name or link, or any website's address. You get a score out of 100 and a list of what to fix, in plain words.
What you still do
A store is only as accessible as what's on it. A product photo full of text with no description shuts people out however well the page around it is built. These take minutes, and the editor reminds you.
Say what matters in a few words: “Iced oat latte in a tall glass”, not “IMG_2041”. The suggestion is a start; you know what the photo is for.
A menu, a flyer or a price list as a photo can't be read out or zoomed. Type it as text, and use the photo as decoration.
If people talk in a video, turn on captions where it's hosted. YouTube and Vimeo can make a first draft for you to correct.
“See the full menu” beats “Click here”. A button's words should make sense on their own.
Custom code, embedded widgets and PDFs you link to aren't Utilica's to check. Ask whoever made them how they work with a keyboard and a screen reader.
Your accessibility page gives people your email. If someone can't finish an order or a booking, help them finish it, then fix what got in the way.
Honest answers
Read how Utilica itself is built in our accessibility statement. Something not working? Write to support@utilica.app.
No, but it removes the most common things plaintiffs look for. Six kinds of problem make up almost all the errors automatic tests find on websites, and Utilica either prevents them or points them out before you publish. Nothing anyone sells can promise you won't be sued: what's on your store (your photos, words and videos) matters too, and the law is decided by courts, not by software.
No. An overlay is a script that sits on top of a site and promises to make it accessible. It doesn't change the page underneath, it often gets in the way of the screen readers and settings people already use, and lawsuits keep naming sites that have one. In 2025 the FTC made one overlay company, accessiBe, pay $1 million over claims that its tool could make any website meet WCAG. Utilica builds the page itself to work instead.
We don't use those words, because no software can honestly promise them. The ADA doesn't name a technical standard for private businesses' websites; WCAG 2.1 AA is the one most often pointed to, and the one the Department of Justice adopted in 2024 for state and local government websites. Utilica is built to WCAG 2.1 AA standards, and the check before publishing helps your own content meet them too.
WCAG 2.1 AA is the target every part of a Utilica store is designed and checked against: contrast, names on controls, labels, headings, keyboard use, zoom and motion. Every website template is checked with automated tools, in light and dark, and tried with a keyboard. It isn't a certification: your own photos, words and anything you paste in count too, which is why the editor asks about them.
Photos with no description, hard-to-read colors, links and buttons with no words, form fields with no label, a missing page title or language, headings that skip levels, zoom switched off, a missing accessibility statement, and overlay widgets. For a Utilica store it reads the store itself; for any other website it reads the page as the server sends it.
No automatic check can. It can tell that a photo has a description, not whether the description is any good, and it can't try your checkout with a screen reader the way a person would. Use it to catch the common problems, then try your site with a keyboard and a screen reader, or ask someone who uses one every day.
No. Photo descriptions, contrast warnings, the check and score, the accessibility page and the free scan are on every plan, including Free. The only difference is how many suggested descriptions you get a day: 15 on Free, 150 on Pro and 400 on Business.
Talk to a lawyer before you answer it: we're not lawyers, and this page isn't legal advice. Meanwhile, scan your store, fix what it finds, and keep a note of what you changed and when. If something on Utilica itself got in the way, write to support@utilica.app.
This page explains how Utilica works. It isn't legal advice; for advice about your own business, talk to a lawyer.
One page for your links, menu and prices. Visitors add items, see the total and pay you in Venmo, Cash App, PayPal or Zelle.
Learn more about Storefront pageCustomers pay you in Cash App, Venmo, PayPal or Zelle with the total already filled in, or by card. Every order is added up, numbered and tracked for you.
Learn more about PaymentsAsk one question at a time or all on one page. Change every color, font, corner and background, add logic, and take payment at the end.
Learn more about FormsAccessible by default
Start a store that's built to WCAG 2.1 AA standards, with the checks that keep it that way. Free to start, no card.