Accessibility widget data paths
Where WordPress accessibility plugins send visitor requests
An accessibility widget can load a script from an outside service on every page. Requests to that service include an IP address and browser information. Some widgets store accessibility preferences. Other plugins keep contrast and text-size tools on your own server. This table describes the setups below; your settings can change where requests go.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group accessibility plugins
We compare the accessibility setups named below. A plugin that serves contrast and text-size tools from your server is different from a plugin that loads an outside accessibility widget. We have not tested consent timing or how long widget-service logs are kept.
Accessibility plugins and widgets
No paid placement. Tools hosted on your site first, then outside accessibility widgets, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Documented script hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| WP Accessibility This row covers WP Accessibility when the built-in toolbar and theme fixes run from files on your WordPress server. An outside font or analytics plugin on the same page is a different setup and is not this row. Consent timing is not tested here. | Tools hosted on your site | No outside widget host documented for this setup. Other page requests are not covered. | Not assessed | Not tested |
| |
| accessiBe This row covers the accessiBe plugin when the accessWidget script is injected. The page loads a widget from acsbapp.com. Mixpanel calls used in the WordPress admin are a different setup and are not this row. Consent timing is not tested here. | Outside accessibility widget | acsbapp.com | Not assessed | Not tested |
| |
| All in One Accessibility This row covers All in One Accessibility when the front-end widget script is enqueued. The page loads a widget from www.skynettechnologies.com. Optional font or translation hosts named in the listing are a different setup and are not this row. Consent timing is not tested here. | Outside accessibility widget | www.skynettechnologies.com | Not assessed | Not tested |
| |
| EqualWeb This row covers the EqualWeb plugin when an EqualWeb accessibility code snippet is pasted into settings. The plugin does not ship a fixed visitor script host in source. Widget hosting is not verified here. Consent timing is not tested here. | Outside accessibility widget | Receiving domains not verified | Not assessed | Not tested |
| |
| UserWay This row covers Accessibility by UserWay when the widget script is printed on the page. The page loads a widget from cdn.userway.org. Consent timing is not tested here. | Outside accessibility widget | cdn.userway.org | Not assessed | Not tested |
| |
| Web Accessibility (Ally / One Click Accessibility) This row covers Web Accessibility, also branded Ally and formerly One Click Accessibility, when a connected Elementor account loads the usability widget. The listing requires that account and describes an outside Elementor service. The page loads a widget from cdn.elementor.com. A legacy local toolbar without that connection is a different setup and is not this row. Consent timing is not tested here. | Outside accessibility widget | cdn.elementor.com | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named accessibility setups. It does not show what loads on your site. Where no outside widget host is documented, that applies only to the setup described. Other page requests are not covered. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long widget-service logs are kept. Accessibility specialists publish a public Overlay Fact Sheet about overlay widgets. This table does not rate whether a widget makes a site accessible. The site scan linked below checks for third-party requests; it does not access your WordPress database.
Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-accessibility-plugin-privacy