Does a Website Redesign Fix Accessibility?
A rebuild changes how a site looks. Esther's findings show which accessibility barriers survive a redesign and which the platform carries in from day one.
Rick Hensbergen4 minute read
A redesign changes what a site looks like. It rarely changes what a site carries.
Most organizations approach a website rebuild as a fresh start. Over the past six months (May 16 to November 11, 2026), though, Esther found the same barriers appearing on sites however recently they had been rebuilt. The platform a site runs on, and the template it ships with, determined far more of the outcome than the content anyone added afterward.
The figure that anchors this: 36% of the barriers Esther found were systemic, meaning they came from the platform or template itself. Another 48% were mixed, present in both the platform layer and the content layer, so fixing them requires work in both places. Only 16% were strictly local, something a content editor or developer added after the template was in place. One in four of the sites assessed carried no locally added barriers at all, and the median site added only one.
The implication is direct. A redesign that swaps the look without auditing the template carries the great majority of the problem forward.
The barriers a rebuild is least likely to clear
Structure that only looks like structure varied most across the seven platform groups (sites built on the same platform). The gap between the platform where it appeared least and the platform where it appeared most was 71 percentage points. That gap reflects how the platform renders headings, lists, and tables by default. Text can be styled to look like a heading without being marked up as one, and a screen reader moving through the page by heading finds nothing to hold onto. The person using it hears the page read flat, with no way to skip to the section they need.
Form fields without labels showed a similar pattern across platform groups. A field that carries only its placeholder (the gray hint text inside the box, which disappears the moment a resident starts typing) has no label a screen reader can announce. The form looks complete. For someone who cannot see it, the field is a blank, and that blank decides whether a payment goes through or an application gets submitted.
Two more barriers sit in the same tier:
- Links that do not say where they go. A list of links reading "click here" and "read more" works for sighted users who see what surrounds each one. For someone moving through a list of links on its own, it names nothing.
- No visible focus indicator. People who use a keyboard move through a page by pressing Tab. Without a visible marker showing which element is selected, there is no way to tell where they are.
The barriers a rebuild is most likely to clear, if someone checks
Missing image descriptions and instructions that rely on sight sit in a different category. Both are serious, and both tend to be content-level: an editor uploads an image without a description, or writes a form instruction that says "click the blue button" to someone who cannot see which button is blue.
Barriers like these are the most likely to disappear in a rebuild, because a rebuild often starts with new content. They are also the most likely to return within months of launch, because they depend on what editors do with every upload and every instruction afterward. A rebuild clears the existing instances. It does not change the process that created them.
Passages in another language not marked had the lowest maximum share of any barrier in the data. A content editor can fix it without a developer, because the markup is a single attribute on the surrounding element.
What to look at before you sign off on a launch
The divide the data draws is between the template and the content. A platform decision sets the ceiling on what a redesign can achieve. If the platform ships with unlabeled form fields and unstructured markup, those barriers arrive on day one, and no amount of careful content editing removes them.
Three questions show whether the new site is better or the same problem in a newer shell:
- Can a person using a keyboard move through every page without a mouse, and see where they are at each step? If nothing highlights when they press Tab through a form, the focus indicator is missing, and the barrier is in the template.
- Does every form field keep a visible label after someone starts typing? If the label disappears, it was only placeholder text, whatever the design mockups showed.
- Do the headings on a page describe what follows each one? Headings that could belong to any section ("Learn more," "Information," "Next steps") mean the structure is visual only, and a person using a screen reader runs into the barrier the previous site carried.
The obligation for state and local government is clear. The Department of Justice requires WCAG 2.1 Level AA, by April 26, 2027, for governments serving populations of 50,000 or more, and by April 26, 2028, for smaller entities and special districts. A redesign scheduled before those dates is an opportunity, and whether it is a sufficient one depends on which layer the work addresses. Barriers that trace to one shared template often clear with a single change that carries to every page built from it, so the work is smaller than the barrier count suggests.
For private organizations there is no equivalent deadline, but the Department of Justice has stated that the ADA applies to business websites, and the obligation is ongoing.
For what this means for a government website, see For government; for a private organization, For business. Earlier findings on where accessibility barriers cluster, and how to check if your website is accessible.
Figures cover government websites in seven platform groups, each site measured once over the six months from May 16 to November 11, 2026. Shares are rounded.
About the author

Rick Hensbergen is the founder and CEO of Esther. He has spent his career in governance and risk, twenty years of it at major banks in the United States and the United Kingdom, including as a Senior Manager approved by the UK's Financial Conduct Authority.
