Website Builders Are the Biggest Offenders — Here's How to Fix That

An uncomfortable truth about our industry

When a small business gets hit with an ADA demand letter, the lawsuit names the business — but the person who built the site is almost always the reason it's non-compliant. Drag-and-drop builders, template marketplaces, agency churn-and-burn shops, and well-meaning freelancers are collectively the biggest source of inaccessible websites on the public internet. Most builders aren't doing it on purpose. They simply were never taught accessibility, the tools they use don't enforce it, and their clients don't know to ask for it. The result: a constant pipeline of brand-new websites that are out of compliance the day they go live.

Why builders ship inaccessible sites

• Templates ship broken. The most popular themes on Wix, Squarespace, Shopify, Webflow, and WordPress regularly fail color contrast, focus visibility, and form-label requirements out of the box. Designers pick a template that looks good and never test what it does to a screen reader.
• "Looks good" is the only QA. Most builders test on their own laptop with a mouse. They don't tab through the page. They don't load it in a screen reader. They don't zoom to 200%. They don't test mobile touch targets.
• Page builders hide the markup. Visual editors emit non-semantic <div> soup, skip heading levels, and bake images into backgrounds (no alt possible). The builder never sees the HTML and assumes it's fine.
• Overlay widgets create false confidence. Adding an "accessibility widget" does not make a site WCAG-compliant. The DOJ and plaintiffs' attorneys have publicly stated this. Real remediation has to happen in the underlying code.
• Clients don't ask. Most small business owners have never heard of WCAG. If the builder doesn't bring it up, it doesn't get done.
• Speed and price compete with quality. When the bid is "$1,500 in two weeks," accessibility is the first corner cut.

The 10 mistakes that show up in almost every freshly-built site

1. Buttons and links with insufficient color contrast (the brand color isn't AA against white)
2. Images with empty, missing, or junk alt attributes ("image123.jpg")
3. Icon-only buttons with no accessible name
4. Form inputs with placeholder text instead of real <label> elements
5. Heading hierarchy that skips levels (h1 → h4) or has multiple h1s
6. Hamburger menus and modals that trap or lose keyboard focus
7. Carousels and sliders with no pause control and no keyboard support
8. Videos embedded without captions or transcripts
9. Mobile touch targets smaller than 44×44px (especially in footer link clusters)
10. Custom dropdowns built with <div>s instead of native <select> or proper ARIA

Why this is now a builder problem, not just a client problem

Two things changed recently. First, the DOJ's 2024 Final Rule cemented WCAG 2.1 Level AA as the federal accessibility standard — the courts and plaintiffs' bar will follow. Second, contracts in most US states now allow plaintiffs to name the developer or agency in addition to (or instead of) the business owner when the failure was clearly a build defect. Agencies that ship inaccessible sites aren't just leaving money on the table — they're taking on direct legal exposure.

A practical playbook for builders

You don't have to become an accessibility specialist overnight. You do have to install some basic discipline:

1. Learn the four POUR principles, then memorize 10 success criteria

You don't need all 50 Level AA criteria in your head. You need the ones that account for ~80% of violations: contrast (1.4.3), keyboard (2.1.1), focus visible (2.4.7), labels (3.3.2), name/role/value (4.1.2), alt text (1.1.1), reflow (1.4.10), target size (2.5.5), captions (1.2.2), and headings (1.3.1).

2. Run automated checks before you call a build "done"

Free tools — axe DevTools, WAVE, Lighthouse, Pa11y — catch roughly 30–40% of issues in seconds. They should be a non-negotiable step in your build checklist. They are not sufficient on their own, but if you're not even running them, you're shipping garbage.

3. Do the 60-second manual checks every time

• Tab through the whole page with no mouse. Can you reach and operate every interactive element? Is the focus indicator always visible?
• Zoom to 200%. Does anything overlap, get cut off, or require horizontal scrolling?
• Resize the window to 320px wide. Does content reflow without breaking?
• Turn on a screen reader (VoiceOver on Mac, NVDA on Windows — both free) and listen to the homepage. Does it make sense?

4. Pick accessible-by-default templates and components

Some platforms and component libraries take accessibility seriously (Radix UI, Headless UI, shadcn/ui, GOV.UK Design System). Others don't. When you choose a foundation, that choice locks in 80% of your accessibility outcome before you write a single line of custom code.

5. Stop selling "accessibility widgets" as compliance

Overlay widgets that promise "instant ADA compliance" are a documented liability trap. Plaintiffs' firms specifically target sites running them. They can be a useful end-user tool layered on top of a properly remediated site — but they are not a remediation strategy. Tell your clients the truth.

6. Quote accessibility as a line item

Most clients will pay for accessibility if you explain it. Add a line item to every proposal: "WCAG 2.1 Level AA build standard — includes audit, remediation, and a compliance report." Then actually deliver it. Charge for it. The Section 44 Disabled Access Credit (up to $5,000/yr) and Section 190 deduction (up to $15,000/yr) mean most small-business clients can recover most of the cost from the IRS. That's a powerful close.

7. Hand the site off with a compliance report

Every project should end with a dated WCAG 2.1 AA conformance report identifying which pages were audited, which success criteria were tested, and the results. This protects your client legally and protects you professionally. It also makes ongoing monitoring an easy upsell.

8. Partner instead of pretending

You don't have to do the deep audit work yourself. ADA Active Shield's reseller and agency partner program lets you deliver certified, remediated sites under your own brand without becoming an accessibility specialist. Your clients get a compliant site and a certification badge. You get a new high-margin service line and zero liability for the audit work.

The bottom line for builders

The web is becoming a regulated medium. Builders who learn to ship accessible sites will keep their clients out of court, command higher rates, and earn referrals from CPAs and attorneys. Builders who keep shipping the same template-driven, untested work will, eventually, ship one straight into a $25,000 demand letter — and their client will remember who built it.