Accessibility Statement
Turn JavaScript off and the form still submits. Report any barrier you hit, and we answer within 48 hours.
This site targets WCAG 2.1 level AA as a floor. Text keeps a contrast ratio of at least 4.5 to 1, and focus stays visible on every control. If a page still blocks you, call us and we take the whole request by phone.
What standard does this site aim for?
The target is WCAG 2.1 level AA, treated as a floor and not as a finish line.
Level AA means you can use the site with a keyboard, a screen reader, or enlarged text.
Accessible pages also read better for search engines and language models. The right thing and the useful thing line up here.
What already works on every page?
The items below are built in and checked page by page before anything ships.
The only script we wrote ourselves handles measurement and form validation. Turn JavaScript off and the form still submits.
- Contrast of at least 4.5 to 1 between text and its background
- A visible focus ring on every link, button and form field
- Every form field tied to a label a screen reader can read
- Heading levels in order, one h1 per page and no level skipped
- Descriptive alt text on content images, and empty alt on decorative ones
- Tap targets of at least 44 by 44 pixels on buttons and mobile links
- Complete HTML served from the server, so the page reads with JavaScript off
- Reduced motion respected, so nothing moves when your system asks for that
- Each page declares its language, English or Spanish, so a screen reader says it right
How does the site behave without JavaScript?
The server sends a complete page. Nothing on it waits for a script to appear.
The estimate form posts the old way, so it works with scripting blocked. Screen readers and text browsers get the same content you get.
There are no carousels, no background video and no animation libraries. A page that loads fast is a page more people can use.
What have we not finished yet?
Several photos are still placeholders. Their alt text is already written for the photo that will replace them.
We have not run an audit with an outside tester who uses a screen reader daily. Automated checks catch part of the problem, never all of it.
If this site ever publishes a PDF, it will carry tagged text instead of a scan. Today there are none.
How do you report a barrier?
Tell us the page, the device you used and what happened. Send it through the contact form or call.
We answer within 48 hours, the same window we hold for written estimates. If the fix is quick, we push it right away.
A report is welcome even when nothing is technically broken. If a page was hard to use, that counts.
What if you cannot use the site at all?
Call. A person takes your name, your city and the work you need, without you opening a page.
The whole estimate can happen by phone and at the visit. Nothing on this site is required to get one.
You can have a family member send the form for you. We talk to whoever you choose, in English or in Spanish.
How do we test these pages?
We walk each page with the keyboard alone, tabbing through every link and field. Focus has to stay visible and the order has to make sense.
We check every color pair against the 4.5 to 1 ratio before it ships. We read the page with styles turned off to confirm the heading order.
Those checks run while the site is built, not after launch. A rule that only gets checked at the end gets skipped.