This post was inspired by a recent project where I audited a website that hadn’t been updated in more than 20 years. The layout, navigation, and design all felt outdated—and so did its approach to accessibility..

During testing, it became clear that most accessibility issues were not easy to fix. The outdated code made even simple improvements—like adding labels or keyboard support—unreliable. I completed the audit and shared my recommendations, but it didn’t seem likely to make a real difference without a full rebuild.

Accessibility Is More Than Code – It’s About Usability Too

Accessibility was only part of the problem. The entire user experience felt outdated. Buttons and links were hard to identify, features weren’t intuitive, and the design hadn’t kept up with modern standards. Even the language felt outdated—clunky and hard to follow, not how people speak or search online.

Here’s the key point: even if the site had passed all accessibility checks, I still wouldn’t want to use it. As a user, the experience didn’t make me want to stay or trust the service. True accessibility must go hand in hand with good usability and a design that feels modern, clear, and user-friendly.

Why Old Code Can’t Keep Up with Modern Accessibility

Updating a website from 2005 to meet today’s accessibility standards is rarely practical. Modern accessibility relies on coding tools and techniques that didn’t exist 20 years ago.

Older websites often use outdated methods like table-based layouts, basic HTML without meaning, inline styling, and early JavaScript with little or no ARIA support. These foundations make accessibility fixes harder and often lead to messy workarounds.

Since then, HTML and ARIA standards have improved. They now include meaningful page elements, better form inputs, and built-in controls for media. Modern JavaScript also supports interactive features that work well with accessibility—something older code simply wasn’t designed for.

Accessibility guidelines have come a long way. WCAG 2.0 introduced clear rules in 2008, and later versions—2.1 and 2.2—added important updates for mobile use and people with cognitive disabilities. Older websites were never built with these standards in mind.

Responsive design is now essential, especially with the rise of mobile. But 20 years ago, it wasn’t even on the radar. Without it, content is hard to read, buttons are too small, and navigation doesn’t work well on phones. This isn’t just frustrating—it creates real barriers for people using assistive technologies on mobile devices.

When It’s Time to Rebuild

If your website was built around 2015, there’s still time to improve accessibility with a few focused updates. But technology moves fast—wait too long, and a full rebuild may become unavoidable.

If your website is nearly 20 years old—especially one with features like online banking, shopping, or booking—it’s time to rethink patching. A full redesign, with accessibility planned from the start, is usually the smarter choice.

Think of it like an old car: repairs work only while parts are still available. In digital terms, once your code can’t support accessible, stable solutions, no fix will be enough.

That’s the reality many organizations face. Accessibility isn’t just about checking boxes—it’s about creating a reliable, inclusive experience. And sometimes, the only way forward is to start fresh. Not just for compliance, but for the sake of your users and your long-term digital future.

Ready to Start Fresh?

If you’re running an older website and wondering whether it’s time to rebuild, start by asking the right questions:

• Does your current codebase support modern accessibility practices?
• Are mobile users able to navigate easily?
• Would you feel confident using your own site as a customer?

If the answer is no, I can help. Whether you’re looking for an accessibility audit or support in building a site that’s designed to be inclusive from the start, reach out. Let’s build something better together.