How Long Does It Take to Make a Website Accessible, and What It Really Depends On
The short answer: How long does it take to make a website accessible? Anywhere from one week to three months. It really depends on how complex the site is, how many templates it has, which processes run on it, and everything else that affects how long the manual audit takes.
If you’ve already come across a company promising you an accessible website in a few minutes, that should set off a red flag. It doesn’t make sense. Not technically, and not in terms of fully meeting the standard’s requirements after a few minutes of work.
What affects how long it takes to make a website accessible?
Broadly, there are three main things that affect the timeline.
The first, and the most significant, is the number of templates on the site. A landing page, or a project site with only one unique template, takes less time to audit than an e-commerce site. An e-commerce site usually has 15 to 25 unique templates, including the purchase flow, and that takes more attention and more time to audit for accessibility.
The second is how complex each template is. If it’s a simple brochure site that’s basically a digital business card, the process moves much faster, because there are no complex components. On the other hand, if it’s an app, or an e-commerce site with a checkout and a shopping cart, the processes are more complex. They need more attention and more serious testing, so the process usually takes longer.
The third is how complex the components inside each template are. If it’s a simple template that shows information, images or a gallery, the check is shorter. If it’s a flow with calculators, filters or more complex components, it needs a more careful and thorough check with a screen reader.
Those are the three things that affect how long it takes us to make a site accessible.
Another thing that matters, on the technical side, is the development itself. If it’s a complex system, the developers have to make more complex adjustments, and sometimes more creative ones: on one hand without hurting how the site looks, and on the other hand delivering a full solution to the standard’s requirements and to screen reader support. The more complex the system, the longer the audit takes, and the more time the development team needs to make the fixes based on what we mapped.
What does the timeline actually look like?
Let’s simplify what the timeline for making a website accessible is made of. There are a few stages that run through the process.
The first stage is reviewing the templates. We go through the site, count how many unique templates it has, and check which steps a user goes through from the moment they land on the site until they leave. In other words, the full journey, end to end.
Take an e-commerce site, for example. We map the journey like this: the user lands on the site, picks the category they want to buy from, goes to a product, chooses it, adds it to the cart, fills in a registration form so they can pay, goes to the payment page, chooses a shipping method, fills in the shipping details, and confirms the payment, including entering their credit card details. Those are all the steps a user goes through on an e-commerce site.
We go through every one of these steps, map them precisely and document them with screenshots, based on the official report format published by Israel’s Ministry of Justice. We hand the report, with our precise instructions, to the development team that maintains the site, or to our own development team if the client doesn’t have one.
They make the fixes with our support. We help with creative solutions to cut the time they need and reduce the total development hours. Then we run a re-test and confirm, against the report, that everything handled along the way was actually done right. And of course, we write a custom accessibility statement that reflects the process, the time it took and the nature of the service.
Why can a 10-page site and a 1,000-page site take the same time?
Does a website with only 10 pages take the same time to audit and make accessible as a website with 1,000 pages? Like I said, the number of pages isn’t what matters here. What matters is the number of templates on the site.
Let me give you an example, back to the e-commerce site. If an e-commerce site has 1,000 products, but all of them are built on exactly the same template, the same page structure, then what we need to do is audit that specific template, not every page. Checking every page usually isn’t possible or sensible anyway. So if you have many pages built on the same template, the timeline will definitely be shorter, because we audit that template and not every single page.
So if you’re building a website, here’s my tip, for accessibility, for user experience, and for crawling by Google and other search engines: build your site with as few templates as possible, and let each template cover as many pages as possible. That way your changes take effect faster, fixes and updates are quicker, and the impact runs across every page on the site. You won’t have to spend hours going over the whole site page by page, because you only need to check those templates.
What makes the process take longer?
So what stretches the timeline? Which things have we seen over the years that make the process take much longer?
The first and biggest one is a development team, or a developer, who isn’t available to make the required accessibility fixes. The developer we reach out to and support, but who takes forever to reply, drags their feet on the report, and doesn’t really want to understand the process. When developers aren’t ready to make the fixes, it definitely takes a long time.
The second is how the site is built. Is it built on a focused set of templates, or spread across all kinds of templates? Is it a very old site, built on old code, old processes or old components that take a lot of time to deal with? That has a big impact.
Other things: Are there lots of PDF documents published on the site, like tenders and meeting minutes? Those also need to be mapped and checked to make sure they were uploaded in an accessible way. Are there forms? Are there add-ons installed on the site, like chatbots or external tools embedded in it, which also need a full accessibility check, or a request to the company providing them so they become accessible? Or does the site need another round of accessibility testing, meaning we can see that two audits won’t be enough because it’s a complex site with a lot of issues? That can definitely affect the timeline too.
I got a demand letter. How much time do I have?
This part is for sites that fall under Israeli accessibility law.
Another question we hear from a lot of people who received a warning letter or a notice before legal action, and don’t know how much time they have. In some cases, there may be a 60-day window to make the accessibility fixes. Note that those 60 days apply only when the issue is a deviation from the standard’s requirements, not when the site wasn’t made accessible at all. In other words, if you really did make the site fully accessible, and the gaps are only on one or two specific pages, you may be entitled to those 60 days to fix the issue. But if you never went through an accessibility process and only installed an accessibility plugin, and no real time or effort went into making the site itself accessible, those 60 days aren’t on your side, and your exposure is immediate.
So in any case, I recommend reaching out to us with the letter you received. We’ll guide you through what needs to be done, how to make the fixes, and how to shorten the process so it’s as fast as possible.
Does an accessibility plugin shorten the process?
Another topic worth talking about: does an accessibility plugin shorten the process? The answer is a clear no. An accessibility plugin solves four or five issues out of the 47 criteria listed in the Israeli standard’s requirements. It doesn’t really shorten the process. It can affect the visual side and save you from changing the colors on your site, but not much beyond that. So the short answer is that an accessibility plugin doesn’t shorten the process and doesn’t reduce the time it takes from start to finish. The goal is to make the site accessible at the code level and make sure things are actually done right. If you want to understand what a plugin really does and what it doesn’t solve, I wrote about it in why accessibility overlays fall short.
Four tips that can shorten the process
So after going through all of this, let’s see how you can cut the working time and the accessibility process, so your site is accessible in the shortest time possible. These are practical tips: if you apply them from the start, you’ll see the process done fully and in an orderly way.
Check whether your development team knows an expert accessibility consultant. If you have a development team supporting you through making the site accessible, talk to them and find out whether there’s an expert accessibility consultant they’ve already worked with on past projects. The advantage here is that once they have an expert consultant, they know how to talk to them, they get how they think, they know exactly what they require, and they can shorten the process like crazy. I can tell you from past experience: when I worked with web accessibility companies and we got all kinds of new clients through them, the processes moved fast. We got sharper, we built a strong working relationship between me and the development team, and we definitely got to a point where the process was done very quickly and professionally. So the first tip: check with the development team, or the developer who will make your site’s accessibility fixes, whether they know an expert accessibility consultant who has taken them through a full process. Not just a plugin installation, which takes no skill at all, just installing an automatic component.
A Zoom call over the report with the accessibility consultant. Once you hand the full, comprehensive accessibility audit report to the developer, ask the expert accessibility consultant to set up a Zoom call and go through the table together. The Israeli standard’s table is very long, tedious and detailed. An experienced consultant can join a short call with the development team, map out the gaps for them and explain which columns to focus on. That cuts the time they spend on the table, and they get it done much faster. The big advantage here, beyond making the process easier, is that the development team will also give you an estimate with fewer development hours. Because if you just send them a table, they panic and quote you a lot of hours, when in practice far fewer hours are needed. So the guideline is to have the expert consultant go over it with the team first, make sure they understand the form, give them the key points on what’s more complex and what’s less, and handle it as professionally as possible. That gives you peace of mind, maximum speed, and a lower hours estimate from the team working on the project.
Split the work between your developers and your content editors. The Israeli standard’s requirements cover technical issues and issues related to content or content entry. If you take the table and an expert accessibility consultant tells you what’s relevant to development and what’s relevant to content, that can definitely shorten the process, because you work in parallel. The technical issues are handled by the development team, and the content issues are handled by the team that edits and uploads content to the site: images, headings, paragraphs, articles. It’s a waste to have the development team handle those. It’s better to cut costs and hand this to whoever edits the site’s content day to day, with the accessibility consultant guiding them on what to do. The big advantage of splitting the work between the two is that both can work in parallel, and that significantly cuts the time it takes to make the site accessible and meet the requirements, in line with the accessibility regulations and the report you received from the expert consultant.
Have one point of contact. Appoint one person to work with the expert accessibility consultant and with the development team or whoever edits the site’s content. I can tell you that with clients who come to me, I take the keys and guide them from one end to the other. At the end of the process they get the accessibility statement and the comprehensive report, complete and in order, after our re-test. We don’t need them in the loop: we learn the business, understand what it wants to define, what the site’s process and goals are, and we run the process with the development team or the content managers. Nobody inside the business has to manage it or waste time on it, because we take it and handle it end to end. We can also tell what the development team is asking for, whether the hours they’re requesting are too high, and how to bring them down. That’s how we save the client money along the way. So it’s important to appoint one person who can manage the process from every direction, so you’re covered and don’t get lost in it.
If you have no idea how to approach the process, I invite you to reach out to us. We’ll do a free initial check, explain the right process for you, and give you a quote within one business day. We’ll get you the solution in the shortest time possible, and most importantly, at a full level, in line with the accessibility requirements. We won’t throw a plugin at you to install and promise you the world. That’s not us. We’re here to give you a full solution, even if it takes a bit more time. It’s a manual check and a process done with a screen reader. It can take time, but that way you know you’re not exposed, and you can sleep well at night, without having just installed some accessibility plugin.
If you’re looking for someone to make your website accessible, here’s our website accessibility service.
FAQ
Yes, but only very simple sites. If you have a complex site and a company promises to make it accessible in hours or minutes, that should set off a red flag. It doesn’t make sense to audit a site, handle the technical fixes and prepare an accessibility statement, all in a few minutes. So yes, a week is possible, but only for very simple sites.
That depends on the type of site, how complex it is and what functionality it has. Generally, we can work on production, meaning the live site, and there’s no need to take it down, so your SEO doesn’t take a hit. But again, we build the process according to the type of site and how much visibility it has in search engines.
The person who works with us doesn’t need to be very involved. They need to give us the contact details of the content person and the technical developer, and we run the whole process without requiring them to be in the loop. There’s no need to appoint someone on their behalf, and that also shortens the process. But if you still want to be in the picture, you can appoint one person who understands both the technical side and the business side, who can follow the project and know exactly what they need to do.
This website uses essential cookies to operate and, with your consent, statistics cookies (Google Analytics). For more details, see our Privacy Policy.