To change your password:

1. Go to your My Elementor dashboard.
2. Click the account icon in the upper right corner.
   
3. Select My profile from the dropdown menu.
   
4. Click Change password.
   
5. Enter your current password.
6. Enter the new password.
   
   Note

   Your password must have at least eight characters including at least one capital letter, one number and one special character. Avoid starting or ending your password with a space.
7. Confirm your new password.
8. Click Save.
   
   
   Tip

   If you forgot your password, or if you want to start using your email instead of Google/Apple to log on, click Forgot password on the login screen.

If you have trouble resetting your password

• Refresh the page, then try again.
• Clear cache/cookies or use a private/incognito window.
• Try a different browser or device and ensure password-manager autofill isn’t interfering.
• Temporarily disable browser extensions that modify forms or content.

SPF (Sender Policy Framework)

SPF lets you define which mail servers are allowed to send email on behalf of your domain.

When an email is received, the recipient’s server checks your SPF DNS record to verify that the sending server is authorized.

If it isn’t, the message is flagged or rejected — helping block spoofed or fraudulent emails.

DKIM (DomainKeys Identified Mail)

DKIM adds a cryptographic signature to your email headers using a private key.

The receiving mail server validates this signature using the public key published in your DNS.

This process:

• Confirms that the email truly came from your domain
• Ensures that the message wasn’t altered in transit
• Strengthens sender legitimacy

DMARC (Domain-based Message Authentication, Reporting & Conformance)

DMARC builds on SPF and DKIM by defining what should happen when authentication fails — such as rejecting or quarantining the email.

It also checks alignment between the visible “From” address and the domains validated by SPF and DKIM.

DMARC includes reporting tools that give domain owners insight into legitimate and fraudulent email activity.

Why These Protocols Matter

Together, SPF, DKIM, and DMARC:

• Protect your domain from spoofing and impersonation
• Improve deliverability for transactional and notification emails
• Ensure your messages are recognized as trusted by recipient mail systems
• Reduce the chances of emails being blocked, filtered, or marked as spam

Setting up these protocols involves adding specific DNS records for each protocol. This enables proper email verification and enforcement.

This usually happens when WordPress shows different display names, but the actual file name on the server hasn’t changed.

The Cause

WordPress lets you change the media title in the Media Library — but this does not rename the underlying file.

If a user uploads the same image file multiple times, even with different display names, they may still have identical file names.

Example

Alex uploads an image with the file name myphoto.jpg and gives it the display name My Garden in the Media Library. They then edit the image and upload it again, giving it the display name My Garden in Winter. However, the actual file name remains myphoto.jpg.

The Image Optimizer checks files based on the actual file name, not the display name.

If it finds duplicates, it cannot optimize them and displays this error.

What You’ll See

• “File with this name already exists”
• Images not being compressed
• Optimization batch stopping or skipping files

The Solution

Option 1: Rename the Actual File

1. Use a file manager or a file renaming plugin) to rename the file itself — for example:
   • myphoto.jpg to myphoto1.jpg
2. Refresh the Media Library.

Option 2: Re-upload the File With a New File Name

1. Download the image.
2. Rename the image — for example:
   • myphoto.jpg to myphoto1.jpg
3. Upload the image again with the new file name. and upload it again, but change the actual filename before uploading.
   Once the filenames are unique, the Image Optimizer will process them correctly.

Summary

The error appears because the plugin optimizes files based on the real file name, and duplicates cannot be processed. Renaming the actual file or re-uploading it with a new filename will resolve the issue.

Why the Tabindex Is Set Above 0

The widget may assign a positive tabindex (usually 1) to specific elements. This is done intentionally to:

• Ensure the Ally accessibility overlay can be reached quickly by keyboard users
• Allow certain “skip to content” or widget-trigger elements to receive focus when needed
• Maintain reliable keyboard access regardless of theme or page structure

This behavior is part of the plugin’s internal logic and is not a user-configurable setting.

Why Accessibility Tools Flag It

While it’s intentional, using a tabindex greater than 0 is not recommended in general accessibility best practices because:

• It overrides the natural focus order of the page
• It can interrupt expected keyboard navigation behavior
• It causes audit tools (like Lighthouse and Axe, etc.) to mark it as a potential issue

These tools flag the general pattern, not Ally’s specific implementation.

Is This a Problem?

In normal use, the positive tabindex does not harm accessibility, and is included to make the widget reliably keyboard-accessible across all WordPress setups.

However, because non-zero tabindex values can theoretically disrupt focus order, automated tools will still report it.

Summary

• Ally sets a positive tabindex on purpose
• It ensures fast and consistent keyboard access to the widget
• Most tools flag it because of general best-practice rules, not because it breaks accessibility • The value used is typically 1, only for specific widget elements

If you suspect a plugin conflict:

1. Temporarily deactivate the suspected plugins. Start with translation, redirection, security, or caching plugins. For details, see Activate and deactivate plugins.
2. Check to see if Ally loads normally, if it does, you have a plugin problem.
3. Reactivate the plugins one at a time until you find the one interfering with Ally.
4. Switch to an alternate plugin.

Recommendations

If a plugin conflicts with Ally due to URL changes or request blocking, we strongly recommend:

• Use a different plugin: If the conflicting plugin is essential, consider using a different one that doesn’t modify your site’s URL or external requests.
• Adjust settings: Use the plugin settings to prevent URL rewriting or aggressive blocking
• For translations, WPML remains the only major multilingual plugin that is fully compatible.

When using these types of plugins, you may see:

• The Ally widget not appearing or not loading

• A “mismatch” connection notice

• A 404 Not Found message

• The dashboard connection repeatedly disconnecting

Incompatible plugins

Translation Plugins (URL-Based Translators)

Plugins that create multilingual versions by changing page URLs.

Known incompatible plugins:

• TranslatePress

• Polylang

• Weglot

• Other URL-altering language tools

These plugins rewrite URLs per language (e.g., /en/, /fr/), causing the Ally subscription URL to break.

Redirection Plugins

Plugins that create custom redirects can interfere with Ally’s endpoint communication.

Known incompatible plugins:

• Redirection

• Safe Redirect Manager

• Yoast Redirect Manager

These plugins may cause mismatch or 404 errors when Ally tries to communicate with its service.

Security Plugins

Security tools that block or filter external API requests may prevent Ally from verifying the site.

Known incompatible plugins:

• Wordfence

• iThemes Security

• Sucuri

• All-In-One Security

These can block Ally’s connection or hide required endpoints.

Caching & Performance Plugins

Page caching, CDN layers, or aggressive minification can prevent the widget from loading correctly.

Known incompatible plugins:

• WP Rocket

• LiteSpeed Cache

• W3 Total Cache

• SiteGround Optimizer

• Cloudflare (via caching rules)

These may cache or rewrite Ally’s script, resulting in widget errors or missing functionality.

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.

If your hosting plan does not include Elementor Pro, you will need to purchase and install Elementor Pro on your website.

• If the Image Optimizer is configured to convert images to WebP format, any images already in WebP format cannot be converted again. This can result in an optimization error.
• Converting an AVIF image to WebP can often increase the file size. since the goal of the Image Optimizer is to decrease the image size, this may lead to an optimization error.

Possible solutions

• Restore the original image and try optimizing it again.
• Optimize the images one at a time. For details, see Optimize a single image.