AsafAmos Accessibility Scanner

2 AA and ADA accessibility violations on your site — the standards behind the EAA 2025, ADA Title III, and Israeli תקנה 35. 11 — is bundled with the plugin and runs entirely in your WP admin browser tab. The target page is loaded in a hidden iframe inside the admin area and evaluated there.

The default scan flow does not transmit your URL, your HTML, or any scan contents to any external service.

What it does

• Loads the target page in a hidden iframe inside your WP admin and evaluates it with bundled axe-core 4.11. Nothing leaves your server during a normal scan.

• Reports every violation grouped by severity (critical / serious / moderate / minor).

• Links to axe-core documentation for each rule so you can fix it in your theme or content.

• New in 1.3: a Generate AI fix button on every violation. Click it and Claude suggests the exact before / after code change for that element. Nothing is sent until you click — see “Optional features” below for exactly what is transmitted. Fixes are suggested code changes; you (or your developer) apply them in your theme or content.

• Optional daily cron re-scans (off by default — see “Optional features” below for what it does and does not transmit).

• Works with any theme, any page builder, any caching plugin.

Why not an accessibility overlay?

Overlay widgets (the “robot button” you’ve seen on other sites) inject runtime JavaScript over broken HTML. They do not fix anything; the FTC fined the largest vendor $1M in January 2025. Real compliance means fixing the source HTML / CSS.

This plugin shows you what to fix — it does not hide problems and it does not ship any JavaScript to your visitors.

Built for new accessibility regulations

• EAA 2025 — European Accessibility Act, enforceable since June 2025

• ADA — U.S. courts apply WCAG 2.1 AA as the de facto standard

• Israeli תקנה 35 — updated October 2024 with stricter enforcement

Free. Optional paid tier (separate hosted service)

The plugin itself is free. Unlimited scans, optional daily cron, full per-rule violation report — all included.

com generates the AI fix suggestions. The service is not part of this plugin and is never contacted by the default scan flow. A small number of AI fixes per day is free without an account.

For unlimited fixes, the axle Site plan ($19/month) gives you an API key that you paste in this plugin’s Settings; it is then sent with your fix requests and with the optional cron scan, both described below.

Not a compliance certificate

11, the engine used here) catch roughly 57% of WCAG issues. Manual review by a qualified human auditor is still recommended for full conformance.

Optional features (and what they transmit)

This is the full and accurate transmission story for every feature. The default install transmits nothing.

1. “Scan now” button — default scan flow

• Runs entirely in your WP admin browser tab.

• Loads the target page in a hidden iframe and evaluates it with bundled axe-core 4.11.

• Does not transmit anything to any external service.

• Scan results are written to your WordPress wp_options table under the key axle_last_scan so the admin dashboard can render the summary.

2. Auto scan = Daily (opt in only — Off by default)

• Only relevant if you explicitly enable this in Tools → AsafAmos Accessibility Scanner → Settings.

• WP-Cron runs without a browser, so the daily cron cannot use the in-browser iframe scanner. Instead it uses the hosted scanner at POST https://axlescan.com/api/scan with body { "url": "<your configured target URL>", "source": "axle-wordpress" } (and Authorization: Bearer <key> if you’ve entered an axle API key).

• Requires your target URL to be publicly reachable — the hosted scanner cannot reach LocalWP, staging behind basic auth, or VPN-only environments.

• No visitor data, form data, or admin content is sent. Only the configured target URL.

• Disabled by default. Setting can be turned off again at any time.

3. “Generate AI fix” button — only when an administrator clicks it

• Nothing is sent when the page loads or when a scan runs. A request is made only when a user with the manage_options capability clicks the “Generate AI fix” button on a violation row.

• Your WordPress server then sends one request to POST https://axlescan.com/api/fix. The request contains: the axe-core rule id, impact, description, help text and documentation link for that violation; one element’s HTML (truncated to 500 characters), its CSS selector, and axe-core’s failure summary for that element.

• If you entered an axle API key in Settings, it is sent in an x-axle-key header so the service can apply your plan. Without a key the free daily allowance is used.

• Not sent: your site URL, other pages, visitor data, form data, WordPress users, passwords or any other admin content.

• The service passes the violation text and the element snippet to Anthropic’s Claude API to generate the suggested change, and returns the suggestion to your admin screen. The suggestion is displayed as plain text and is never applied to your site automatically.

• No fix is requested unless you click, and you can stop using the feature at any time simply by not clicking it.

com)

com/legal/privacy)

com/terms

com/privacy

com at the network level.