Accessibility Statement

Seattle Foundation Repair wants this site to be usable by everyone who needs information about a foundation concern, including people using screen readers, keyboard navigation, magnification, or reduced motion settings.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We treat that as an ongoing commitment rather than a completed certification, because content and features change.

What we have implemented

• A skip link to main content as the first focusable element on every page
• Semantic landmarks, header, navigation, main, and footer, on every page
• One H1 per page and a heading hierarchy that does not skip levels
• Visible focus indicators on links, buttons, and form controls
• Full keyboard operation, including the mobile menu, accordions, and the image viewer
• ARIA labelling on navigation regions, icon-only buttons, and menu toggles
• Text alternatives for informative images, and empty alt attributes for decorative ones so screen readers skip them
• Form labels tied to their inputs, with required fields marked in text rather than by colour alone
• Colour contrast checked against WCAG AA for body text and interface components
• Respect for the prefers-reduced-motion setting, which disables transitions and smooth scrolling
• Touch targets sized for comfortable use on mobile devices

Known limitations

• Embedded Google Maps on service-area pages are third-party content we do not control. Each map is accompanied by a text description of the area it shows, so no information is available only inside the map.
• Some illustrative photographs carry descriptive alt text that summarises the scene rather than describing every detail.
• PDF documents we send directly to customers, such as proposals, may not meet the same standard. Ask us and we will provide the content in an accessible format.

Alternative ways to reach us

If any part of this site prevents you from getting in touch, contact us through the contact page and we will respond using whichever method works for you. We can take project details by phone or email rather than through a web form, and we can read a written scope aloud or supply it in a different format on request.

Reporting a barrier

Tell us the page, what you were trying to do, and the assistive technology or browser you were using. Specific reports are far easier to fix than general ones, and we treat accessibility defects the same way we treat any other defect: they get corrected.

Ongoing review

We review accessibility when we add pages or change interactive components, and we update this statement when the position changes. If something here no longer matches what you experience on the site, that is a reporting-worthy discrepancy in itself.