HTML structures your page. CSS makes it look like something. Between those two you can build essentially anything, and more importantly, you can fix essentially anything. That second part is why I have never left them.
Why control is the real argument
Every template is somebody else’s decision about your website, made before they met you. Most of the time that is invisible and harmless. It stops being harmless the moment you need something the template did not anticipate: a heading structure a screen reader can follow, a form label that is actually tied to its input, a color pairing that clears 4.5:1, a page type the theme has no slot for.
At that point you find out how much of your own site you can actually reach. With hand-coded HTML and CSS, the answer is all of it. With a template or a drag-and-drop builder, the answer is whatever the platform chose to expose in its settings panel.
h3 to an h2 without changing how it looks. On a hand-coded site that is a ten-second edit. On a lot of builder platforms it is not possible at all, because the visual size and the heading level are the same setting.
ADA compliance lives in the markup
This is the part business owners find surprising. Accessibility is not a feature you switch on. It is a property of the code: the order of the headings, the presence of landmarks, whether every image has a real alt attribute or an empty one on purpose, whether the keyboard can reach every control and whether focus is visible when it gets there.
The POUR principles from WCAG name the four things that have to be true:
- Perceivable — text alternatives for anything visual, captions for anything spoken, contrast a low-vision reader can actually see.
- Operable — everything reachable and usable by keyboard, switch device or screen reader, not just a mouse.
- Understandable — consistent navigation, predictable behavior, error messages that say what went wrong and how to fix it.
- Robust — valid, semantic markup that assistive technology can parse now and after the next browser update.
All four are decisions made in the HTML. That is why I hand-code every site and why every Web Chick build gets a real screen-reader pass, JAWS and VoiceOver, before it goes live. An automated scanner catches maybe a third of what matters. It cannot tell you that your tab order sends someone through the footer before the form.
Speed: what a template makes you carry
A hand-coded page loads the HTML, the CSS and the fonts. That is the payload. A typical builder page loads a theme framework, the page-builder runtime, jQuery, an animation library, and whatever each installed plugin decided to inject, and it does most of that before your first paragraph shows up.
Google has been mobile-first for years now, and Core Web Vitals are part of how pages get ranked. Slow is not just annoying, it is a ranking input and a bounce driver. When people have trouble getting information from a site, most of them do not try again; a large share go straight to a competitor.
Looking like yourself
There is also the plain commercial problem. Popular templates are popular. If three businesses in your county bought the same theme, you all look like the same business, and the one visitors remember is whoever got there first.
Around here the motto is: if you look fresh, we look fresh. That is why revamps are part of what Web Chick clients get rather than an upsell. Your site staying current is in my interest too.
When a template is genuinely fine
I am not going to pretend it never is. If you need a one-page placeholder up this weekend, you are the only person who will ever edit it, and nothing about your business is legally required to be accessible, a template is a reasonable tool and I would not talk you out of it.
The trouble starts when that placeholder becomes the real site, and then a customer using a screen reader cannot check out, or a demand letter arrives, or you want a page the theme has no room for. Everything you build on top of a platform you do not control is built on rented ground.
The short version
Templates optimize for getting started. Hand-coded HTML optimizes for everything after that: being fixable, being fast, being accessible, and being yours. Thirty years in, I have not found a client who regretted owning their code.
Originally published on Daily Queue in June 2024. Rewritten and expanded for WebChick.com in July 2026 with current WCAG 2.2 guidance, Core Web Vitals context and an expanded FAQ.
