Our goal is WCAG 2.1 at level AA. In practice, we write simple HTML, keep headings in order, give each image a text description, attach a visible label to every form field, pick colors with plenty of contrast and let pages reflow on phones and at high zoom. FAQ answers sit open on the page rather than hidden in panels.

Both the cost calculator and the wet-basement checker run fine from a keyboard. If either one won't cooperate, the cost guide and the service pages cover the same material as plain text.

We haven't caught everything. When something blocks you, maybe a link your reader skips or a field you can't fill, report it on the contact form and tell us which page. The page's address plus one line about the barrier gives us enough to begin.

New and updated pages get an accessibility review each time. Missouri law governs this statement.