[WordPress] 外掛分享: AccessMate

首頁外掛目錄 › AccessMate
WordPress 外掛 AccessMate 的封面圖片
全新外掛
安裝啟用
尚無評分
剛更新
最後更新
問題解決
WordPress 5.8+ PHP 7.4+ v1.1.0 上架:2026-05-24

內容簡介

AccessMate 是一款專為 WordPress 設計的無障礙檢測外掛,能夠掃描網站並檢查是否符合 WCAG 2.0、2.1、2.2 和 Section 508 標準,並提供修正建議,幫助網站提升可及性。

【主要功能】
• 無障礙掃描器,支持多種 WCAG 標準
• 每頁得分與等級評分系統
• 全站掃描,逐頁結果顯示
• 前端掃描功能,便於即時檢查
• 問題詳情面板,提供具體錯誤資訊
• 訪客無障礙工具列,增強用戶體驗

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.1.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「AccessMate」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

AccessMate scans your WordPress site for accessibility issues against WCAG 2.0, 2.1, 2.2, and Section 508 — pick a single standard or combine several — scores each page, and provides guided fixes, all from your WordPress dashboard.
Zero running cost for you. The scanner, the reports and the visitor toolbar are free and have no usage limits. The optional AI features (code fix suggestions and plain-English explanations) use your own API key from Anthropic, OpenAI, Google Gemini, or a local Ollama instance. Your key is stored encrypted in your database and never proxied through our servers.
Core features

Accessibility scanner — powered by axe-core, scans your pages against your choice of WCAG standard, or several combined at once
Score & letter grade — every scanned page gets a 0–100 score and an A/B/C/D/F grade, calculated from passed checks against failures weighted by Critical/Serious/Warning/Notice severity
Site-wide scanning — AccessMate discovers the public URLs on your site and scans them individually, with per-page results, search, and post-type filtering
Scan from the front end — a “Scan Page” button in the admin bar scans whatever page you are viewing and shows results in a slide-in panel, with filter tabs for Critical, Serious and Passed checks and a ruleset switcher for re-scanning
Issues by page — stacked bar chart showing critical/serious/warning/notice counts per page
Issue detail panel — shows the offending HTML, the WCAG success criterion with a link to the spec, the CSS selector, and the affected element count
Passed checks — AccessMate records what passed, not just what failed, so you can show progress
Accessibility statement generator — a five-step wizard that produces a published accessibility statement page for your site
Visitor accessibility toolbar — floating widget with 10 user-controlled accessibility features, configurable colour, position and button size
AI fix suggestions (requires API key) — explains what to change and generates a corrected code snippet
AI explanations (requires API key) — plain-English summaries of an issue for non-technical site owners

WCAG standards & rulesets
AccessMate scans with axe-core, the same open-source accessibility testing engine used by major browser DevTools. Pick any one of the following from the ruleset selector in the scanner or in Settings:

WCAG 2.0 — A, AA, or AAA
WCAG 2.1 — A, AA, or AAA
WCAG 2.2 — AA
Section 508
Best Practice — common accessibility recommendations beyond the WCAG spec
Combined presets — Best Practice + WCAG 2.0 AA, + WCAG 2.1 AA, or + WCAG 2.2 AA

Visitor accessibility toolbar features

Font size
High contrast
Dyslexia font
Grayscale
Reading guide
Pause animations
Line height
Large cursor
Highlight links
Screen mask

Each feature can be switched on or off in the Widget configurator, along with the accent colour, screen position and button size. The toolbar renders inside a Shadow DOM, so its styles cannot affect your theme, and visitor preferences are remembered in their browser’s localStorage.
AI providers supported

Anthropic Claude (claude-haiku-4-5, claude-sonnet-4)
OpenAI (gpt-4o-mini, gpt-4o)
Google Gemini (gemini-1.5-flash, gemini-1.5-pro)
Ollama (local, no key needed — llama3.2, mistral, phi3)

Privacy
AccessMate makes no external requests unless you configure an AI provider and trigger an AI action. When an AI action is triggered, your WordPress server makes a direct request to your chosen provider using your key. No data passes through AccessMate servers. The API key is encrypted at rest using AES-256-CBC with your WordPress auth salt.
The OpenDyslexic font used by the toolbar’s dyslexia feature is bundled inside the plugin and served from your own site. No font CDN is contacted.
Third Party Libraries

axe-core by Deque Systems — Mozilla Public License 2.0 (MPL-2.0)
OpenDyslexic font via Fontsource — Bitstream Vera Fonts License — bundled with the plugin and served locally; no CDN request is made

External Services
This plugin can connect to the following external services. No external requests are made unless you explicitly configure and trigger the relevant feature.
AI providers (optional)
When you add an API key and click an AI action (fix suggestion or plain-English explanation), your WordPress server sends a direct HTTPS request to your chosen AI provider. The request contains the page HTML snippet and accessibility issue context being analysed. No data passes through AccessMate servers. These requests are only sent when you have entered an API key in Settings and manually trigger an AI action.
Anthropic — https://api.anthropic.com/
Used for: AI fix suggestions and plain-English issue explanations.
Data sent: page HTML snippet, accessibility issue context, and your Anthropic API key (in the request header).
Terms of Service | Privacy Policy
OpenAI — https://api.openai.com/
Used for: AI fix suggestions and plain-English issue explanations.
Data sent: page HTML snippet, accessibility issue context, and your OpenAI API key (in the request header).
Terms of Service | Privacy Policy
Google Gemini — https://generativelanguage.googleapis.com/
Used for: AI fix suggestions and plain-English issue explanations.
Data sent: page HTML snippet, accessibility issue context, and your Gemini API key (as a URL parameter).
Terms of Service | Privacy Policy
Ollama — http://localhost:11434/ (local only)
Ollama runs entirely on the user’s own machine or local network. No data is sent to any external server.
Source Code
The admin interface and scan overlay are built from TypeScript and React sources with Vite. The unminified sources are included in this plugin under /src and /widget, alongside package.json, tsconfig.json and the Vite configuration files. To rebuild the bundles in /assets, run npm install followed by npm run build.

延伸相關外掛

文章
Filter
Mastodon