Accessibility Statement

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the most widely used standard for accessible websites, and version 2.2 Level AA includes everything in the earlier version 2.1 Level AA. We know some parts of the site don't meet this standard yet. They're listed under "Known problems" below.

• Menus, pop-ups, forms and buttons that work with assistive technology. We build them so screen readers and other assistive technology announce them correctly. Form errors are shown in words, not just by color.
• Keyboard support. You can use the main menu, the mobile menu and our pop-up notices with a keyboard. Pressing Escape closes the main menu and puts you back on the menu button. Links and buttons show a visible outline when you reach them with the keyboard, except in the places listed under "Known problems".
• A "Skip to content" link on our main pages, so keyboard and screen reader users can jump past the menu.
• Reduced motion. If your device is set to reduce motion, we turn off our animations. The scrolling partner strip on the home page also has its own Pause button.
• Bigger buttons on phones. Our main buttons are at least 44 pixels tall on phones, so they're easier to tap.
• Layouts for every screen size. Pages adjust to phone, tablet and desktop screens. Our tests check a sample of pages at each of those sizes to make sure they don't scroll sideways.
• Videos play only when you choose. Our video players show a still image with a play button first, so nothing starts playing on its own.
• An emergency notice that always shows. On our Respond page for homeowners, the "call 911" notice is part of the page itself, so you'll see it even if the pop-up version doesn't work for you.
• Automated testing. We run automated accessibility tests whenever we change the site's code. They check a sample of about 30 pages, including the home page, section pages, articles, tools, contractor pages, video episode pages and the sign-up, sign-in and password reset pages, at phone, tablet and desktop screen sizes. The tests check against the WCAG 2.0 and 2.1 Level A and AA rules. If they find a serious problem, we fix it.

We'd rather tell you about these than have you find them by surprise.

• Some buttons and labels are hard to read. Some of our orange and blue buttons, labels and headings don't have enough difference between the text color and the background color to meet the WCAG minimum for regular-sized text. If you have trouble reading any of them, contact us and we'll get you the information another way.
• Small slide dots in one carousel. The dots that move between slides in the "Start here" carousel on our homeowners page are smaller than the WCAG 2.2 minimum target size, so they can be hard to tap. They're also the only way to change slides. If you can't reach a slide, contact us and we'll send you what's on it.
• No "Skip to content" link on account pages. Our staff sign-in and password reset pages don't have one yet. These pages have short menus, but we plan to add it.
• New and edited content isn't tested automatically. Our automated tests check the site's code using a fixed set of sample pages. When our team adds or edits pages, text or images, those changes aren't checked automatically.
• Automated testing has limits. Automated tools find many problems, but not all of them. Our tests run in one browser engine (Chromium, which Google Chrome is built on), and they don't yet check the rules that are new in WCAG 2.2. We haven't yet done a full manual review with screen readers.

Some things we link to or show come from other companies, and we can't control how accessible they are. These include:

• the YouTube video player, which loads when you choose to watch a video
• the Apple App Store and Google Play pages for our mobile apps
• our podcast feed
• partner and government websites we link to, and our social media pages
• stores that sell our book

If one of these gets in your way, tell us. We'll try to give you the same information another way.

The site is built to work in current versions of the main web browsers on computers, tablets and phones. It's also built to work with screen readers, screen magnifiers, voice control and keyboard-only use.

Our automated tests run in Chromium, the engine behind Google Chrome, and we haven't tested every combination of browser and assistive technology yet. If something doesn't work with your setup, tell us what you're using.

If you can't use part of this site, or something is hard to use, please contact us:

• Email: info@buildsos.com
• Mail: BuildSOS Inc., 21212 Smith Road, Covington, LA 70435

It helps if you tell us the page address, what you were trying to do, and the device, browser and any assistive technology you were using. You don't have to give us all of that to get help. Our Privacy Policy explains how we handle what you send us.

We aim to reply within 10 business days. If we can't fix the problem right away, we'll tell you what we plan to do. In the meantime, we'll help you get the information or finish the task another way.

If you need information from this site in another format, such as large print or plain text, contact us using the details above and we'll work with you to provide it.

• We run our automated accessibility tests every time we change the site's code, not just once.
• We fix problems people report to us. Any we can't fix yet, we list on this page.
• We review this statement at least once a year, and whenever we make a significant change to the site.

This statement was last reviewed on November 13, 2026. It's based on our own checks and automated testing, not on an independent audit.