accessiBe review: does the accessibility overlay work?
Web accessibility is becoming harder to ignore. The Equality Act 2010 already requires UK businesses to make reasonable adjustments for disabled users, and the European Accessibility Act is pushing standards further for businesses that serve EU customers. For many small businesses, the question is not whether to improve accessibility, but how to do it affordably.
accessiBe offers an AI-powered overlay that promises to address WCAG 2.1 AA compliance through a single line of JavaScript. It is one of the most well-known accessibility overlay tools, and also one of the most debated. This review covers what it does, the genuine controversy around its approach, and when it makes practical sense for UK businesses.
What accessiBe does
accessiBe works by adding a JavaScript widget to your website that uses AI to analyse and modify your site's front-end code in real time. The overlay provides two main functions:
- Automated background adjustments: The AI scans your pages and adds missing ARIA attributes, generates alt text for images, fixes keyboard navigation issues, adjusts form labels, and modifies heading structures. These changes happen automatically without visible user interaction.
- User-facing accessibility interface: A widget icon (typically in the corner of your site) opens a panel where visitors can adjust settings including text size, contrast, cursor size, line spacing, content highlighting, and screen reader optimisation.
Installation is straightforward. You add a single script tag to your site's header, and the overlay activates within 48 hours after the AI completes its initial scan. The system re-scans your site regularly to account for content changes.
The overlay debate: both sides
Accessibility overlays are genuinely controversial, and it would be irresponsible to review accessiBe without addressing this directly. Here is what both sides argue.
The case against overlays
Many accessibility advocates, disability organisations, and web developers have raised serious concerns about overlay tools. The core arguments are worth understanding:
- Interference with assistive technology: Screen reader users have reported that overlays can conflict with their existing tools, sometimes making navigation worse rather than better. Overlays modify the DOM in ways that can confuse assistive technologies.
- False sense of compliance: An overlay does not fix the underlying accessibility issues in your code and content. If your site's structure is fundamentally inaccessible, an overlay applies surface-level fixes that may not withstand scrutiny.
- Legal risk: Several businesses using overlays have still faced accessibility lawsuits, particularly in the US. An overlay alone may not constitute the reasonable adjustments required under the Equality Act 2010.
- User experience concerns: Some disabled users find the overlay widget itself intrusive or patronising, preferring that sites be built accessibly from the start.
The case for overlays (particularly for SMEs)
The counter-arguments focus on practical reality for small businesses:
- Cost of alternatives: A full manual accessibility audit and remediation for a small business website can cost £2,000-10,000 or more. Many SMEs simply cannot afford this. An overlay at $490 per year provides some improvement where the alternative is doing nothing.
- Speed of implementation: Manual remediation takes weeks or months. An overlay activates within days, providing immediate improvements while longer-term fixes are planned.
- Continuous monitoring: accessiBe's AI re-scans pages regularly, catching new accessibility issues as content changes. Manual audits are point-in-time snapshots.
- Some improvement is better than none: For the millions of small business websites with no accessibility measures at all, an overlay represents a meaningful step forward.
Pricing
accessiBe costs $490 per year (roughly £390) for a single website with up to 1,000 unique pages. Larger sites are priced higher. This is an annual subscription, not a one-off payment, so the ongoing cost over three years is approximately £1,170.
Compared to manual remediation, this is significantly cheaper in the short term. Compared to doing nothing, it is an added cost that many small businesses struggle to justify. The value depends entirely on your perspective: is $490 per year worthwhile for the level of improvement an overlay provides?
Who accessiBe is for
accessiBe makes the most practical sense for:
- Small businesses that cannot afford manual remediation and want to demonstrate they are taking accessibility seriously
- Businesses with older or template-based websites where rebuilding for accessibility is disproportionately expensive
- Organisations that need a quick starting point while planning longer-term accessibility improvements
- Sites that change content frequently and benefit from automated re-scanning
Limitations
To be clear about what accessiBe does not do:
- It is not a substitute for building an accessible website from the ground up
- It does not guarantee legal compliance under the Equality Act 2010 or the European Accessibility Act
- It cannot fix deeply structural accessibility issues in your site's architecture
- It does not address accessibility in PDFs, videos, or other non-HTML content
- It may not satisfy the requirements of public sector accessibility regulations
Check your site's accessibility status
Run a free compliance scan to see how your website scores on accessibility, privacy, and cookie consent.
Scan your website free →Our verdict
accessiBe
Pros:
- Fast implementation via a single script tag
- Significantly cheaper than manual accessibility remediation
- AI re-scans catch new issues as content changes
- User-facing widget provides genuine customisation options
- Demonstrates intent to improve accessibility
Cons:
- Controversial among accessibility advocates and disabled users
- May interfere with existing screen readers and assistive tools
- Does not fix underlying code-level accessibility issues
- Annual subscription adds up over time
- Not a guaranteed path to legal compliance
If your budget allows, consider combining an overlay with targeted manual fixes for your most critical pages. An accessibility statement on your site explaining your approach and inviting feedback is also good practice under the Equality Act 2010, regardless of which tools you use.
Frequently asked questions
Does accessiBe make my website fully WCAG 2.1 AA compliant?
accessiBe claims to address WCAG 2.1 AA requirements through its AI-powered overlay, but it cannot guarantee full compliance. The overlay handles many adjustments automatically — alt text generation, keyboard navigation fixes, ARIA attribute additions — but some accessibility issues require changes to your underlying code and content structure. Accessibility experts generally agree that overlays should be considered a layer of improvement, not a complete solution.
Will the European Accessibility Act affect UK businesses?
The European Accessibility Act (EAA) comes into full effect in June 2025 across the EU. While the UK is no longer in the EU, UK businesses selling products or services to EU customers may need to comply. The UK also has the Equality Act 2010, which already requires reasonable adjustments for disabled users. The direction of travel is clear: web accessibility requirements are expanding, and UK businesses should be preparing now regardless of which specific law applies.
Are accessibility overlays controversial?
Yes. Many accessibility advocates and disability organisations have criticised overlay tools, arguing they can interfere with existing assistive technologies like screen readers, create a false sense of compliance, and sometimes make the experience worse for disabled users. Supporters counter that overlays provide a practical, affordable starting point for small businesses that cannot afford manual remediation. The truth is nuanced: overlays can help, but they are not a substitute for building accessibility into your site's design and code from the start.
See where your site stands on accessibility
Our free scan checks accessibility basics alongside privacy policy, cookie consent, and security headers.
Run your free scan →