You launch a redesigned site, clear an accessibility audit, and feel like the problem is finally handled. Six months later, support tickets and sales feedback say something different: new landing pages break keyboard focus, forms confuse screen readers, and marketing PDFs are opaque to anyone using assistive tech.
If accessibility work only happens during redesigns, your problem isn’t missing checklists—it’s missing ownership, workflows, and metrics that keep accessible content and UX from regressing.
This isn’t about one bad project or one sloppy vendor. It’s a governance pattern. And if you run a revenue-impacting site, keeping that pattern running is quietly expensive.
In this article, we’ll treat your recurring accessibility failures as a website ownership problem, not a moral failing or a technical quiz. The question isn’t “Do we care?” It’s “Who owns this, every week, between redesigns?”
1. The moment you realize accessibility work only shows up during redesigns
The realization usually lands in an uncomfortable meeting.
Someone forwards a frustrated user email. Sales mentions a prospect who couldn’t submit a form. Legal asks when you last checked for accessibility issues. You remember the big audit during the redesign and think, “Didn’t we already fix this?”
Then you dig in and notice the pattern:
- The homepage and core templates still look close to what was audited.
- But the campaign microsites, resource library, and new forms are full of fresh barriers.
- No one can tell you who is supposed to catch those issues before launch.
We often see this when a marketing or operations lead inherits a “recently redesigned” site. On paper, it’s modern and compliant. In practice, the past six months of content changes have quietly reversed a lot of that work.
The root problem: accessibility is treated as an event, not an operating condition.
You can see the same pattern described from a strategy angle in Committing to Accessibility in Your SEO Content Strategy: What Changes When You Take It Seriously, which is a useful prerequisite if you’re still persuading colleagues that accessibility belongs inside content and search work at all, not just in legal reviews (/blog/committing-to-accessibility-in-your-seo-content-strategy-what-changes-when-you-take-it-seriously/).
As a prerequisite to this decision, Committing to Accessibility in Your SEO Content Strategy: What Changes When You Take It Seriously explains the adjacent issue in more detail.
Here, we’ll assume you already care—and focus on why the fixes won’t stick.
2. Symptom checklist: are you stuck in the redesign-only accessibility cycle?
Before you plan another project, diagnose how your organization actually runs accessibility today.
Use this checklist as a governance mirror, not a compliance scorecard.
Ownership symptoms
- Owner of last resort: When something breaks, everyone sends it to “the web team,” but no one can name a person or role explicitly accountable for accessibility.
- Vendor-only expertise: The only people who understand accessibility criteria work for your agency, not your organization.
- Frozen responsibility: The person named as “accessibility lead” in the redesign RFP has since moved roles, but your docs still point to them.
Workflow symptoms
- No content checks: New pages, blog posts, and landing pages can be published without any accessibility review—manual or automated.
- Template drift: Editors can bypass templates or add raw HTML that breaks headings, landmarks, or labels.
- Rush exceptions: High-pressure campaigns often get a pass on accessibility checks “to make the date.” No one circles back later.
Funding and planning symptoms
- Redesign-only budget: Accessibility hours only appear in project SOWs, not in any ongoing budget line for content or SEO work.
- Audit spikes: You run audits right before or after a big launch, then nothing for a year—or longer.
- Invisible maintenance: If someone does accessibility work between redesigns, it’s hidden inside general “content updates” time, with no explicit mandate.
Measurement symptoms
- No regression tracking: You don’t keep a running list of issues found, fixed, and re-opened.
- Support noise: Support and sales escalate user complaints, but you don’t tag which ones are accessibility-related.
- Flat reporting: Accessibility gets a single line on quarterly reports (“We’re compliant”) with no operational metrics.
If three or more of these feel familiar, you’re not dealing with a one-off project gap. You’re living inside a redesign-only accessibility model.
3. Why barriers keep coming back: governance gaps, not just bad implementation
When we look at recurring accessibility issues during audits or support reviews, the same underlying causes show up.
1) No clear owner with decision rights
If no one is authorized (and expected) to say, “This launch waits until accessibility checks are done,” then accessibility is optional every time schedules get tight.
That’s not a knowledge issue. It’s a decision-rights issue.
2) Content workflows that ignore structure
Most accessibility guidance during redesigns focuses on code and templates. But after launch, your biggest source of risk is content:
- Headings that become visual styling instead of logical structure.
- Links like “click here” or “learn more” that give no context.
- Images added without alt text.
- Long-form resources shipped only as inaccessible PDFs.
If your content workflow never asks, “Does this preserve structure and meaning for assistive tech?” then every new campaign has a chance to introduce fresh barriers.
3) Semantic Decay between redesigns
Best Website uses the term Semantic Decay for what happens when a site’s structure and language drift away from the patterns that originally made it clear and authoritative.
You can see Semantic Decay in both SEO and accessibility:
- SEO impact: headings, internal links, and page relationships become noisy, so search engines lose a clean sense of your topical authority.
- Accessibility impact: the same structural decay breaks landmarks, headings, and relationships that assistive tech relies on.
Redesign accessibility work usually strengthens semantics at launch: clear headings, consistent navigation, descriptive labels. Governance gaps then allow everyday edits to erode those semantics until your “accessible redesign” is only accessible on a handful of legacy pages.
4) Misaligned incentives between teams and vendors
Agencies are incentivized to ship a clean build and pass an audit. Internal teams are incentivized to move campaigns fast.
Without a shared operating model, you get:
- Templates that are technically solid but easy to misuse.
- Editors who aren’t trained or supported to maintain accessibility.
- Product or sales teams spinning up unmanaged microsites on different stacks with no guardrails.
In other words: the implementation might have been fine. It’s the ongoing system that’s broken.
4. Three paths you can take: project, policy, or ongoing ownership
Once you see the governance pattern, the next decision is what kind of intervention you actually need.
Think of three paths:
- Project – You need targeted remediation work.
- Policy – You need rules and standards that change behavior.
- Ongoing ownership – You need someone accountable for accessibility as part of how the website runs.
Each has its place—but only one fixes the redesign-only loop.
Path 1: Project – when a focused fix is enough
A project is appropriate when:
- You have a specific part of the site with known issues (e.g., legacy forms, a resource hub full of old PDFs).
- Your content workflows are mostly healthy, but one area slipped through.
- You have clear ownership, but the team needs specialized implementation help.
In this case, a short engagement to repair templates, refactor components, or clean up a defined content set can make sense.
However, if you know new issues keep appearing in random places, a project-only response is like mopping the floor while the pipe is still leaking.
Path 2: Policy – when you need guardrails but can execute internally
Policy is appropriate when:
- You can assign an owner who has genuine authority.
- You have the internal skills to implement accessibility but no consistent rules.
- Teams are willing to change how they work, but they lack clear expectations.
You might focus on:
- A content style guide that covers headings, links, and media.
- An authoring guide for your CMS.
- A simple checklist for new page types and campaigns.
Policies help, but they still rely on people remembering and caring. If accessibility isn’t part of how work is planned, approved, and measured, policy becomes another PDF no one opens.
Path 3: Ongoing ownership – when the system, not the sprint, is the issue
Ongoing ownership is necessary when:
- Accessibility issues appear in support tickets and sales conversations every quarter.
- You’ve done audits before, but the same categories of problems keep coming back.
- No one’s performance expectations or budgets explicitly mention accessibility maintenance.
In that situation, you’re facing a structural ownership gap. What you need is a way to:
- Assign named accountability for accessibility within your digital team.
- Embed checks into content and SEO workflows instead of bolting them on.
- Track regressions as a governance signal, not just bugs to close.
That’s where treating accessibility as part of your ongoing SEO & Content Strategy—not a separate compliance initiative—starts to pay off.
If you’re weighing which path you’re on, another article in this archive, Deciding When Accessibility Fixes Belong in Content vs. Code on a Revenue-Critical Website, can help you expand the analysis by separating structural code fixes from content and governance work (/blog/deciding-when-accessibility-fixes-belong-in-content-vs-code-on-a-revenue-critical-website/).
5. Designing accessibility ownership into content and SEO workflows
Let’s assume you’ve recognized the pattern: your problem is ongoing ownership, not just another audit. What has to change this quarter to make regressions less likely?
You don’t have to rebuild your org chart. You do need to design accessibility into the way work flows.
We use a simple model: Owner, Workflow, Metrics.
Owner: who can say “not yet”?
Start by naming a role, not a hero.
- Accountability: Make one role (e.g., Head of Digital, Web Product Owner, or SEO & Content Lead) accountable for accessibility as part of site quality.
- Decision rights: Document that this role can pause launches when critical barriers are found—and will be supported when they do.
- Support: Give them access to specialized help for audits or training. Don’t expect them to be a solo expert in every WCAG nuance.
Without this, every other idea in this section becomes “optional if schedule allows.”
Workflow: where accessibility fits into real work
Next, adjust your workflows so accessibility is checked as part of the job, not as an afterthought.
In support work and redesign planning, we’ve noticed a few high-leverage points:
-
Briefs and requirements
Add explicit accessibility expectations to campaign briefs and page requirements:- What audiences and assistive technologies are we considering?
- What types of content (video, forms, documents) need accessible alternatives?
-
Templates and components
Lock as much accessibility into your components as possible:- Headings that enforce logical hierarchy.
- Buttons and links with clear default styles and ARIA attributes baked in where appropriate.
- Forms with reusable, labeled input patterns.
Components don’t solve everything, but they remove the need for editors to remember dozens of details.
-
Publishing checks
Add a short, repeatable check before anything goes live:- Run an automated scan on the new page.
- Confirm headings and link text make sense out of context.
- Confirm alternative text exists (and is meaningful) for non-decorative images.
This doesn’t need to be a 30-minute ritual. A disciplined five-minute checklist can prevent a lot of regressions.
-
Navigation and internal links
Keep an eye on changes to navigation and key internal links. If you’re curious how internal linking itself can become a governance and path-blending problem, How to Use Internal Links to Keep Audit, Retainer, and Project Paths From Blending Together offers a contrasting angle on how link structures either support or confuse governance expectations (/blog/how-to-use-internal-links-to-keep-audit-retainer-and-project-paths-from-blending-together/).
These workflow changes fight Semantic Decay directly by keeping structure, labels, and relationships in focus every time content moves.
Metrics: how you’ll know it’s working
Finally, treat accessibility as something you measure, not something you “trust.”
For a single quarter, track:
- Issue sources: For every accessibility issue logged, note whether it came from content changes, code changes, or third-party tools.
- Reopened tickets: Watch how many accessibility-related tickets reopen after a “fix.” A rising reopen rate is often a governance issue, not a technical one.
- Campaign reviews: Track how many major campaigns ship with at least a minimal accessibility review logged.
Another piece in this archive, Why Your Website Support Tickets Keep Reopening (And What That Says About Your Governance), escalates this idea and shows how recurring tickets—accessibility or otherwise—signal deeper ownership gaps (/blog/why-your-website-support-tickets-keep-reopening-and-what-that-says-about-your-governance/).
With even a month or two of this basic tracking, you’ll have evidence for whether your problem is mainly code, content, or process. That matters when you’re deciding what to fund next.
When we design this kind of model with clients through SEO & Content Strategy work, the goal is simple: make accessibility visible and governable, so it can survive real-world publishing pressure (/services/seo-content-strategy/).
To operationalize this decision, how our SEO & Content Strategy work supports this decision explains the adjacent issue in more detail.
6. How this connects to your broader accessibility and governance roadmap
This article sits alongside other accessibility pieces in the archive as the governance sibling: it assumes you’ve already accepted that accessibility belongs in your strategy, and it asks whether your operating model matches that belief.
If you’re still getting executive buy-in, start with the Committing to Accessibility in Your SEO Content Strategy article mentioned earlier; it serves as a prerequisite mindset shift that connects accessibility to traffic, conversion, and brand trust rather than only to legal risk.
From there, this piece adds the next layer: treating recurring failures as symptoms of governance gaps—funding, workflows, and decision rights—rather than as isolated mistakes.
If you want to explore more topics around accessibility, UX, and SEO through that governance lens, the Accessibility articles hub collects related posts so you can see how issues like search, support, and structure interplay over time (/blog/topics/accessibility/).
For a deeper treatment of this decision, related Accessibility articles guidance explains the adjacent issue in more detail.
A useful way to think about the archive is as an internal “relationship map”: some articles act as prerequisites (mindset), others expand a concept (like Semantic Decay across SEO and accessibility), and others operationalize it (like the internal linking and governance posts). Together, they support a more mature model of web ownership.
7. Decision recap: what to do this quarter if you’re redesign-only today
If accessibility work only appears during redesigns, you’re not just under-compliant—you’re running a website that lets barriers and Semantic Decay rebuild themselves between projects.
This quarter, three decisions matter more than another giant checklist:
- Name an owner with real authority. Decide which role is accountable for accessibility across the site, not just during projects. Put it in their objectives and support them when they delay launches to protect users.
- Embed accessibility into content and SEO workflows. Update briefs, templates, and publishing checks so accessibility is part of how work moves, not a late-stage patch.
- Measure regressions as a governance signal. Track where new issues come from and which tickets reopen. Use that data to decide whether you need targeted remediation, better policies, or ongoing strategic support.
If you leave things as they are, the pattern is predictable: redesign-only accessibility → temporarily accessible templates → uncontrolled content and navigation changes → Semantic Decay and new barriers → user frustration, support load, and legal exposure → another expensive project that fixes symptoms but not ownership.
If you’re seeing that pattern on your own site and don’t have the internal capacity to design the ownership, workflow, and measurement changes, it’s time to treat accessibility as part of how your digital channels are governed. A focused SEO & Content Strategy engagement can map where accessibility really breaks (content vs. code vs. process), define decision rights, adjust briefs and templates, and create a practical measurement plan so regressions become rare instead of routine (/services/seo-content-strategy/).
And if you’re already convinced this governance gap is hurting users and revenue but need to pressure-test what an engagement would look like in your specific environment, start a conversation with us about your current redesign cycle and support patterns so we can see whether strategic accessibility ownership work would pay off for your team (/contact/).