What's inside
Nothing is "done" until it's been checked on a phone.
After every build, Spanli looks at your site the way a visitor would — at laptop size and at phone size — and runs a list of checks over what it sees. Serious problems on your home page have to be fixed before the build can finish.
You type “A family dental practice in Madison, unhurried appointments, nervous patients welcome” — and Spanli assembles the site in front of you: opening, treatments and fees, the practice, new patient enquiry. The changes receipt reads: Added: 4 sections — opening, treatments and fees, the practice, new patient enquiry.
Sound familiar?
On your laptop it's lovely.
Then someone opens it on a phone: the menu doesn't open, a heading runs off the side of the screen, and the button you cared most about is pale grey text you can't read in daylight. You find out because a friend mentions it — and you wonder how many people just left without saying anything.
Step by step
How it works
In the demo beside each claim: the site Spanli built; then the hygienist, 30 min line being corrected — you click it, type “hygienist is 75”, and $85 becomes $75; then new patient enquiry arriving in the Spanli inbox.
Spanli looks at the real page, not the code
After building or changing your site, it takes actual pictures of your pages at laptop width and at the width of an ordinary phone — a real phone screen size, not a browser window squeezed narrow.
It runs the checks a careful person would run
Anything running off the side of a phone screen. Buttons and links too small to hit with a thumb. Text too pale against its background to read. Words cut off by the box around them. A phone menu that isn't there, or is there and doesn't open. Links that lead nowhere. Pictures with no description for someone using a screen reader. Movement that ignores a visitor's "reduce motion" setting. Colours that wandered off your site's own palette.
It checks against accessibility rules too
The same standard set most organisations work to, run automatically over the pages it captures — so the problems that shut people out get found by a machine, every build, instead of by a complaint.
Honest about what this is: it's a real check, repeated on every build, not a certificate. Some of accessibility can only be judged by a person — whether your wording is clear, whether a photo's description actually describes the photo. Spanli catches the mechanical failures that make up most of the damage, and it catches them before you ship, which is the part nobody else does for you.
Continued
Serious findings on your home page block the finish
This is the part that makes it real: while something serious is open on your home page, the AI is not allowed to call the job done. It has to go back and fix it. That rule is enforced by Spanli, not left to the AI's good intentions.
It doesn't loop forever, and it doesn't hide anything
If something resists a few rounds of fixing, the build ends and tells you what's still off, in plain words. You'd rather know than have it churn quietly.
You can ask any time
"How does the pricing page look on a phone?" is a normal thing to say in chat, and you'll get the same look and the same list back.
Who it's for
The people who can least afford a broken phone layout:
restaurant owners whose visitors are all standing outside deciding where to eat, hair salon owners whose booking link lives on a phone, dental clinics whose patients skew older and won't pinch-zoom to find your number, and nonprofits who have both a duty and an audience that notices.
Make it yours
Before the first build, you set the look.
- Quietly exceptionalElegant & refined
- The story, up frontBold & editorial
- Take a breathSoft & calm
- Built for the nightSleek & dark
- An evening to rememberGlamorous & vintage
- The season, consideredFashion magazine
In case you're wondering.
Does this mean my site is accessible?
It means your site is checked against a standard set of accessibility rules on every build, and that serious findings on your home page had to be fixed before the build could finish. That's a genuine, repeated check — not a certification, and not a promise that every rule is met everywhere. Anyone who tells you a builder makes a site "fully accessible" by itself is selling you something.
Do I have to ask for the checks?
No. They run on every build, whether you asked or not. There's no setting to remember and no button to press.
What phone does it check?
An ordinary phone screen size — the width most people are actually holding — plus a laptop width for comparison. The point is that the narrow layout is a first-class check, not an afterthought someone gets to skip.
Does it check every page?
Your home page carries the hard rule: a serious finding there stops the build being called done. Other pages are checked as they're built and changed, and you can ask for any specific page at any time.
What if I spot something the checks missed?
Point at it and say so. Click the thing in the preview, type what's wrong, and it gets fixed — see point and edit.
Ready to see your website?
Describe your business and watch it come to life. Free to start — no credit card required.