Home-services contractors—HVAC companies, plumbers, electricians, handyman services, roofers, pest-control operators, and general construction firms—serve a customer base that is statistically more likely to include people with disabilities than the general population: older homeowners aging in place with reduced vision and hearing, disabled veterans using VA home-improvement grants, and families with disabled household members who rely on climate control, running water, and electricity as genuine medical necessities. Yet home-services websites remain some of the most inaccessible small-business sites on the web. They are typically template-driven, frequently built on WordPress or Wix by a generalist marketing agency, and often retrofitted with third-party booking widgets, live-chat plugins, and quote-request forms that were never audited against WCAG. The stakes are higher than most contractors realize: when a homeowner cannot reach an HVAC company during a July heat wave because the phone-number link on the mobile site is an image of text with no tel: href, or when a deaf customer cannot schedule an emergency plumbing call because the after-hours form depends on audio CAPTCHA, the inaccessibility is not theoretical—it can become a habitability or medical emergency. Serial ADA demand-letter campaigns have expanded beyond retail and hospitality into the home-services sector over the past 24 months, with California, New York, and Florida plaintiffs targeting HVAC and plumbing companies that advertise statewide service areas. This guide covers the legal framework contractors face, the specific accessibility failures that recur across the sector, and a concrete compliance checklist that a small-shop owner can work through without hiring an enterprise accessibility consultant.

Legal Requirements

Key Accessibility Issues in Home Services & Contractors (HVAC, Plumbing, Electrical)

Emergency-Service Phone Numbers Rendered as Images of Text

HVAC and plumbing sites almost universally feature a prominent 24/7 emergency phone number, but that number is frequently embedded in a decorative banner image with no alt text, no tel: link, and no text fallback. A screen-reader user in an emergency—say, a deaf-blind customer whose refrigeration has failed and medication is warming—cannot extract the number from the page. Even visually-oriented users on small screens sometimes cannot tap an image-embedded number.

How to fix:

Always render the phone number as real text wrapped in a tel: link: <a href="tel:+15551234567">(555) 123-4567</a>. Ensure the link text includes the full number and is not visually hidden. Add descriptive alt text to any graphical banners (alt="Call our 24/7 emergency line at 555-123-4567"). Test on a mobile screen reader (VoiceOver or TalkBack) to confirm the number is announced and actionable.

Online Quote Forms Without Field Labels or Error Messages

Quote-request forms often rely on placeholder text as the sole field label, lack fieldset/legend grouping for multi-section forms, and validate only on submit without associating error messages to the specific fields. Customers using screen readers frequently cannot tell which field is asking for which information, and many abandon the form mid-way.

How to fix:

Use visible, persistent <label> elements for every form field. Group related fields (customer info, service address, problem description) inside <fieldset> with <legend>. On validation failure, move focus to the first error, associate error text via aria-describedby, and ensure errors are announced through a polite live region. Never rely on placeholder text as the only label.

Scheduling Widgets From Third-Party Vendors Without VPATs

Contractors increasingly embed third-party scheduling widgets (Housecall Pro, ServiceTitan, Jobber, Schedule Engine, ActiveCampaign) to let customers book directly. These widgets vary enormously in accessibility: date pickers are often keyboard-inaccessible, time-slot grids fail keyboard focus order, and modal dialogs trap focus incorrectly. The contractor is legally responsible even when the barrier is in a vendor's widget.

How to fix:

Request a VPAT or Accessibility Conformance Report from every embedded-widget vendor before deployment. Test the live widget against WCAG 2.1 AA: keyboard navigation of the calendar, screen-reader announcement of available slots, focus management on modal open and close, and color contrast of selected states. If a widget is not conformant, provide a clearly labeled phone and email alternative on the same page ("Prefer to book by phone? Call 555-123-4567 or email [email protected]").

Before-and-After Project Galleries With No Alt Text

Roofers, remodelers, and general contractors typically include extensive photo galleries showcasing before-and-after transformations. These images carry most of the sales content on the site, yet they are almost always uploaded with no alt text or with generic CMS-generated alt ("IMG_2345.jpg"). A blind prospective customer evaluating workmanship has no equivalent content.

How to fix:

Write descriptive alt text for every meaningful project photo ("Before: cracked asphalt driveway with potholes—35 feet by 20 feet. After: poured concrete driveway with stamped-brick border, same dimensions"). For decorative borders and logo images, use empty alt (alt=""). Consider a short written case study next to each before/after pair summarizing materials, timeline, and cost range.

Accessibility of Financing Applications and Digital Payment

HVAC and roofing projects frequently run into five figures, and contractors partner with third-party financing providers (Synchrony, GreenSky, FTL Capital) whose application forms are embedded or linked from the contractor site. These finance-application flows are subject to both WCAG requirements and the heightened error-prevention requirements of WCAG 3.3.4 (legal, financial, data). Inaccessible authentication, form timeouts without warning, and long legal disclosures delivered as scanned PDFs are recurring failures.

How to fix:

Confirm financing-partner applications meet WCAG 2.1 AA; require a VPAT as a condition of the partnership. On embedded flows, audit the full journey from “Apply Now” to approval confirmation. Ensure timeout warnings give the user a chance to extend the session (WCAG 2.2.1). Deliver disclosures as accessible HTML with tagged-PDF alternatives rather than image-only scans. Offer a phone-based application path as a documented accommodation.

Compliance Checklist

  • Phone numbers are real text inside tel: links, not images of text
  • Quote and contact forms have visible labels, fieldset grouping, and accessible error handling with focus management
  • Third-party scheduling widget has a current VPAT and has been tested for keyboard and screen-reader accessibility
  • Project gallery images have descriptive alt text; decorative images use empty alt
  • Emergency-service page is reachable within two clicks from the home page and is keyboard- and screen-reader-navigable
  • Financing application flow meets WCAG 2.2 AA including error prevention and authentication requirements
  • Color contrast meets 4.5:1 for body text and 3:1 for UI components and large text
  • Site has been audited against WCAG 2.2 AA within the past 12 months and findings tracked to remediation
  • Accessibility statement published with contact channel for accommodations and last review date
  • Service-area map and ZIP-code lookup have a text-based alternative

Further Reading

Other Industry Guides