We're here to help
Have a question about AccessiYes? Our team monitors the WordPress.org public support forum daily — every thread gets a response.
Post on the Support ForumTypical response: within 48 hours · All threads are public and searchable
Real people. Real responses.
The WordPress.org forum is where our team lives. Here's what you can expect when you post.
Our team checks the forum every day. Most questions receive a reply well within two business days.
We don't let threads go unanswered. Every question gets a response, however complex.
All support threads are publicly indexed. Your question may already have been asked — and answered.
3 steps to a faster answer
Following these steps helps you find solutions quickly and helps us resolve your issue faster.
Check the common issues list
Scroll down to browse the most frequent support questions — many issues have a known solution that takes under a minute to apply.
Jump to common issuesSearch the forum
Use the WordPress.org forum search to find existing threads on your topic. Thousands of questions have already been answered there.
Search the forumPost your question
Include your WordPress version, active plugins, theme name, and a screenshot if possible. The more detail you share, the faster we can help.
Post a new topicTop questions from the support forum
Browse these before posting — most questions have already been answered.
Check the following in order:
- Go to Plugins → Installed Plugins and confirm AccessiYes shows as Active.
- Clear your caching plugin cache (WP Rocket, W3 Total Cache, etc.) and reload the page.
- Check if your theme sets a high
z-indexon its own elements that could be stacking above the widget. - Temporarily switch to a default theme (Twenty Twenty-Four) to rule out a theme conflict.
Still not appearing? Post on the support forum →
To isolate the conflict:
- Deactivate all plugins except AccessiYes and check if the issue disappears.
- Reactivate plugins one at a time until the conflict reappears — that's the culprit.
- If the conflict is with a theme, temporarily switch to a default theme to confirm.
Share your findings on the forum so we can issue a compatibility fix in the next release.
Go to Settings → AccessiYes in your WordPress dashboard. The position (bottom-left or bottom-right) and accent colour are both configurable without writing any code.
If you need further customisation — for example, to move the widget to a different corner or match a specific brand colour — post in the forum and we can advise on CSS overrides.
AccessiYes stores visitor preferences in the browser's localStorage. If preferences aren't persisting, this usually means one of the following:
- A cookie consent banner on your site is blocking
localStorageaccess until consent is given. - The visitor is using a browser with strict privacy settings (e.g. Firefox in private mode, Safari ITP).
- A security plugin is blocking local storage writes.
AccessiYes loads asynchronously — it never blocks rendering or delays LCP. If Lighthouse or PageSpeed Insights is flagging it, the most common cause is a caching plugin that has saved a synchronous version of the script tag.
Clear all caches and re-run the test. If the issue persists, share your PageSpeed Insights report URL in the forum.
No. All accessibility preferences are stored locally in each visitor's browser using localStorage. No data is ever sent to a server, no tracking pixels are loaded, and no analytics are collected. AccessiYes is fully GDPR-compliant with zero data collection.
Support people actually talk about
From the WordPress.org reviews — real words from real site owners about getting help.
★★★★★Excellent plugin – Incredible support!"Not only is it an excellent plugin, but the support is incredibly efficient. I had a small problem following WordPress updates, which was resolved quickly and easily. There are real people behind this plugin. I highly recommend it."
★★★★★Simple plugin with brilliant support!"Since I'm building a website with an EU grant, accessibility requirements were essential. I needed support in Polish, English, and Ukrainian. It took Ryan and his team literally a few days to prepare the Ukrainian language update. I was pleasantly surprised by his openness. I believe this plugin will support many important community projects!"