Recorded use of the accessibility widget, per feature and page view
widget_usageThe Inclusify accessibility widget — the overlay Inclusify serves onto the customer's own site — and what visitors do with it. Read this before writing ANY remediation plan for a site where site_overview reports "widgetEnabled": true, and for 'is anyone using this', 'what are we getting for the money', 'which features matter to our visitors', or before a renewal or cancellation conversation. The overlay gives visitors contrast, text-size, spacing, cursor, reading and navigation controls, so an active one is a layer between the site's source and what a visitor experiences, and a plan written from findings alone describes a page nobody sees: some of what you are about to fix is already being worked around at runtime, and a fix at source can duplicate or fight a feature that is switched on. A review wrote a 19-item plan for a store with the overlay live and never mentioned it once. What it returns: per feature, the number of page views in which a visitor switched it on, on how many separate days, the total across all features, and this month's visitor count for context. The unit is page views, not clicks: reporting is deduped per feature per page view, so a slider adjusted repeatedly on one page counts once. Read every count as a floor. Do not use it to judge whether the site is accessible — it measures visitor behaviour, not the site's condition; site_overview and the finding tools do that. Read-only: costs one read and loads no page. Reads zero carefully: a zero total is reported together with which of four causes applies (the widget is switched off in Inclusify; nothing has EVER reported in, meaning the widget is almost certainly not installed on the site at all; visitors were counted before but not in this window; or visitors arrived and feature use has not been reported). A zero of the last kind means only that: no report has arrived. It has two causes a zero cannot tell apart — nobody switched a feature on, or the site is still serving a widget build from before feature reporting existed (bundles are edge-cached for hours and a storefront can hold an older copy for much longer). Never present an empty result as evidence that the widget is unwanted or unused.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days back to count (default 30, cap 365). | |
| website | Yes | The website domain as registered in Inclusify, e.g. "example.com". |