Legal
Accessibility
Crews and office staff use this software all day, in trucks, on roofs, and at kitchen tables. It should work for all of them. Here is the standard we build to, where we know we fall short, and how to tell us when we do.
This applies to ContractorX and to every site and product we operate under it: contractorx.co, rooferx.com (RooferX), solarsalesx.com (SolarSalesX), and tradesmenx.com (TradesmenX). RooferX, SolarSalesX and TradesmenX are the ContractorX platform presented for a particular trade, not separate services. Where this page says ContractorX, the Services, or we, it means all of them.
Last updated August 20, 2026. Questions about anything here? Contact us.
The standard we build to
We target WCAG 2.2 Level AA across contractorx.co and the platform. In practice that means semantic structure and landmarks, keyboard operability for every interactive element, visible focus, text alternatives for meaningful images, color contrast that clears the AA thresholds, meaning never carried by color alone, touch targets sized for use with gloves on, form labels and described errors, and respect for reduced-motion preferences.
How we hold ourselves to it
- Accessibility is part of design review, not a pass at the end.
- Keyboard and screen reader checks are part of how we test interactive work.
- Motion-heavy sections respect the operating system's reduced-motion setting and fall back to a static presentation.
- Mobile layouts are designed for one-handed use with large touch targets, because the field app is used standing up.
Where we know we fall short
Being straight about this is more useful than a blanket claim of conformance. Some parts of the product are harder than others: dense data tables, the drag-and-drop scheduling surface, and map-based canvassing views rely on visual interaction that we have not yet matched with an equally good non-visual path. Third-party components we embed, such as payment and signature flows, are governed by their providers’ own accessibility work. We treat those as open items rather than finished ones.
Tell us about a barrier
If something blocks you, we want the specific case rather than a general complaint, because the specific case is fixable. Send it through the contact page with “Accessibility” in the subject, and include the page or screen, what you were trying to do, and the assistive technology and browser or device you were using.
We acknowledge accessibility reports within five business days, tell you what we found, and give you a timeline for the fix. If a fix will take a while, we will work with you on another way to get the task done in the meantime.
Formal requests
If you need this statement or any of our policies in another format, or need an accommodation to evaluate or use the platform, ask through the same route and we will arrange it. This statement is current as of August 20, 2026 and is reviewed as the product changes.