Conversion, accessibility, and the liability nobody mentions.
60.8 percent of roofing homepages ship a critical WCAG violation, against 3,948 federal ADA filings in 2025.
A legal risk and a conversion problem, together.
60.8 percent of roofing-brand homepages carry at least one critical WCAG violation, measured on the homepage alone before any interior page is tested. In 2025, 3,948 federal ADA website lawsuits were filed in the United States. The common failure pattern is mundane: the phone number buried in the footer, no above-fold estimate request, form fields without labels, contrast that fails on a phone in daylight.
What a critical violation actually is.
Not an obscure technicality. Filings and scans concentrate on the same handful of failures.
Why this trade in particular.
Roofing sites are built on the tooling that produces the failing markup, and they are transactional rather than decorative. A complaint needs something a person could not do, and an estimate form is exactly that. The combination is why the trade appears disproportionately in both the scans and the filings.
The same fixes serve conversion.
Labelled inputs, real headings, keyboard-operable navigation, and sufficient contrast are accessibility requirements and conversion improvements at once. Every item on the checklist above also affects whether a homeowner completes your form on a phone on mobile data. Nothing on the list constrains the design, and most of it is what correct markup gives you for free.
Overlay widgets do not fix it.
The accessibility overlay, the circular icon that opens a panel of contrast and font-size controls, has itself been named in filings. It sits on top of the markup rather than correcting it, and it cannot supply a label a form field does not have. The fix is structural, which is why the build standard here is semantic HTML with no JavaScript required to render a page.
Speed belongs in the same conversation.
Google publishes three thresholds for a good experience: Largest Contentful Paint at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1, all measured on real visits, mostly on mid-range phones. The usual cause of failing them is scripts, and the usual source of scripts is the page builder plus a chat widget, a review carousel, and a call-tracking snippet nobody can name the owner of.
Trust is the other half of conversion.
The test every trust signal has to pass is whether a reader can check it. A licence number can be verified, a manufacturer certification can be looked up, a photograph of a roof in their suburb can be recognised. Stock imagery, unrecognised badge grids, and counters claiming thousands of happy customers fail that test and weaken the verifiable facts placed next to them.
What to do first.
Run a free automated checker, then try to complete your own estimate form using only the keyboard. Automated tools catch a minority of issues, commonly estimated at around a third, because most criteria require judgement. Treat a clean scan as a floor rather than a pass. None of this page is legal advice. For exposure specific to your company and state, ask a lawyer. What an audit can tell you is exactly what your site fails today.
The first screen has three jobs.
Say what you do, say where you do it, and offer one obvious next step, inside about two seconds. The documented failure across roofing sites is a hero image, a slogan, and nothing actionable until the footer. A homeowner who has just found water coming through a ceiling does not scroll to look for you, and a first screen approved on an office desktop is how that gets shipped.
Why one call to action rather than three.
Competing actions reduce completion of all of them, because the visitor now has a decision to make before they can act. A homeowner in the middle of a leak is not choosing between a brochure download, a newsletter, and a quote. Pick the single enquiry you want, put one checkable trust fact beside it, and move everything else below the fold.
Click to call, done properly.
Six details, and the first two account for most failures.
What page builders emit, and why it matters here.
Containers nested eight or ten levels deep, headings chosen for size rather than hierarchy, buttons built from styled divs, inline scripts per section, and content that only appears once the builder's runtime has executed. A crawler, an assistive technology, and an answer engine all depend on structure to understand a page. Strip it out and the page looks organised to a human and reads as an undifferentiated block to everything else.
The CMS is not the variable.
Clean markup is a question of who writes the templates, not which platform they sit on. WordPress under a lean theme is fine; the same WordPress under a page builder is not. So the question for a vendor is whether they control the markup or inherit it, and the way to settle it is to open the source of a page they built.
Three checks, five minutes, no vendor required.
View source and count the nesting depth before you reach a paragraph of real text. Search for a JSON-LD block. Then disable JavaScript and reload: if the page is blank, everything that reads markup rather than rendering it is seeing the same blank page. Those three answers tell you most of what an audit would, and they cost nothing.
The asset already sitting on your phone.
Completed jobs. Nearly every company photographs them and almost none publish them in a form that does any work. Captioned with the suburb, the roof type, the problem and the fix, one job is a trust signal, a local page and an answer to a real query at the same time. Cheapest content in the trade, least used.
The exposure, in three figures.
Sourced from the roundup cited under each figure.
Roofing homepages with a critical violation
At least one critical WCAG failure on the homepage alone.
Federal ADA website lawsuits, 2025
Filings in United States federal courts in a single year.
Most common failure
Phone number in the footer only, no visible estimate request on first screen.
SOURCE: WEB TONIC ROUNDUP, 2025 FEDERAL ADA FILING COUNT.
Every guide in this pillar.
60.8 percent of roofing homepages ship a critical violation. Here is what that means and what to check first.
The documented failure is a phone number buried in the footer and nothing actionable above the fold.
Most roofing traffic is mobile. The phone number should be one tap, on every page, without JavaScript.
What the three vitals mean for a roofing site, and why JavaScript is almost always the cause.
Two sites with identical content can perform very differently. The markup is the reason.
Licence detail, real project galleries, and named references, rather than a grid of badges nobody recognises.
Questions about this pillar.
Is this legal advice?+
No. It explains a documented risk pattern and the technical standard that addresses it. For exposure specific to your company and state, ask a lawyer.
Does an accessibility overlay fix it?+
No. Overlay widgets have been named in filings themselves. They sit on top of the markup rather than correcting it, and they cannot supply a label a form field does not have.
Does compliance hurt the design?+
No. Contrast, labels, and heading structure constrain nothing that matters visually, and they measurably improve completion on mobile.
How much of this can be tested automatically?+
Commonly estimated at around a third. The rest needs judgement, and the keyboard test finds more real problems than any scanner.
We are on a page builder. Do we have to rebuild?+
Not necessarily. Labels, alternative text, and contrast can be fixed in place. What cannot be fixed in place is markup structure and the scripts the builder requires to render, which is where a rebuild earns its money.
Find out what your site fails.
$2,500, and every accessibility and speed failure comes back in writing.