The short version: Installing accessiBe takes about fifteen minutes of actual setup work, but doing it means auditing your site first, configuring the widget settings deliberately rather than leaving defaults, and accepting that the tool is a layer on top of your site, not a replacement for fixing broken code underneath it. Get this wrong and you end up with a widget icon that looks reassuring but doesn't do much.
What accessiBe does before you install it
accessiBe is an AI-powered accessibility widget. You drop a line of JavaScript into your site, and it scans your pages, adjusts things like contrast, font sizing, keyboard navigation and screen reader compatibility, and gives visitors a small accessibility menu to customise how they view your site.
What it is not is a guarantee of ADA compliance. I want to say that plainly before we get into the steps, because most guides on this topic skip past it. Overlay tools, and accessiBe is the best known of them, have been criticised by accessibility advocates and organisations who argue that widgets layered on top of inaccessible code can mask problems rather than fix them, and in some documented cases make screen reader navigation worse, not better. There have been lawsuits against sites running accessibility overlays, including accessiBe itself. If you want the detail on this, I covered it in my accessiBe review on ADA compliance.
None of that means skip it. It means install it as one layer of a real accessibility approach, not the whole strategy.
Step 0: audit before you touch the install script
Before accessiBe goes anywhere near your site, spend thirty minutes checking the basics yourself. Tab through your homepage and checkout flow using only your keyboard, no mouse. Check whether your images have alt text. Check whether your forms have visible labels, not just placeholder text that disappears when you click in.
Say you run an online homeware shop on Shopify with around 600 product pages. Before installing anything, you'd want to know that your product image galleries don't have alt text, your checkout button relies on colour alone to show it's active, and your mobile menu can't be opened with a keyboard. Those are code-level problems. accessiBe's widget will help some visitors work around them, but it won't rewrite your theme's HTML for you. Knowing this upfront changes what you expect from the tool and stops you being surprised six months in when a complaint still comes in.
Step by step: installing accessiBe
- Step 1: Choose your plan. accessiBe's pricing is tiered by number of pages and monthly traffic. Smaller sites typically sit in the tens of pounds a month, larger ecommerce catalogues climb into the hundreds. Pick the tier that matches your actual page count, not what you think you'll grow into. You can upgrade later in minutes.
- Step 2: Create your account and add your domain. You'll be asked for your website URL and basic business details. accessiBe generates a unique embed script tied to that domain.
- Step 3: Install the script. Copy the JavaScript snippet from your dashboard and paste it into the head section of your site, ideally through your theme's header file, your CMS's custom scripts area, or a tag manager like Google Tag Manager if you already use one for other tracking. On WordPress, most people drop it in via the theme editor's header.php or a lightweight header-and-footer plugin rather than touching core files directly.
- Step 4: Verify the widget appears. Reload your homepage and look for the small accessibility icon, usually bottom left or bottom right of the screen. If it's not there, clear your cache first; caching plugins are the most common reason the script doesn't show up straight away.
- Step 5: Let the AI scan run. accessiBe's automated scan typically takes 24 to 48 hours to fully process a site and assign the right adjustments to each page. Larger sites with more product pages or dynamic content take longer on the slower end of that window.
- Step 6: Configure the widget settings yourself. Don't leave this on default. Go into the dashboard and set the widget's position so it doesn't sit over your checkout button or cover a chat widget you already use. Choose a colour that's visible against your brand palette but doesn't clash with your logo. Review which accessibility profiles are switched on by default, things like motor impairment, epilepsy-safe mode, ADHD-friendly mode, and turn off any that don't suit your audience.
- Step 7: Add the generated accessibility statement. accessiBe produces a statement describing what's been done to your site. Add it to your footer, linked clearly, usually titled "Accessibility Statement." This matters for legal documentation as much as for visitors.
- Step 8: Test it yourself, manually. Open your site and use only the keyboard: tab through the menu, the forms, the checkout. Turn on a free screen reader (NVDA on Windows, VoiceOver on Mac) and listen to how your site reads out loud. If something sounds wrong, it's a code issue the widget hasn't touched, not a widget bug.
- Step 9: Fix what the widget can't. Go back to your developer with the specific issues the manual test surfaced. Missing alt text, unlabelled form fields and colour-only indicators need fixing in your actual code, not patched over by the overlay.
- Step 10: Check the dashboard monthly. accessiBe re-scans periodically and flags new issues as you add pages or products. Treat this like you would a security scan, something you glance at monthly, not something you set up once and forget.
A worked example: a small service business site
Say you run a local accountancy firm with a twelve-page WordPress site: homepage, services, about, team, contact, and a handful of blog posts. You'd sign up for accessiBe's entry-level tier, which covers you comfortably at that page count. Installation through a header-and-footer plugin takes about ten minutes. The AI scan finishes within a day because the site is small. You spend twenty minutes configuring the widget position so it doesn't overlap your phone number in the top corner, and another twenty testing with a keyboard, where you discover your contact form's submit button isn't reachable by tabbing because of a custom CSS override your old developer added years ago. You send that single fix to whoever maintains your site. Total time from sign-up to a improved, tested site: about two hours spread over two days, most of it waiting for the scan.
That's the realistic timeline. Anyone telling you it's a five-minute set-and-forget job is selling you something.
Where accessiBe fits with everything else
If you're building a case for why accessibility matters to your board or your clients, pair the technical install with something written for people, not developers. My piece on what a product review involves is a useful companion if you're deciding whether to publish your own write-up of the tool for customers, since transparency about what you've done and what's still in progress tends to land better than silence or overclaiming.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
And if you want the fuller breakdown of where accessiBe sits legally, including the overlay criticism in more depth, I've gone through it in my other accessiBe ADA compliance review.
What I'd tell you to skip
Don't skip the manual keyboard and screen reader test. It's the single step that separates a tidy accessibility icon from a site that works better for disabled visitors. Don't skip reading your accessibility statement before publishing it, because an inaccurate statement is worse for you legally than no statement at all. And don't assume one install covers you forever. Websites change constantly, new pages, new forms, new plugins, and each one needs the same scrutiny the original site got.
Frequently asked questions
Does installing accessiBe make my website ADA compliant?
No. accessiBe improves accessibility and supports your compliance efforts, but it doesn't guarantee legal compliance on its own, and several lawsuits have involved sites running accessibility overlays. Treat it as one part of a wider accessibility approach that also includes fixing your underlying code.
How long does accessiBe take to install?
The script installation itself takes about fifteen minutes. The AI scan that follows typically runs for 24 to 48 hours depending on your site's size, and real testing afterwards adds another hour or two.
How much does accessiBe cost?
Pricing is based on page count and traffic. Small sites sit in the tens of pounds per month, while larger ecommerce sites with hundreds or thousands of pages pay considerably more. Always check current pricing on the plan that matches your actual site size, not projected growth.
Can I use accessiBe alongside manual accessibility fixes?
Yes, and you should. Use accessiBe for the widget-level adjustments and the ongoing scanning, and have a developer fix structural issues like missing alt text, unlabelled forms and poor colour contrast directly in your code. The combination is far stronger than either on its own.
