Accessibility Statement

The standard we work to

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. WCAG is the standard referenced by the Americans with Disabilities Act guidance and by most state procurement rules, and it is organized around four principles: content should be perceivable, operable, understandable, and robust enough to work with assistive technology.

Level AA is the conformance level ordinarily expected of a public-facing commercial website. It is a target rather than a certification: no automated tool can confirm conformance on its own, and we do not claim more than we have tested.

How we test

We run an automated accessibility audit across every page template on the site — service pages, blog articles, service-area pages, the answers hub, legal pages, the contact form, and the sign-in and unsubscribe screens — using axe-core, the same rule engine built into most browser accessibility extensions. The most recent pass reported zero violations across all tested templates.

Automated testing catches roughly a third to a half of real barriers, so it is a floor rather than a finish line. We supplement it in two ways. Color contrast on our photographic page headers is measured from rendered pixels rather than from stylesheet values, because text over a photograph behind a semi-transparent overlay produces a composited color that no static analysis can read. And keyboard behavior — the skip link, focus order, and whether focus actually lands where the page says it does — is checked by operating the site with a keyboard rather than by inspecting the markup.

Measures we have taken

• A skip link as the first focusable element on every page, so keyboard and screen-reader users can bypass the navigation and land in the main content.
• Semantic HTML throughout, with landmark regions and uniquely labeled navigation elements so assistive technology can distinguish the header, footer, and in-page navigation.
• Descriptive alternative text on every meaningful image, and empty alt attributes on decorative imagery so screen readers skip it rather than announcing a filename.
• Body and interface text that meets or exceeds the 4.5:1 contrast minimum, and header text over photography that has been measured in place rather than assumed.
• Visible focus indicators on every interactive element, including elements that only receive focus programmatically.
• Form controls bound to visible labels, so the label is announced with the field and clicking the label moves focus into it.
• Support for the operating system's reduced-motion setting, which turns off the site's entrance animations.
• Layouts that reflow without horizontal scrolling at the phone, tablet, and desktop widths we test at, down to a 360-pixel viewport.

Known limitations

We would rather name these than leave you to discover them. Both are open items on our list.

• On narrow phone screens the menu button is slightly smaller than the 44-by-44-pixel target size we aim for, which can make it harder to hit accurately.
• The category label on blog listing cards renders below our intended minimum text size. It repeats information available in the article heading, so no content is lost, but it is small.

Third-party content

This site is built and hosted by us and does not embed third-party widgets, chat tools, or advertising frames, so there is no vendor component whose accessibility we cannot control. Links that leave our site are marked as such in context; we cannot control the accessibility of the destination.

Ongoing effort

Accessibility is an ongoing process rather than a one-time project. We re-run the automated audit whenever page templates change, and we review this statement alongside it. Feedback from people using the site is more valuable than any tool, and we act on it.

Contact us and how we respond

If you encounter an accessibility barrier on this website, please call us at (406) 493-8300 and describe what you were trying to do and where it went wrong. If you tell us which browser, device, or assistive technology you were using, that helps us reproduce it, but it is not required.

We treat accessibility reports as we treat any other request that reaches us: a person reads it and gets back to you. If a fix will take time, we will say so rather than leave you waiting, and there is always another route to what you needed — every service on this site can be arranged over the phone, including free estimates, scheduling, and emergency storm response.