Accessibility statement
Websites everyone can use.
Every site is built and tested so people with disabilities can use it. If anyone finds a problem, it gets fixed.
Last reviewed: October 2026
What that means for your customers.
Some of your customers are blind, have low vision, can't use a mouse, or are color blind. Every site I build is made so they can find your hours, see what you offer, and get in touch like anyone else. It's part of every plan at no extra cost.
Easy to see
Text that is easy to read, colors with enough contrast, and descriptions on meaningful images for people who cannot see them.
Works without a mouse
Every link, button, and form can be reached and used with just a keyboard, and you can always see where you are on the page.
Easy to understand
Clear headings, predictable menus, labeled form fields, and error messages that say what went wrong and how to fix it.
Works with screen readers
Checked by hand with the screen-reader software blind visitors use on computers and phones.
Testing method
Every site is checked with screen-reader software, tested using only a keyboard, and checked for readable text and color contrast before it goes live. I go through it by hand, because a person notices things automatic checks miss.
No check catches everything, which is why the most important promise is the second half: if anyone finds a problem, it gets fixed.
This site.
mosaicridge.com is built and checked the same way as client sites. If something here doesn't work for you, that's a problem, and I'll fix it.
Common questions about accessibility.
What does "accessible" actually mean for my website?
It means people with disabilities can use it: someone who is blind and uses a screen reader, someone who can't use a mouse, someone with low vision or color blindness. In practice: text that's easy to read, colors with enough contrast, every button reachable with a keyboard, clear labels on forms, and descriptions on meaningful images.
Does the ADA apply to my website?
It might. Courts have increasingly said the Americans with Disabilities Act covers websites of businesses open to the public. I build every site with accessibility in mind from the start, but I'm not a lawyer, and this isn't legal advice. If you have a specific concern, a lawyer is the right person to ask.
Is accessibility part of every plan, or only some?
Every plan. A five-page Foothold site and a Summit online store get the same care and the same checks.
How do you check that a site is accessible?
Two ways. Automated checking tools catch the obvious problems. Then I go through the site by hand: with only a keyboard, and with the screen-reader software blind visitors actually use on computers and phones. The hands-on part catches what the tools miss.
My current site has accessibility problems. Can you fix it?
Often, yes. I'll start by checking the site and giving you a plain-English list of what's wrong and what it would take to fix. Sometimes that's a handful of fixes; sometimes a new site is simpler. I'll tell you honestly which, and quote it before doing any work.
Does building an accessible site take longer?
No. It's part of how I build from the first day, not an extra step at the end. Foothold sites still take 2 to 3 weeks, Ridgeline 3 to 4, and Summit 4 to 6.
Does accessibility cost extra?
No. It's included in every plan at the listed price. Doing it right from the start costs far less than fixing it later, so I just build it in.
Report an accessibility issue
Email hello@mosaicridge.com with the page you were on, what you were using (for example, your phone or a screen reader), and what got in the way. I'll get back to you within five business days and fix what I find.
For the technical folks
The details your web developer or IT person might ask about. You don't need any of this to work with me.
Standard: the checklist I build and test against is WCAG 2.1 Level AA. That covers text alternatives, color contrast of at least 4.5:1 for body text and 3:1 for large text, full keyboard operability with visible focus indicators, labeled form controls, a logical heading structure with landmarks, ARIA only where native HTML falls short, and respect for prefers-reduced-motion.
Tools: axe-core and Lighthouse for automated checks, manual keyboard review, and screen-reader walkthroughs with NVDA (Windows) and VoiceOver (macOS and iOS). This is a description of how sites are built and tested, not a legal certification.
Next step
What can I help with?
Start with a free website & Google checkup. I'll look at your site and Google profile and tell you, in plain English, what's working and what isn't. No charge, no pressure.
Get a free checkup