Troubleshooting

Toolbar appears too small

If the Toolbar is unusually narrow and its labels or controls appear too small, an older plugin build may derive its dimensions from the theme’s root font size. Free is also affected. Install a corrected plugin package and, if needed, clear the page and browser caches afterward. The corrected Toolbar uses a theme-independent desktop width of up to 760 CSS pixels and adapts to smaller screens. Do not change your website’s global font size to compensate; browser zoom remains available.

Proxy unreachable

Symptom: Message “Proxy server is not available”

Cause: Network issue or cloud proxy temporarily unavailable

What to do:

1. Check your internet connection
2. Wait a few minutes and retry
3. See if a firewall or security plugin blocks outbound HTTPS
4. Contact support if it persists

Limit reached

Symptom: HTTP 429 or “Limit reached”

Cause: Monthly cap for AI generations or tested URLs

What to do:

1. Open usage under the “Account & License” tab
2. Wait until the next reset date and time shown under Account & License.
3. Or upgrade to a higher plan (Free, Basic, Plus, Premium, Agency)

Freemius not connected

Symptom: Cloud features unavailable

Cause: Freemius not connected or opt-in incomplete

What to do:

1. Open the “Account & License” tab
2. Complete the Freemius opt-in flow
3. Confirm the site is registered

Batch Accessibility Test stuck

Symptom: Batch run does not progress

Cause: Timeout, cron, or server limits

What to do:

1. Verify WP-Cron or Action Scheduler is running
2. Cancel the batch and start again
3. In WordPress, open Tools → Site Health and review any warnings (PHP, scheduled events, background tasks).
4. If the batch still stalls, contact support through the product website with a short description and a screenshot if you can.

Reading mode or Read aloud finds no content

Symptom: The Toolbar reports “No meaningful main content was found on this page” or “No readable content was found for this start point” even though visible text exists.

Cause: Reading mode and Read aloud share one content detector. It prefers semantic main regions, also recognizes common WordPress and page-builder wrappers, and uses a filtered page-body fallback when landmarks are missing. Headers, navigation, sidebars, footers, forms, dialogs, advertisements, cookie notices, and hidden content are not included.

What to do:

1. Update EZZE WCAG Pro to a version that includes the filtered content fallback.
2. Where possible, still add a correct <main> element or role="main" to the theme; this also improves orientation for assistive technologies.
3. If the message remains, check whether the visible text exists only in excluded UI regions, forms, or permanently hidden elements.

Read aloud is unavailable or no voice appears

Symptom: Read aloud is marked unavailable, the voice list remains empty, or playback produces no sound.

Cause: The browser exposes no speech synthesis, loads voices after a delay, or the selected browser/system voice is currently unavailable. Selected text is usable only when the selection is inside the detected main content.

What to do:

1. Reopen the Read aloud view after a moment and choose another available voice.
2. Deliberately press Start read aloud; opening the detail view never starts audio.
3. Check browser volume, operating-system output, and—when using an online voice—the internet connection.
4. Update the browser and operating system or try another current browser. The feature remains intentionally unavailable when the browser provides no speech service.
5. Remember that Stop, Reset all, and leaving the page end playback.

Read aloud does not use the EZZE proxy, so reconnecting Freemius does not repair a browser or operating-system voice.

Toolbar preferences do not persist

Symptom: Adjustments are gone after closing the tab or browser.

Cause: This session uses sessionStorage. Private browsing, browser cleanup, or blocked site storage can also remove device preferences and named profiles.

What to do:

1. Select Remember on this device under Profile.
2. Allow site storage for the domain and avoid automatic deletion on browser close.
3. Named profiles exist only in this browser on this device and are not synchronized.
4. Use Reset all for corrupt preferences, then create the profile again.