Accessibility statement
Built for everyone who visits.
Last updated October 19, 2026
Our aim
Our own pages and the websites the builder makes aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on phones and on computers.
What we check before every release
- Our main public pages, at phone and computer widths, against the automated WCAG 2.2 AA rules, with no sideways scrolling and every button and link at least 24 pixels.
- The steps people take with us: building a free draft, buying, editing, publishing and reading messages, checked for serious accessibility problems.
- Every design the builder offers: text and button colors meet AA contrast, and buttons are at least 44 pixels tall.
- Complete example websites, on phones and computers, checked with the same automated rules.
Latest results
- On October 19, 2026 we scanned 29 pages and page states (including the free preview, the design collection and the editor demo) at phone width (390 pixels) and computer width (1,280 pixels): 58 scans with axe-core 4.13 (WCAG 2.0, 2.1 and 2.2, levels A and AA) in Chromium 141. They found no violations.
- On every page the scanner could not decide the contrast of some text placed over photos or color blends, and marked it for a person to check. We have not checked every one of those by hand yet.
- The same day, keyboard-only tests passed: the first Tab reaches “Skip to main content”, every stop on the way to the homepage’s main button shows a visible outline, a free preview can be made with the keyboard alone, and the editor demo can be reset and edited by keyboard.
Not tested yet
We have not yet tested with screen readers (VoiceOver, NVDA, TalkBack), in Safari or Firefox, on real phones, or at 400% zoom, and no outside accessibility audit has been done. Until then we do not claim that every page meets WCAG 2.2 AA.
Built in
- Our pages work with a keyboard, with a visible outline on whatever you are on.
- Motion follows your device’s reduced-motion setting, and the moving example on the homepage has a Pause button.
- The editor asks you to describe your main photo, so people who use screen readers hear what it shows.
What automated checks cannot catch
Automated checks find many problems but not all of them, and a website owner’s own words and photos are theirs to choose. If you add photos, describe them. If something on our pages or on a website we built is hard to use, we want to know.
Tell us about a problem
Email support@simpleasite.com or use our contact page. Say which page and what happened. Our support team replies within one business day.