Accessibility Statement

Our Commitment

This statement was last reviewed in July 2026.

The standard we build to is the Web Content Accessibility Guidelines version 2.2 at Level AA. That is a published, testable standard rather than a general intention to do well.

The reason is straightforward. A person looking for a crane at eleven at night with a failed rooftop unit needs the phone number to work with a screen reader, at high zoom, on a phone, with one hand. Accessibility here is not a compliance exercise bolted on at the end, it is the same work as making the site fast and clear.

What Has Been Built In

These are the specific measures already in place across every page of the site, not a wish list.

• Semantic HTML. Real headings in order, real lists, real navigation landmarks, real definition lists on the glossary. Structure is expressed in markup rather than in styling.
• Keyboard navigation. Every interactive element can be reached and operated with a keyboard alone. There is a skip link to the main content as the first focusable item on every page.
• Visible focus indicators. A high contrast outline follows keyboard focus everywhere, including on dark sections where the outline color changes to stay visible.
• Color contrast. Body text, muted text and interface text are all checked against the AA thresholds. The lime accent is used only as a background behind near-black text, never as text on white, because that combination fails contrast.
• Touch target size. Buttons, links in navigation and form controls meet a minimum height so they can be operated reliably by touch.
• Reduced motion support. The site honors the reduced motion preference in your operating system and removes transitions and smooth scrolling when it is set.
• Forms with real labels. Every field has a visible label tied to it, hints are associated by description, and errors are announced rather than shown only in color.
• Meaningful alternative text. Photographs describe what is actually happening in the job rather than repeating a keyword. Decorative graphics are hidden from assistive technology.
• Zoom and reflow. Pages reflow to a single column at high zoom and on small screens, and no page scrolls horizontally at any width.
• Content that works without JavaScript. Frequently asked questions, navigation and page content are readable and usable with scripting unavailable.

What We Know Is Not Perfect

Being honest about the gaps is more useful than claiming there are none.

The embedded Google map is a third-party component and we do not control its internal accessibility. Every address it shows is written out in plain text next to it, and directions are available through a normal link, so nothing on that page depends on the map itself.

Some of the legacy photographs recovered from the previous site are lower resolution than we would like, which affects clarity at high zoom.

Testing is done with keyboard navigation, screen reader review, contrast checking and automated audits, and it is done by the people who built the site rather than by an outside auditor. We would rather tell you that than imply an independent audit that has not happened.

Report A Barrier

If any part of this website stops you from getting what you came for, we want to know, and we will treat it as a fault rather than a suggestion.

Call (928) 249-2188. The phone is answered around the clock and it reaches the owner, not a queue. You can also email hcwmobileservices@gmail.com.

Tell us the page, what you were trying to do, and what got in the way. If you are using a screen reader, a magnifier, voice control or any other assistive technology, naming it helps us reproduce the problem quickly.

In the meantime, anything on this website can also be done by phone. Quoting, scheduling, describing a site and asking questions all work perfectly well in a conversation, and that route is always open to you.