Our story

A quick accessibility check shouldn't need a sales call.

I'm Johnny Mobley. I started building systems for other people in 2000, when I was 16, and I've been doing it ever since. Along the way I automated most of my own work, and the tools I built for myself became these companies. Each one runs on rules I wrote down, not on paid AI calls, which is why it can cost so little.

Most accessibility problems on a web page are basic: no language set on the page, images without alt text, no main heading, form fields with no label. You can see them in the HTML. I built EnablingHomes to read a page's markup and list exactly those facts, so you know what to fix first.

It checks only what raw HTML can show. It is not a full WCAG audit: color contrast, keyboard order and screen-reader behaviour need a real review. The same site has a home-accessibility checklist for families planning changes to a parent's house, built from plain written rules.

What works today

• Checks any public web page for a language attribute, a viewport tag, image alt text, a main heading and labelled form fields
• Builds a prioritized home-modification checklist (grab bars, ramps, handrails, lighting) from your answers about the home and the person's mobility

What it doesn't do yet

WebAIM's WAVE still does things EnablingHomes doesn't:

• Color-contrast, ARIA and page-structure checks drawn on top of the page.
• A browser extension that checks pages behind a login.
• An API for running checks in bulk from your own code.
• A vetted contractor network. Our referral form is a queue for a person to follow up, not an instant match.

What it costs

WebAIM WAVE's price is from their pricing page as of October 29, 2026. Prices change, so check theirs before you compare.

— Johnny