Title: Limen Accessibility Audit
Author: limenae
Published: <strong>2026 年 9 月 22 日</strong>
Last modified: 2026 年 10 月 10 日

---

搜尋外掛

![](https://ps.w.org/limen-accessibility-audit/assets/banner-772x250.png?rev=3706604)

![](https://ps.w.org/limen-accessibility-audit/assets/icon-256x256.png?rev=3706600)

# Limen Accessibility Audit

 由 [limenae](https://profiles.wordpress.org/limenae/) 開發

[下載](https://downloads.wordpress.org/plugin/limen-accessibility-audit.1.0.2.zip)

 * [詳細資料](https://tw.wordpress.org/plugins/limen-accessibility-audit/#description)
 * [使用者評論](https://tw.wordpress.org/plugins/limen-accessibility-audit/#reviews)
 *  [安裝方式](https://tw.wordpress.org/plugins/limen-accessibility-audit/#installation)
 * [開發資訊](https://tw.wordpress.org/plugins/limen-accessibility-audit/#developers)

 [技術支援](https://wordpress.org/support/plugin/limen-accessibility-audit/)

## 外掛說明

Limen Accessibility Audit checks your published pages against **WCAG 2.1 Level AA**
and, for every failure it finds, shows you the specific code that fixes it in WordPress
or WooCommerce.

It is built around one uncomfortable fact that most accessibility tools skate over:**
automated testing finds roughly a third of accessibility barriers.** No scanner 
can tell whether your alt text is accurate, whether your headings actually describe
the content, or whether a keyboard user can finish checkout. This plugin says so
plainly, separates what it _proved_ from what a person still has to check, and never
issues a conformance claim.

#### What it does

 * Scans your home page and a sample of each content type — posts, pages, products,
   custom types
 * Reports **27 checks** across WCAG 2.1 Level A and AA
 * Separates **confirmed failures** from **checks that need a human**, and never
   counts the second group in your score
 * Shows the fix as WordPress-specific code you can copy, not generic advice
 * Orders findings by what actually appears in legal complaints, not by scanner 
   severity
 * Lists explicitly what it could not determine

#### Your pages are never uploaded

The scan runs entirely inside your browser tab. The plugin fetches your own pages
from your own site — same origin, no proxy — and audits them in JavaScript on your
machine.

There is no server in the path. This is not a privacy promise bolted on afterwards;
it is how the plugin is built, and it means the tool also works on staging sites,
password-protected pages, and logged-in views that an external crawler could never
reach.

#### Everything here is free

Every check, every score and every fix snippet is free and fully enabled, permanently.
Nothing is held back, and there is no paid version of this plugin.

#### Stores nothing, contacts nothing

The plugin writes nothing to your database: no options, no tables, no transients,
no scheduled tasks. It makes no requests to any external service. The only network
requests it makes are to your own site, from your own browser, to fetch the pages
it audits.

#### Source code

All of the code is included in the plugin, unminified. The audit engine lives in
the `engine/` folder as readable JavaScript.

## 螢幕擷圖

[⌊The scan result: confirmed failures separated from checks that need a person.⌉⌊
The scan result: confirmed failures separated from checks that need a person.⌉[

The scan result: confirmed failures separated from checks that need a person.

[⌊A finding expanded, with the WordPress-specific fix ready to copy.⌉⌊A finding 
expanded, with the WordPress-specific fix ready to copy.⌉[

A finding expanded, with the WordPress-specific fix ready to copy.

[⌊The honesty panel listing what automated testing cannot determine.⌉⌊The honesty
panel listing what automated testing cannot determine.⌉[

The honesty panel listing what automated testing cannot determine.

## 安裝方式

 1. Install and activate the plugin.
 2. Open **Accessibility** in the admin menu.
 3. Press **Scan my site**.

There is nothing to configure.

## 常見問題集

### Does this make my site accessible?

No, and be wary of anything that claims it will. It finds and explains a specific
set of failures. Fixing them is real work, and a clean result here means the automated
checks passed — not that your site is accessible. The plugin tells you exactly which
questions it could not answer.

### Does it slow my site down?

No. The plugin adds nothing whatsoever to your front end — no scripts, no styles,
no database queries for visitors. It only runs inside wp-admin, and only while you
are looking at its screen.

### Is this an accessibility overlay or widget?

No. Overlays attempt to patch your site at runtime for visitors and have been widely
shown not to work; one major vendor has faced FTC action. This plugin changes nothing
on your site. It tells you what is broken and shows you how to fix it properly, 
in your own theme.

### Will it edit my theme for me?

No, deliberately. It shows you the code and where it goes. A plugin that rewrote
your templates automatically would be one bad guess away from breaking your site,
and it would also disqualify the tool from being an evaluation tool at all.

### Who can run a scan?

Anyone who can edit posts, because the people who introduce accessibility problems
are usually the people writing content. The capability is filterable via `exhibit_a_capability`.

### Does it work on a site that is not public yet?

Yes. Because the scan runs in your browser using your own session, it works on staging
sites, sites behind HTTP auth, and pages that require login — none of which an external
scanner can reach.

### Does it help with the European Accessibility Act or the ADA?

It helps with the part of both that can be tested automatically. The European Accessibility
Act, in force since 28 June 2025 for online shops selling to EU consumers, points
to WCAG 2.1 Level AA through the standard EN 301 549, and US accessibility claims
under the ADA almost always cite WCAG too. This plugin tests 27 WCAG 2.1 A and AA
rules and shows how to fix each failure. It cannot tell you that your site complies
with either law, and nothing automated can: about two thirds of barriers need a 
person to judge them.

### Does it check WooCommerce product and checkout pages?

It scans your home page and a sample of each public content type, including WooCommerce
products, and its fixes cover WooCommerce templates. The cart and checkout depend
on a shopping session, so check those with the free Limen Chrome extension, which
audits a page exactly as your browser shows it, including logged-in and checkout
pages: https://chromewebstore.google.com/detail/limen-accessibility-audit/ghiolennoknelppjjicdmnhgkhogicol

### What standard does it check?

WCAG 2.1 Level A and AA. Not 2.2, and not 2.0 — 27 rules implemented against 2.1,
and the plugin does not claim coverage it does not have.

## 使用者評論

這個外掛目前沒有任何使用者評論。

## 參與者及開發者

以下人員參與了開源軟體〈Limen Accessibility Audit〉的開發相關工作。

參與者

 *   [ limenae ](https://profiles.wordpress.org/limenae/)

[將〈Limen Accessibility Audit〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/limen-accessibility-audit)

### 對開發相關資訊感興趣？

任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/limen-accessibility-audit/)、
查看 [SVN 存放庫](https://plugins.svn.wordpress.org/limen-accessibility-audit/)，
或透過 [RSS](https://plugins.trac.wordpress.org/log/limen-accessibility-audit/?limit=100&mode=stop_on_copy&format=rss)
訂閱[開發記錄](https://plugins.trac.wordpress.org/log/limen-accessibility-audit/)。

## 變更記錄

#### 1.0.2

 * The plugin’s description, tags and FAQ now say plainly what it is: a free accessibility
   checker for WordPress and WooCommerce. New answers on the European Accessibility
   Act, the ADA, and WooCommerce checkout pages.
 * A single line under the scan results invites a review on WordPress.org. It is
   part of the plugin’s own screen only: no admin notice, no pop-up, and nothing
   stored.
 * No change to the checks or their results.

#### 1.0.1

 * Fix: a link inside aria-hidden=”true” that also has tabindex=”-1″ is no longer
   reported as a focusable hidden element. This is the recommended pattern for a
   redundant product-card image link, and it matches axe-core. A plain link or a
   tabindex=”0″ element inside aria-hidden is still reported.
 * Fix: fewer false reports. A control inside

## 中繼資料

 *  版本 **1.0.2**
 *  最後更新 **10 小時前**
 *  啟用安裝數 **少於 10 次**
 *  WordPress 版本需求 ** 6.0 或更新版本 **
 *  已測試相容的 WordPress 版本 **7.1.3**
 *  PHP 版本需求 ** 7.4 或更新版本 **
 *  語言
 * [English (US)](https://wordpress.org/plugins/limen-accessibility-audit/)
 * 標籤:
 * [accessibility](https://tw.wordpress.org/plugins/tags/accessibility/)[accessibility checker](https://tw.wordpress.org/plugins/tags/accessibility-checker/)
   [ada](https://tw.wordpress.org/plugins/tags/ada/)[wcag](https://tw.wordpress.org/plugins/tags/wcag/)
   [woocommerce](https://tw.wordpress.org/plugins/tags/woocommerce/)
 *  [進階檢視](https://tw.wordpress.org/plugins/limen-accessibility-audit/advanced/)

## 評分

這個項目尚無任何評論記錄。

[撰寫評分](https://wordpress.org/support/plugin/limen-accessibility-audit/reviews/#new-post)

[查看全部使用者評論](https://wordpress.org/support/plugin/limen-accessibility-audit/reviews/)

## 參與者

 *   [ limenae ](https://profiles.wordpress.org/limenae/)

## 技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

 [檢視技術支援論壇](https://wordpress.org/support/plugin/limen-accessibility-audit/)