Sometimes when consulting with clients, we’ll recommend they skip audit and remediation and go straight to a site rebuild. Here are the three main reasons why:
No-Code Access Platform
There are some site builders or site building platforms that don’t allow full code access. This limits our ability to make the fixes necessary – if we don’t have complete access to the code, there’s a cap on what we can do.
Take the example of a site builder like Square Space or Godaddy. These provide website owners with a lot of customization, but because they simplify the process of building a website, they can also take away some of the code access we need.
The end result for clients is we recommend a site rebuild, typically on WordPress.
Outdated Technology
Every now and then a client will come to us with a website that was literally created 10+ years ago. The site will not only be riddled with accessibility issues, but the fixes will be much more work than if we just rebuilt from the ground up.
Plus, for the client, they receive the huge value add of a completely new and modernized redesign.
Too Many Accessibility Issues
It’s not just old websites, newer websites can be bogged down by hundreds of accessibility issues – to the point where it may not be worth it to remediate everything.
When the number of issues is so voluminous and also diverse that we’d spend more time on auditing and fixing issues, then we advise the client of both options and let them decide. One counter to this is if the SEO is really good, then it’s best to continue with remediation.
Summary
Of course, cost is a driving factor in the last two reasons for a site rebuild. And no-code access arrives at risk and an incomplete project. There’s always a cost-benefit analysis that takes place and sometimes a complete rebuild is the right choice.
If you need help with website accessibility and/or following best practices for ADA compliance, we’re happy to help. Just send us a message and we’ll be right back with you.
