Last updated
This policy covers two separate things. Our own website, webability.io, uses analytics and advertising tools, which we list below. You can switch off the advertising and measurement tools; our product analytics (PostHog) currently loads regardless of that choice, and we say so plainly in section 2. The WebAbility widget that runs on our customers’ websites is different: it sets only first-party storage for accessibility preferences and loads no third-party trackers there.
This summary is for orientation only. The full terms below are what apply.
“WebAbility” can mean two things in a cookie context, and they behave very differently:
If you are a visitor to a website that uses the WebAbility widget, only Section 4 applies to you. If you are browsing webability.io right now, Sections 2 and 3 apply.
webability.io uses the following third-party tools. Each may set cookies or use browser storage (localStorage / sessionStorage) under its own domain or ours.
| Tool | What it does | When it loads |
|---|---|---|
| PostHog | Product analytics: page views, feature usage, and similar usage measurement. Uses a cookie plus localStorage and sessionStorage. | On page load, before a consent choice is made. |
| Google Analytics and Google Ads (via Google Tag Manager) | Traffic analytics and advertising measurement / conversion tracking. | After you consent. |
| LinkedIn Insight Tag | Advertising measurement and audience building for LinkedIn campaigns. | After you consent. |
| Microsoft Clarity | Session recording and heatmaps on this marketing site. It captures interactions such as mouse movement, clicks, and scrolling so we can see how pages are used. | After you consent. |
We do not list individual cookie names and lifetimes for these tools here, because the third parties change them without notice and a stale table would be worse than none. Each provider documents its own cookies; the table above tells you which providers are present and why.
The WebAbility widget is embedded on our customers’ websites (“host pages”). There it sets first-party storage only — no third-party trackers — in these categories: your saved accessibility preferences, per-tab session state, cached licence validation, and de-duplication of usage counts so a single visit is not counted twice. Keys are prefixed asw or _asw_. The main ones are listed below; we describe categories rather than enumerate every key, because the exact set changes between releases and a stale list would be worse than an accurate description.
| Name | Type | Purpose | Duration | Classification |
|---|---|---|---|---|
asw | First-party | Stores the visitor’s accessibility preferences (font size, contrast, dark mode, cursor style, profile selection, language choice, enabled tools). | 30 days | Strictly Necessary / Functional |
Flags: Path=/; SameSite=Lax; Secure (on HTTPS pages). Not set if the product fails to load or token validation fails. Under GDPR and the ePrivacy Directive this cookie is classified as strictly necessary and therefore exempt from consent requirements (ePrivacy Art. 5(3), second exemption).
| Key | Purpose |
|---|---|
asw-widget-hidden | Per-tab hidden state for the accessibility button. |
asw-session-id | Per-tab random session identifier used for impression de-duplication. |
| Key | Purpose |
|---|---|
logoImage | Cached custom logo image (customer branding). |
asw-original-api-config | Original API-provided product configuration, used by the Reset action. |
screen-reader | Screen reader mode on/off. |
wa-snap|<domain> | A list of short records for pages the widget has already analysed on this site, so it does not upload the same page again. Each record holds a hash of the page path and title, the element count, the page size in characters, and the capture time. Records expire after 24 hours. No page content, and no identifier for the visitor. If localStorage is not usable (full or blocked), the widget writes this key to sessionStorage instead. |
None. On host pages — the websites where our customers embed the widget — our product does not load third-party scripts, pixels, or ad/analytics providers. The analytics and advertising tools described in Section 2 exist only on webability.io itself and are never loaded by the widget.
See also our Privacy Policy and Terms of Use.