Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
accessiBe is an Israeli accessibility overlay that injects a JavaScript widget on the customer website to make it conform to WCAG 2.1 AA, the ADA, the European Accessibility Act and other accessibility regulations. The widget sets first party cookies to remember user accessibility profiles and sends usage analytics to accessiBe servers in the United States.
accessiBe is an accessibility automation company founded in 2018 and headquartered in Tel Aviv. Its flagship product is acsB, a JavaScript overlay that the customer adds to every page through a single script tag. The script applies AI based accessibility remediations, exposes an accessibility menu where visitors can adjust contrast, font size, animations, screen reader compatibility and motor profile, and stores those preferences in cookies.
accessiBe sets first party cookies on the customer domain such as acsbi_token, acsbi_active and acsbreset that store the active accessibility profile (visually impaired, motor impaired, cognitive disability, seizure safe, ADHD friendly, etc.). The widget also pings accessiBe analytics endpoints with anonymised usage events, page URL, browser, and assistive technology detected. No payment, contact or behavioural marketing data are collected.
Choosing the visually impaired or motor impaired profile may reveal information about disability, which is health data under Art. 9 GDPR. Storage on the user device qualifies as terminal storage under Art. 5(3) ePrivacy Directive, but the cookies that remember the accessibility profile are arguably strictly necessary to deliver the service the user has just requested. Usage analytics by accessiBe are not strictly necessary and require consent.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The accessibility menu itself can load without prior consent on a legitimate interest basis. The cookies that remember the profile may be set as soon as the user activates a profile, since they are necessary to honour that choice. Usage analytics, behavioural scoring and any AI training on user interactions require explicit opt in consent under Art. 6(1)(a) GDPR.
accessiBe Ltd. is established in Israel, which benefits from an adequacy decision under Art. 45 GDPR. However the production CDN (acsbapp.com) and analytics endpoints route through the United States. Transfers to the US rely on the EU US Data Privacy Framework where accessiBe is certified or on Standard Contractual Clauses otherwise. Document this in the record of processing and in the privacy policy.
Sign the accessiBe DPA, document the legitimate interest assessment for the accessibility profile cookies, gate accessiBe analytics behind the CMP, mention accessiBe as a recipient outside the EEA in the privacy policy, set a clear retention for the acsbi_token cookie, and treat accessibility profile data as sensitive in your record of processing activities.
Websites using accessiBe must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is recommended because accessiBe processes potentially sensitive data: the accessibility profile chosen by a user (visual impairment, motor impairment, cognitive impairment) can reveal health information under Art. 9 GDPR. Document the lawful basis for processing that information, the retention period of the acsbi_token cookie, the international transfer to the United States and the legitimate interest balancing for analytics.
Sample consent text
We use the accessiBe accessibility widget to make this site usable for people with disabilities. The acsbi_token, acsbi_active and acsbreset cookies are necessary to remember your accessibility profile and operate on the basis of our legitimate interest in providing an accessible website. Optional accessibility analytics are activated only after you click accept in our privacy banner.
Third-party domains contacted
acsbapp.comaccessibe.comacsbap.comacsbapi.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| acsbi_token | First party (accessibility preferences) | 1 year | Stores the user accessibility preference selections for the widget |
| acsbi_active | First party (widget state) | 1 year | Indicates whether the accessibility menu has been activated |
| acsbreset | First party (widget reset) | Session | Tracks the reset action for the accessibility widget |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
accessiBe sets first party cookies including acsbi_token (1 year, accessibility preferences), acsbi_active (1 year, widget activation state) and acsbreset (session, reset action). They are linked to the accessibility functionality of the widget.
If accessiBe is strictly tied to the accessibility function activated by the user, the cookies may qualify for the strictly necessary exemption. Loading the script on every page and the IP transfer to US accessiBe servers is not exempt, so most CMP integrators classify accessiBe under a functional or analytics category that requires consent.
Functional cookies for user accessibility preferences can rely on Art. 6(1)(b) GDPR contract or 6(1)(f) legitimate interest in delivering an accessible site. IP transfer and audit logging require 6(1)(f) plus SCCs for the transfer, or 6(1)(a) consent if classified beyond strictly necessary.
Yes. accessiBe Ltd. is based in Israel (EU adequacy decision) but production runs on AWS US East 1 and Cloudflare global edge. Transfers to the US require SCCs and ideally a Transfer Impact Assessment. accessiBe publishes a DPA addendum.
Most accessiBe deployments do not require a DPIA, but one may be appropriate when accessiBe is combined with other tracking, or when an organisation has a high volume of users with disabilities whose preferences are processed at scale.
Sign the accessiBe DPA, classify the widget in your CMP (functional category with the prudent option of consent), document accessiBe in your record of processing, regularly review the audit reports, and complement with native code remediation since overlays are not a full ADA / WCAG defence.
Yes: UserWay (US/Israel), AudioEye (US), EqualWeb (Israel), AccessiWay (Italy/EU), AllyAble (Israel) and native remediation through accessibility audits (Deque, Tenon, Siteimprove). Many disability advocacy groups recommend native fixes over overlays.
List the acsbi_* cookies in a functional or accessibility category, name accessiBe Ltd. as the operator, disclose retention periods (1 year for preference cookies, session for reset) and link to the accessiBe privacy policy and DPA.