Make Your Website Easier for More People to Use.
About one in six people worldwide lives with a significant disability. Readable text, keyboard access, and clear navigation help more visitors use your site.
The data behind "nice to have."
How We Build for Accessibility.
Accessibility involves design, development, content, and ongoing testing. These are the three areas we address in our work.
Built to standard, at the source
We target WCAG 2.1 Level AA through semantic markup, readable contrast, keyboard navigation, and visible focus indicators. We test those features and revisit them when the site changes.
Honest about limits
No vendor — including us — can promise an injected script will "make any site accessible." We say what our tools do, and what they don't. When a site has structural issues, we fix the site, not the symptoms.
User control, on every page
Visitors get a built-in panel for adjustable text size, contrast, motion, and reading aids. Their choices persist across pages. That panel — UserPrefs — runs on every site we maintain at no additional cost.
Why we replaced our SaaS overlay with something we built.
For years, the studio paid a monthly subscription to a SaaS accessibility overlay. The marketing claim — "AI fixes any site automatically" — has been challenged repeatedly by accessibility experts and disability-rights organizations. In April 2025, the U.S. Federal Trade Commission fined the leading overlay vendor $1 million for deceptive claims that its AI could make websites WCAG-compliant, and barred it from making such claims going forward. In practice, overlay-driven alt-text is often wrong, overlay-driven ARIA can collide with legitimate ARIA, and overlay-using sites are still named defendants in ADA lawsuits — having an overlay installed does not, on its own, stop a complaint from being filed.
"Accessibility overlays do not, and cannot, fix the underlying accessibility issues of a site. They simply hide them."Joint statement, signed by 600+ accessibility advocates
So we did the work. We built our own user-facing accessibility widget — UserPrefs — that handles the legitimate layer of overlay tooling: adjustable text, contrast, motion, reading aids. UserPrefs gives visitors display and reading controls. Structural accessibility issues still need to be corrected in the site itself.
The widget we built — and gave to every client.
Self-hosted. Single script tag. Roughly 17 KB on the wire. Every site under Wandzilak management runs UserPrefs at no extra cost. Click the bubble in the lower corner of this page to try it.
- 7 user profiles
- Font & contrast controls
- Reading guide & mask
- Stop-animations toggle
- Big-cursor option
- Keyboard-only mode
- 27 language slots
- Persists across pages
What clients usually ask.
Is wandzilakwebdesign.com itself WCAG 2.1 AA conformant?
Yes. As of May 2026, this site has been evaluated against and conforms to WCAG 2.1 Level AA, with documented exceptions for third-party content delivered by the hosting platform's edge security layer. The site is re-evaluated annually; the next review is scheduled for May 2027.
What standard do you build to?
WCAG 2.1 Level AA — the standard referenced by the U.S. Department of Justice, the ADA, the European Accessibility Act, and most enforcement actions. Sites we build are intended to meet AA conformance through markup, contrast, focus, and keyboard structure — not through an injected overlay.
Do you use AccessiBe or similar overlays?
No. We replaced our SaaS overlay with the self-hosted UserPrefs widget we built ourselves. UserPrefs handles the user-facing layer; the underlying site is built right at the source. We do not pretend an injected script can substitute for accessible markup.
Is UserPrefs available on every site you've built?
Yes — at no cost to the client, on any site under our maintenance. The widget is licensed for use on Wandzilak Studio properties and the client sites we host. It loads from a single domain, weighs about 17 KB after gzip, and respects user preferences via localStorage.
What if I have an accessibility complaint about a Wandzilak-built site?
Email mike@wandzilakwebdesign.com with the specific page and the issue. We respond to reported accessibility issues, usually within one business day. We do not gate accessibility behind a form or a SaaS vendor.
Contact us to discuss an accessibility review or improvements to your site.
Start a conversation Read our philosophy