Linux 软件免费装
Banner图

AcceGuru - Accessibility Scanner, Auto-Fixer & AI Alt Text

开发者 merkucio
更新时间 2026年10月4日 13:44
PHP版本: 8.0 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

a11y wcag web accessibility ada wp accessibility

下载

1.0.2 1.0.4 1.0.1 1.0.7 1.0.3 1.0.5 1.0.6 1.1.0

详情介绍:

AcceGuru helps identify and address accessibility issues related to ADA, WCAG 2.0 / 2.1 / 2.2, Section 508, EN 301 549, the California Unruh Civil Rights Act, the European Accessibility Act (EAA), AODA, the UK Equality Act 2010, and other accessibility laws and standards. Automated testing cannot establish legal compliance or complete WCAG conformance; manual review is still required. The axe-core scanner checks selected posts, pages and public custom post types from one dashboard. Saved results appear in the Block Editor sidebar and A11y post-list column, while the front-end overlay highlights affected elements on the live page. AcceGuru also provides toggleable accessibility fixers, site-wide ignored rules, optional AI-generated alt text using your own provider key, and an accessibility statement generator. Key features Auto-fixers Low-impact fixes are enabled on install. Appearance-changing fixes are off by default. Settings -> Fixers provides separate controls for skip links, focus outlines, language attributes, search and comment-form labels, empty searches, new-window and document-link labels, link underlines, video controls, positive tabindex, redundant titles and viewport scaling. Standards & laws coverage Accessibility requirements vary by jurisdiction. AcceGuru does not determine or guarantee legal compliance or complete WCAG conformance. AI providers AI alt text is optional and uses an API key supplied by the site owner. Supported providers are OpenAI, Anthropic, Google Gemini and Mistral. Keys are encrypted at rest using the WordPress authentication salt. See Privacy below for exactly when data is sent and for provider terms and privacy policies. Want more? AcceGuru Pro Need faster scanning and additional review workflows? AcceGuru Pro extends the free plugin with: The free plugin remains fully functional without Pro. Pro is a separate add-on and requires AcceGuru Free. Compare plans and get AcceGuru Pro

安装:

  1. Upload the acceguru folder to /wp-content/plugins/, or install via Plugins -> Add New.
  2. Activate the plugin through the Plugins screen.
  3. Go to AcceGuru -> Settings to enable the fixers you want.
  4. (Optional) Add an API key under AI Alt Text if you want AI-generated alt text.
  5. Run a site scan from AcceGuru -> Dashboard.
  6. Open any scanned post or page in the Block Editor to review its saved results.

屏幕截图:

  • Site-wide scan dashboard with top offending pages and most common issues.
  • Front-end overlay highlighting accessibility issues on the live page.
  • Bulk AI alt-text generation across the Media Library.
  • Settings screen with toggleable fixers and AI provider selection.
  • Accessibility statement generator with live preview.

升级注意事项:

1.1.0 Rebuilds the scan panel and the editor sidebar around nine subject categories, saves manual checks with the scan and announces scan results to screen readers. 1.0.7 Removes mouse-click focus rings, improves keyboard-focus visibility on light and dark backgrounds, separates fixer styles and expands the accessibility statement. 1.0.6 Adds manual checks: the places the scanner cannot judge are now listed in the front-end panel and counted on the dashboard. 1.0.5 Explains why pages were skipped, prevents duplicate front-end scans, improves long finding text and reduces repeated featured-image database work. 1.0.4 Tested with WordPress 7.1, restores click-to-highlight in the Block Editor panel, adds AVIF support, sends smaller image copies for alt text and fixes rule documentation links. 1.0.3 Fixes full-site scans on sites with redirects and makes A11y column sorting match the displayed issue counts. 1.0.2 Fixes missing scan results on multilingual sites, inconsistent Media Library alt-text totals, and statement-page, A11y-count and scan-log issues. 1.0.1 Adds OpenAI and Anthropic alt-text providers, "Retry failed pages" on the dashboard, and tab-loss and navigation guards during site scans. 1.0.0 Full visual redesign, scan pause and resume, adaptive time estimate, and four new fixers.

常见问题:

Does this make my site WCAG compliant automatically?

No. Automated testing covers only part of accessibility. Manual review is still required for matters such as meaningful headings, link purpose, keyboard interaction and reading order. AcceGuru does not determine or guarantee legal compliance or complete WCAG conformance.

Where are AI API keys stored?

In wp_options, encrypted with AES-256-GCM using a key derived from wp_salt('auth'). If the server lacks the required OpenSSL support, the key is not saved unencrypted. It is sent only to the configured provider.

Does the scanner slow down my site?

The scanner is not loaded for normal visitors. axe-core is lazy-loaded for an authorized user only when a dashboard scan or front-end overlay scan is requested.

Which post types does the A11y column appear on?

Posts, pages, and public custom post types that use the standard WordPress posts list table. Media Library attachments are not included.

Can I exclude specific issues or rules?

Yes. Use the "Ignore" button on the dashboard's Most Common Issues panel to hide a rule site-wide; ignored rules are excluded from dashboard counts and per-page panels.

Does it work with block themes?

Yes. The fixers support block themes, including theme.json styles.

Why does the dashboard count differ from what I see in the front-end overlay?

The site scan uses a desktop-sized viewport based on the administrator's browser, with a minimum of 1024x768. The overlay uses the current live viewport, so layout-dependent results can differ.

How is Passed Checks calculated?

Passed Checks is the percentage of completed axe-core checks that passed. AcceGuru findings appear in issue totals and lists but are not mixed into that percentage. Results are marked for a new scan after relevant settings or rules change.

Why do some pages show "Timed out after 30s" in the scan log?

Each page has a 30-second limit. Slow hosting, heavy themes/plugins or third-party scripts can cause a timeout; use "Retry failed pages" after the server recovers.

更新日志:

1.1.0 1.0.7 1.0.6 1.0.5 1.0.4 1.0.3 1.0.2 1.0.1