General contractors and construction companies—residential remodelers, design-build firms, kitchen-and-bath specialists, custom-home builders, multi-family and commercial general contractors, civil contractors, road and highway sub-contractors, electrical and mechanical sub-contractors, restoration contractors after fire and water damage, and disaster-recovery contractors—run customer-acquisition and bid-management flows through a website with online quote-request forms, project-gallery showcases, financing-application portals, real-time project-status dashboards, and bid-submission portals for sub-contractor partners. That flow is the customer's and sub-contractor's only practical channel for engaging the business, and under controlling ADA Title III case law in every U.S. circuit (the Domino's, Winn-Dixie, and Robles lines of authority) the website is itself a place of public accommodation when it is the gateway to commercial services. Construction has become a meaningful plaintiffs'-firm sector since 2024: California Unruh, New York State Human Rights Law, and Florida private-attorney-general cases have been filed against residential remodeling firms and design-build companies, with settlements in the $8,000–$30,000 range plus remediation costs. The much larger legal exposure for construction firms, however, is the DOJ's 2024 Title II Final Rule. Any contractor that holds a contract with a state, county, municipal, or public-university entity—a substantial share of all general contractors holds at least one such contract over the lifetime of the firm—is a sub-contractor of a public entity. The Title II Final Rule extends to information and services provided by sub-contractors on behalf of the public entity, including the contractor's online project-status, document-submission, and pay-application flows used by public owners, with a hard April 24, 2026 compliance deadline for jurisdictions serving 50,000 or more people. Federal-Highway-Administration projects, HUD-funded multi-family projects, and federally funded school-construction projects independently trigger Section 504 of the Rehabilitation Act. Construction firms in the European Union or marketing to EU-resident customers (luxury custom-home builders, second-home construction in Spain, Italy, France) face EAA exposure as of June 28, 2025. This guide covers the multi-statute legal framework, the construction-specific failure patterns, and a concrete compliance checklist.

Legal Requirements

Key Accessibility Issues in Construction & General Contractors

Quote-Request Forms With Placeholder-Only Labels and Inaccessible Photo-Upload Controls

Construction quote-request forms typically ask customers to describe a project, upload photos of the existing space, select a service category, and provide contact information. Common failures: every input uses placeholder-only labels (which disappear once the customer types and are not properly read by screen readers); the photo-upload control has no label and no instructions about acceptable file formats or maximum size; the service-category selector is a custom-styled grid of icon-only cards with no text; the budget-range field is a custom slider that cannot be operated with a keyboard. A homeowner with a disability who has just had a tree fall through their roof has no practical way to request emergency restoration services.

How to fix:

Use proper <label> elements—not placeholder text—for every form input. Provide explicit instructions for the file-upload control: accepted formats, maximum file size, and an alternative for customers who cannot themselves take photos ('Please call us instead' with a clear phone number, plus a 'Have someone else take photos and email them to us' alternative). Service-category selectors must be keyboard-operable radio buttons or a select element with descriptive labels, not icon-only cards. Budget-range inputs must be an accessible <input type='number'> or a properly-implemented WAI-ARIA slider, not a custom styled <div>.

Project Galleries Without Descriptive Alt Text and With Mouse-Only Lightbox Modals

Construction-portfolio pages depend heavily on photography—before-and-after kitchen remodels, custom-home exterior shots, commercial-building completions, drone footage of large projects. The standard implementation in WordPress builder themes (Bridge, Avada, Divi, Salient) and Squarespace construction templates is a Masonry-style image grid where every photo has empty or filename alt text and clicking a photo opens a JavaScript lightbox modal that does not trap focus, does not return focus to the originating thumbnail on close, and does not expose Previous/Next controls to keyboard users. Screen-reader users cannot understand what was built; keyboard users get trapped in the lightbox.

How to fix:

Write descriptive alt text for every project photo in client-meaningful terms ('Modern white-oak kitchen with quartz countertops, paneled refrigerator, and island seating four; before remodel was a galley kitchen with closed-off dining room'), not internal job numbers. Lightbox modals must trap focus, expose Previous/Next/Close as keyboard-operable buttons with visible focus indicators, and return focus to the originating thumbnail on close. For drone-footage videos, provide captions, an audio description track, and a text transcript that summarizes what is visible.

Project-Status Dashboards and Owner-Communication Portals That Fail Single-Page-Application Accessibility Basics

Mid-size and large general contractors increasingly run a project-status dashboard or owner-communication portal—Procore, Buildertrend, CoConstruct, Houzz Pro, JobNimbus, or a custom React/Vue single-page-application—where the public-entity owner or homeowner can see schedule, change orders, RFIs, payment applications, and progress photos. Common failures: page transitions do not announce to screen readers (no ARIA-live region updates, no focus management); the schedule visualization is a Gantt chart implemented as a canvas with no accessible alternative; change-order PDFs are image-only flattened exports; progress-photo galleries inherit the same defects as marketing-site galleries.

How to fix:

Verify the vendor's VPAT and independently test the embedded portal with NVDA/Firefox and VoiceOver/Safari. The portal must announce navigation changes through ARIA live regions and manage focus correctly across route transitions. Gantt charts and other complex visualizations must have an accessible alternative—a structured HTML table with task name, start date, end date, dependencies, and status. Change-order, RFI, and pay-application PDFs must be tagged accessible PDFs with proper heading structure, not image-only flattened exports. If the vendor cannot deliver this, escalate to the vendor or replace the portal in advance of public-entity contract renewals.

Financing-Application Forms That Embed Inaccessible Third-Party Lender Iframes

Many residential remodelers and design-build firms offer in-house or partnered financing through GreenSky, Synchrony Home, Wisetack, Hearth, or a regional bank's branded portal, embedded as a third-party iframe on the contractor's website. Common failures: the iframe has no accessible name (no title attribute); focus visibility is broken inside the iframe; required fields are conveyed only through red border styling; error messages appear as transient red text that disappears on the next interaction; the iframe is fixed at a width that breaks at 320px viewport, violating WCAG 1.4.10 Reflow.

How to fix:

Add a descriptive title attribute to every embedded iframe ('Project financing application'). Verify the lender vendor publishes a current VPAT and that the embedded form actually conforms to it (vendor VPATs frequently overstate; independently test). Required fields must be conveyed by text labels and aria-required, not red border styling alone. Error messages must persist until corrected and must be announced via aria-live regions. The iframe must be responsive down to 320px width or include a documented alternative path (a clearly published phone number and email for paper applications).

Sub-Contractor Bid-Submission Portals That Lock Out Disabled Sub-Contractor Owners

General contractors who run sub-contractor bid invitations through a portal—Building Connected, iSqFt, Pantera, BidClerk, ConstructConnect, or a custom system—routinely deploy interfaces that block sub-contractor owners with disabilities from competing. Common failures: the bid-document download is provided only as image-scanned PDFs from old project drawings; the bid-submission form requires a JavaScript-only file uploader; addenda are posted as image-only notices; the messaging center between the GC and the sub is a chat widget that violates the same accessibility patterns as customer-support chat. This independently exposes the GC to ADA Title I employment-related discrimination claims and, on public-entity projects, to Title II Final Rule sub-recipient obligations.

How to fix:

Bid documents must be tagged accessible PDFs with proper text layers (run OCR on legacy scanned drawings and ship the OCR layer with the PDF). Bid-submission file uploaders must work without JavaScript or have a clearly published email-based fallback. Addenda must be posted both as accessible PDFs and as plain HTML on the project page. Replace the chat-widget messaging center with one that has been independently tested to meet WCAG 2.1 AA (Intercom and Drift have reasonable VPATs but require independent verification; older Tawk.to and LiveChat installs frequently fail). Document the alternative-format request process in a 'Sub-Contractor Accessibility' page.

Compliance Checklist

  • Quote-request forms use proper <label> elements (not placeholder-only), file-upload instructions are explicit, and an alternative for customers who cannot photograph their project is provided
  • Service-category and budget-range selectors are keyboard-operable native form controls or properly-implemented WAI-ARIA widgets, not custom styled divs
  • Project galleries have descriptive alt text on every photo, lightbox modals trap focus and return focus on close, and Previous/Next/Close are keyboard-operable
  • Drone-footage and project-walkthrough videos have captions, audio description, and a text transcript
  • Project-status dashboards and owner-communication portals have a current VPAT, announce route transitions via ARIA live regions, and provide accessible alternatives for Gantt charts and other complex visualizations
  • Change-order, RFI, and pay-application PDFs are tagged accessible PDFs (not image-only flattened exports)
  • Financing-application iframes have descriptive titles, conform to a current VPAT, and meet WCAG 1.4.10 Reflow at 320px viewport width
  • Sub-contractor bid documents are tagged accessible PDFs (with OCR text layers for legacy scans), and bid-submission flows include a documented non-JavaScript or email fallback
  • Careers and job-application pages on federal-contractor sites meet WCAG 2.1 AA per Section 503 / Section 508 expectations
  • If the firm holds a state, county, municipal, or public-university contract, DOJ Title II compliance is on schedule (April 2026 large entity / April 2027 small entity)
  • If the firm uses federal funds (FHWA, HUD, ED, USDA), Section 504 compliance is documented and the agency's accessibility expectations have been incorporated
  • Accessibility statement is published, names the project-management and financing vendors, and provides a documented contact path for accessibility issues
  • Site has been audited with axe, Pa11y, or Lighthouse and manually tested with NVDA, VoiceOver, and TalkBack in the last 12 months

Further Reading

Other Industry Guides