Accessibility statement.

Inspect Solutions is committed to digital accessibility. The marketing site at inspectsolutions.com is built to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level — the same standard used as the federal floor under Section 508 and adopted in most state and international procurement frameworks.

Accessibility is not a one-time project. Conformance is the baseline; ongoing testing, content review, and code-level fixes carry it forward as the site grows.

The client portal — used by carriers and manufacturers to file inspection assignments and retrieve reports — is on a separate track. Portal-side WCAG conformance is being confirmed for v1 and will be documented separately.Pending — to be confirmed

In building the v1 marketing site, our engineering and design teams shipped the following accessibility-first work:

• Skip-to-content link. Keyboard users can bypass the navigation and jump straight to the page content.
• Keyboard navigation. Every interactive element is reachable and operable with a keyboard alone — no mouse-only paths.
• Visible focus indicators. A 3-pixel navy ring with offset is rendered around every focused element. The ring uses outline + offset rather than shadow so it is not suppressed by parent overflow rules.
• Semantic HTML. Headings progress in order, lists use list elements, navigation regions are landmarked, and ARIA attributes are used only where native semantics fall short.
• Contrast-audited tokens. The full color token set has been audited for WCAG AA contrast on text, AA Large on UI components, and 3:1 non-text contrast on form inputs and interactive controls. Decorative-only tokens are documented as such and never used for text.
• Reduced motion. Hero animations and transitions respect the user's prefers-reduced-motion setting. When the user has reduced motion enabled, animations either do not run or are reduced to a fade.
• Image alt text. Every meaningful image carries descriptive alt text. Decorative images use empty alt attributes so screen readers skip them.
• Form labels & error states. Every form field has a visible label and a programmatic association. Errors are announced to assistive technology and color is never the sole indicator of state — icon plus text plus color, every time.
• Touch targets. Interactive controls meet the 44×44 px minimum target size on mobile.

We aim for full WCAG 2.1 AA conformance on the marketing site. Where we know we fall short of that standard at any point in time, we list it here honestly:

• Third-party content. Embedded third-party content (for example, future video players or external map widgets) may not meet the same standards as our own components. We work around third-party gaps where we can; some are outside our control.
• Sample-report PDFs. Anonymized sample-report PDFs available via the resources hub are produced from inspection-platform output and may not yet be tagged for screen-reader navigation. Tagging the sample-report PDFs is on the roadmap; if you need an accessible version of a specific sample, email accessibility feedback below and we will produce one.
• Client portal. The client portal — preserved from the prior platform — is on a separate accessibility track. Specific portal-side conformance status is being confirmed for v1.Pending — to be confirmed

If you encounter a barrier on this site that is not listed above, please tell us — see "Feedback" below.

If a barrier on inspectsolutions.com prevents you from completing a task, or if a piece of content is unreadable, unclear, or unusable with assistive technology, we want to know about it.

The fastest way to reach the right person is email:

Email: info@inspectsolutions.com
Use subject "Accessibility feedback." A dedicated accessibility@ alias may be wired in a later update; until then, info@ is the canonical channel. Please include the URL where you encountered the issue, the assistive technology you were using (browser, screen reader, magnifier, voice control), and a description of what happened.

We aim to acknowledge accessibility feedback within two business days and resolve in-scope issues within 30 days. Out-of-scope items (for example, third-party widgets or PDF retroactive tagging) may take longer; we will tell you what we can and cannot fix and by when.

Accessibility work is part of how we ship — not a final inspection at the end. Specific recurring practices:

• Automated accessibility checks run as part of every code change before deployment
• Manual screen-reader testing on the home page and one service-detail page on every release
• Token-level contrast review whenever the design system changes
• External audit on each major site relaunch

This statement was last updated on the date shown at the top of this page. Material changes to our conformance status will be reflected here.