aaronhsieh

<p>Site Add-on Watchdog keeps an eye on your site’s plugins and warns you when:</p>
<ul>
<li>Your installed version is two or more minor releases behind the directory build.</li>
<li>The official changelog mentions security or vulnerability fixes.</li>
<li>(Optional) WPScan lists open CVEs for the plugin when you provide your own API key.</li>
</ul>
<p>The plugin runs on a schedule you control—choose daily, weekly, a twenty-minute testing cadence, or rely on manual scans—and stores results locally. Nothing leaves your site unless you explicitly configure outgoing notifications.</p>
<h3>Privacy first</h3>
<ul>
<li>No plugin inventory or telemetry is ever sent off-site by default.</li>
<li>Optional webhooks are opt-in and only post the detected risks.</li>
<li>WPScan lookups only run when you add your personal API token.</li>
</ul>
<h3>Admin tools</h3>
<ul>
<li>Dashboard page with the current risk list and manual scan button.</li>
<li>Ignore list to suppress noisy plugins.</li>
<li>Notification settings for email, Discord, Slack, Microsoft Teams, or a generic webhook.</li>
</ul>
<h3>Notifications</h3>
<ul>
<li>Email: send to one or more recipients (comma separated).</li>
<li>Discord: post to a channel via webhook.</li>
<li>Slack: connect via an incoming webhook to post alerts into any workspace channel.</li>
<li>Microsoft Teams: send adaptive card style notices through an incoming webhook connector.</li>
<li>Generic webhook: post JSON payload to any endpoint you control, with optional HMAC signatures. Failed deliveries are logged and highlighted on the Watchdog admin screen so you can reconfigure or resend manually.</li>
</ul>
<h3>Troubleshooting</h3>
<h3>Scheduled scans are not running</h3>
<p>Watchdog relies on WP-Cron to trigger scheduled scans and notifications. If you have set <code>DISABLE_WP_CRON</code> to <code>true</code> or your site receives very little traffic (so WP-Cron rarely runs), configure a system cron job to call either <code>wp-cron.php</code> or the plugin’s REST endpoint. The admin <strong>Delivery health</strong> panel lists the REST URL you can target; a typical example looks like this:</p>
<pre><code>curl -X POST https://example.com/wp-json/site-add-on-watchdog/v1/cron
</code></pre>
<p>Testing-mode notifications also rely on this trigger, so be sure your cron job is running when validating delivery.</p>
<h3>CLI Usage</h3>
<p>Watchdog bundles a WP-CLI command so you can run scans outside of the WordPress admin. All examples below assume the command is executed from a shell where <code>wp</code> (WP-CLI) is available.</p>
<pre><code>wp watchdog scan [--notify=<bool>]
</code></pre>
<ul>
<li><code>--notify</code> (optional): Accepts <code>true</code> or <code>false</code> (defaults to <code>true</code>). When set to <code>false</code>, Watchdog will skip any configured email or webhook notifications and only record the scan locally.</li>
</ul>
<p>Examples:</p>
<ul>
<li>Run a scan and send notifications (default): <code>wp watchdog scan</code></li>
<li>Run a scan silently (skip notifications): <code>wp watchdog scan --notify=false</code></li>
</ul>
<p>Recommended workflow: on CI/CD platforms, add a job step that boots your WordPress/WP-CLI container, runs pending database migrations if needed, and then calls <code>wp watchdog scan --notify=false</code> to verify the plugin state without spamming production channels. Promote to production by rerunning the same command with notifications enabled when you are ready to alert your team.</p>
<h3>Development</h3>
<p>The development repository is available on GitHub: https://github.com/happyloa/Site-Add-on-Watchdog. Clone it locally to review the source or run the test suite.</p>


Site Add-on Watchdog

Monitor installed plugins for security notices, outdated releases, and WPScan disclosures without leaking your site's plugin inventory.

netopsae

<p>AudioEye’s patented technology tests for over 400 accessibility and compliance issues, and fixes many of them automatically, reducing the time to make content accessible.</p>
<p>You will get your first AudioEye Accessibility Score the moment you install AudioEye on your site. From then on, AudioEye monitors your site for new issues with every site visitor, detecting and fixing hundreds of errors, while also providing you with a reporting dashboard that identifies what we cannot fix and needs your attention.</p>
<p>Technology can’t do it alone. With advanced plans, AudioEye has a team of certified accessibility experts who can help you throughout your accessibility journey. For those issues that we cannot fix automatically, we show you what the issue is, and how to address it on your site. If a lawsuit occurs, AudioEye is here to support you every step of the way.</p>
<p>Note: Use of the AudioEye plugin requires an active subscription to an AudioEye Plan. See pricing <a href="https://www.audioeye.com/plans-and-pricing" rel="nofollow ugc">here</a>. A link to sign up for a new account is presented during the plugin activation process. To log into an existing AudioEye account, you will need to provide your AudioEye Site ID.</p>
<p>Script delivery (CDN): AudioEye loads the storefront script (<code>aem.js</code>) from <code>wsmcdn.audioeye.com</code> by default today. We are migrating to <code>wsv3cdn.audioeye-services.com</code>. New setups without a saved Site ID use the new host by default; sites that already had a Site ID saved before the CDN preference existed keep the legacy host until an administrator enables the new host under AudioEye <span aria-hidden="true" class="wp-exclude-emoji">→</span> Script CDN (Advanced) after allowlisting the new URL in any Content Security Policy (<code>script-src</code>, etc.). On first run, the plugin includes an optional onboarding step that explains how to allowlist the new host in your CSP.</p>
<p>Features included in all AudioEye base plans:</p>
<ul>
<li>Path to compliance with ADA, Sec 508, AODA & more, using WCAG 2.1 AA</li>
<li>AudioEye Trusted Certification​</li>
<li>Usability toolbar with 24/7 Helpdesk​</li>
<li>Suite of AI-Powered Tests & Fixes​</li>
<li>Access to Certified Accessibility Experts</li>
<li>Basic Legal Support & Warranty​</li>
</ul>
<p>Features available in AudioEye custom plans:</p>
<ul>
<li>Advanced Legal Support</li>
<li>Manual Remediations</li>
<li>Premium Support</li>
<li>Custom Training</li>
</ul>


Accessibility by AudioEye


Kind reminder that accessibility can't take shortcuts. It's like telling an online shop owner there is a widget that fixes all their UX issue. As a UX Designer, I can tell it's impossible. As an accessibility expert, I can tell this kind of solution only bring more complexity to the disable folks' experience.



In January 2025, the US Federal Trade Commission ordered [similar solution name] to pay $1 million (subject to a thirty day finalisation period) due to misrepresentation that its software could make any website compliant with WCAG.



Also, WCAG isn't necessarily what's needed in your country. (France is RGAA, Luxembourg is RAWeb, Europe is EN 301 549)Best is to stay informed, and don't install a magic wand that is more of a black box.


Missleading - Risks of lawsuits (says European Council)

AudioEye automatically finds and fixes common accessibility issues on your site. This plugin provides an easy way to install AudioEye’s accessibility  …

Site Add-on Watchdog vs Accessibility by AudioEye