System requirements and compatibility
WordPress and PHP version requirements for AccessYes, plus compatibility notes for common plugins, caching tools, and browser support.
Updated
In this article: The minimum WordPress and PHP versions required to run AccessYes, what browsers the front-end widget supports, and known compatibility notes with other plugins.
AccessYes has a deliberately low barrier to entry. It runs on the vast majority of WordPress sites without any special server configuration.
WordPress requirements
| Requirement | Minimum | Recommended |
|---|---|---|
| WordPress version | 5.0 | Latest stable (6.x) |
| PHP version | 5.6 | 7.4 or higher |
| MySQL / MariaDB | No specific requirement | — |
WordPress 5.0 was released in December 2018 and introduced the block editor. AccessYes does not depend on the block editor — it works equally on classic and block-based themes — but 5.0 is the minimum because of REST API improvements introduced at that version.
PHP 5.6 is the minimum, but running PHP 5.6 or 7.0 is not advisable. Both versions reached end of life years ago and receive no security patches. If your host is still on PHP 5.6, updating PHP should be a priority regardless of which plugins you run.
Check your PHP version in WordPress Admin → Tools → Site Health → Info → Server. If you're on PHP 7.x or below, ask your host to upgrade to PHP 8.1 or 8.2, which are the currently supported versions.
Tested WordPress versions
AccessYes is actively tested against the latest WordPress release. The current version (3.1.3) is tested up to WordPress 6.9.
The plugin is updated regularly to maintain compatibility as WordPress releases new major versions.
Browser support
The front-end widget is a vanilla JavaScript file that runs in any modern browser. There are no build-time dependencies on React or other frameworks on the front end (the admin settings screen uses React, but visitors never load it).
| Browser | Support |
|---|---|
| Chrome / Edge / Opera | Full support |
| Firefox | Full support |
| Safari (macOS and iOS) | Full support |
| Samsung Internet | Full support |
| Internet Explorer 11 | Not supported |
Internet Explorer 11 reached end of life in June 2022 and is no longer a compatibility target for any maintained software. If you have users on IE11, they will not see the widget, but their browsing experience is otherwise unaffected.
Known plugin compatibility
Caching plugins
AccessYes is compatible with all major WordPress caching plugins. One known edge case:
Language files and page caching — If you use a caching plugin and have the multi-language selector enabled, ensure your cache is configured to serve different cached pages per language (or use fragment caching for the widget). A full-page cache that ignores the visitor’s language preference may serve the wrong language initially. This was addressed in version 3.0.3.
Tested and confirmed compatible with: WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, and Cloudflare.
MonsterInsights
A conflict between AccessYes and MonsterInsights was resolved in version 3.0.3. If you are running an older version of AccessYes alongside MonsterInsights, update to 3.0.3 or later.
Other accessibility plugins
AccessYes is designed as a standalone widget and does not conflict with other accessibility tools. However, running two widget-based accessibility tools on the same site is not recommended — it creates redundancy and can confuse visitors.
Server requirements
AccessYes uses the WordPress REST API to save settings from the admin screen. There are no additional server requirements beyond a working REST API.
If your server blocks REST API requests (unusual but possible with some firewall configurations), the settings screen will not save changes. In that case, check your firewall rules or ask your host to confirm REST API access is allowed.
AccessYes does not create any custom database tables. Settings are stored in WordPress's standard wp_options table under the key cya11y_widget_settings. Uninstalling the plugin cleans up this option.
Privacy and data collection
AccessYes collects no data from your visitors. The widget stores each visitor’s personal accessibility preferences (such as their chosen font size or contrast mode) in their own browser’s localStorage — not on your server. There are no cookies, no tracking pixels, and no data transmitted to CookieYes or any third party.
This means AccessYes does not need to appear in your cookie consent banner and does not affect your site’s GDPR compliance posture.
Related articles
- Installing AccessYes — step-by-step installation guide
- Quick start guide — first configuration steps after installation