Ally works with the WordPress websites to help make them more accessible. Ally Accessibility should work with most standard WordPress configurations. However, because Ally connects each site through a domain-based subscription, compatibility depends on how WordPress handles URLs at the site level. Below is an overview of what Ally works with — and where limitations apply.
WordPress Core compatibility
Ally supports:
• Latest WordPress versions
• Classic Editor and Gutenberg (Block Editor)
Ally scans the rendered HTML, so it works with any editor that outputs standard front-end markup.
Theme Compatibility
Ally works with:
• Most modern WordPress themes
• Custom themes built with standard coding practices
• Page builder–based themes, including Elementor, Divi, Beaver Builder, etc.
Since Ally analyzes the published HTML, theme structure and builder UI do not affect compatibility.
Plugin Compatibility
Ally is compatible with most plugins — except for those that change the site’s URL structure, which affects the subscription connection. For a more detailed look, see Incompatible plugins – Ally.
Works With
• Most page builders
• Most form plugins
• Most SEO plugins
• Most eCommerce plugins
• WPML, which does maintain URL consistency in a way that keeps Ally’s site connection intact
Incompatibility
The main cause of incompatibility
Ally uses a per-site connection that requires the WordPress site URL to match the registered domain exactly. When plugins or configurations alter the URL — such as language-based slugs or multisite subdomains/subdirectories — the connection is interrupted, preventing Ally from functioning properly.
Incompatible plugins and setups
- Most translation/localization plugins (e.g., Polylang, TranslatePress)
These plugins often change the URL of each translated page and Ally’s subscription requires a strict match between the domain and the WordPress URL and these URL changes break the connection. - Multisite installations
Each site in a multisite uses a different URL structure and this prevents Ally from maintaining a stable per-site subscription connection. - Subdirectory installations (e.g., domain.com/site1/)
The subdirectory becomes part of the site’s URL, causing the subscription to fail because it no longer matches the registered domain.
Summary
Ally Accessibility works reliably with most standard WordPress setups, themes, and common plugins. However, due to the domain-matched subscription system, it is not compatible with most translation plugins, multisite, or subdirectory-based sites. WPML is the exception, as it preserves URL integrity in a way that keeps Ally’s connection stable.
