Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
AccessiWay is an Italian accessibility platform offering a JavaScript widget that adds an in browser toolbar for visually impaired and cognitive accessibility profiles (high contrast, large text, dyslexia friendly font, screen reader optimisations). It also provides automated audits, manual remediation and certification services to help publishers comply with the European Accessibility Act, EN 301 549 and WCAG 2.2. The widget collects accessibility preferences and stores them in a persistent cookie so the visitor's profile is reapplied on return visits.
AccessiWay is an Italian platform that combines an accessibility toolbar widget with audit, remediation and certification services. The widget appears as a small icon at the corner of the page; when opened, it lets the visitor pick an accessibility profile (high contrast, large text, dyslexia friendly font, screen reader optimisations) and apply the profile to the current site without a page reload. The platform is widely used in Italian public sector sites and increasingly by EU private businesses preparing for the European Accessibility Act.
The accessibility profile choice is not a neutral preference : selecting a dyslexia font or a screen reader optimisation strongly suggests that the user has a specific impairment. Under Article 9 GDPR this is health related data and a Special Category. The persistent storage of that choice in the aw_profile cookie therefore requires not just any consent but an explicit consent (Article 9(2)(a) GDPR) and a clear notice explaining why the choice is stored.
AccessiWay sets aw_session (strictly necessary, session, current toolbar session), aw_profile (functional, 1 year, the chosen profile) and aw_lang (functional, 6 months, language). The aw_profile cookie carries the special category implication discussed above; aw_session and aw_lang do not.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
From 28 June 2025 the European Accessibility Act applies to a wide range of products and services sold in the EU. AccessiWay can support that compliance journey through audits and remediation, but the widget alone is not enough : EU and national supervisory bodies and accessibility experts agree that automated overlays are no substitute for source code level accessibility. Treat the widget as an aid for visitors and combine it with manual remediation and a conformance statement.
Place the AccessiWay widget behind a CMP consent gate so the aw_profile cookie is only set after explicit consent. Provide a clear notice explaining why an accessibility choice is stored. Combine the widget with source level WCAG 2.2 remediation. Publish an accessibility statement (EN 301 549 template). Sign the AccessiWay DPA and confirm EU only hosting in your processing register.
Websites using AccessiWay must obtain user consent under GDPR regulations.
DPIA considerations
AccessiWay processes accessibility preferences that may reveal a disability, a Special Category of data under Article 9 GDPR. Key considerations: (1) the persistent accessibility profile cookie reveals likely cognitive or visual impairments and therefore requires informed consent and a clear notice; (2) audit reports stored on the AccessiWay dashboard list the publisher's URLs and DOM snapshots that may contain personal data exposed on the page; (3) the widget loads accessibility tools (text to speech, font replacement, dictionary) that may call third party libraries, those should be vetted before deployment; (4) automated overlays are not a full WCAG remediation; the publisher remains responsible for source code level accessibility under the European Accessibility Act; (5) the audit log on the AccessiWay back end is a processing activity to declare in the publisher's register. A DPIA is recommended whenever the widget is deployed on a public sector site or on a service likely to be used by vulnerable populations.
Sample consent text
Our site offers an accessibility toolbar powered by AccessiWay (AccessiWay S.r.l., Milan, Italy). When you open the toolbar and pick a profile (for example dyslexia friendly font or high contrast), AccessiWay stores your choice in a cookie so the same profile is applied on your next visit. Because the choice can reveal a disability, this storage requires your consent. You can refuse and still use the site normally; we will simply not remember your accessibility preferences for later.
Third-party domains contacted
accessiway.comcdn.accessiway.comapi.accessiway.comapp.accessiway.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| aw_profile | Functional | 1 year | Stores the accessibility profile chosen by the visitor (e.g. high contrast, dyslexia font, screen reader optimisations) so it is reapplied on the next visit. May reveal a disability and therefore requires consent. |
| aw_session | Strictly necessary | Session | Identifies the current session of the AccessiWay toolbar to keep the chosen profile active across page reloads in the same visit. |
| aw_lang | Functional | 6 months | Stores the chosen language for the AccessiWay toolbar so the controls are displayed in the visitor's language. |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
aw_session (strictly necessary, session), aw_profile (functional, 1 year, accessibility profile), aw_lang (functional, 6 months, toolbar language). aw_profile may reveal a disability and is therefore special category data.
Yes for aw_profile (explicit consent under Article 9(2)(a) GDPR because it can reveal health information). aw_session and aw_lang can be loaded as strictly necessary and functional.
Explicit consent (Article 9(2)(a)) for the persistent accessibility profile cookie. Legitimate interest (Article 6(1)(f)) for the strictly necessary toolbar delivery. Legal obligation (Article 6(1)(c)) for the publisher's accessibility compliance with the European Accessibility Act.
No. AccessiWay is hosted in the European Union and uses European sub processors in the default configuration. Verify in the AccessiWay DPA that no US analytics integration is enabled before going to production.
Recommended for public sector sites, education, healthcare and any service likely to be used by vulnerable populations. The combination of disability inference and persistent identifier crosses the systematic large scale processing threshold under Article 35(3)(b).
Place the widget behind the CMP consent gate so aw_profile only loads after explicit consent. Show a clear notice explaining the special category storage. Combine the widget with real WCAG 2.2 remediation. Publish an accessibility statement. Sign the AccessiWay DPA.
Yes : UserWay (US, but EU regions), EqualWeb (Israel), AudioEye (US), accessibility libraries like axe DevTools for audits, or simply hiring accessibility expertise for source level fixes. Overlays are a complement, never a complete substitute.
List aw_session, aw_profile and aw_lang with domain, duration and purpose. Flag aw_profile as carrying special category data and explain why. Add AccessiWay S.r.l. as a processor based in Milan and link to its privacy policy and the publisher's accessibility statement.