Title: Adinav Accessibility Audit for EAA Author: adinav Published: 2026 年 7 月 17 日 Last modified: 2026 年 7 月 17 日 --- 搜尋外掛 ![](https://ps.w.org/adinav-accessibility-audit-eaa/assets/banner-772x250.png?rev =3611495) ![](https://ps.w.org/adinav-accessibility-audit-eaa/assets/icon-256x256.png?rev= 3611495) # Adinav Accessibility Audit for EAA 由 [adinav](https://profiles.wordpress.org/adinav/) 開發 [下載](https://downloads.wordpress.org/plugin/adinav-accessibility-audit-eaa.0.1.0.zip) * [詳細資料](https://tw.wordpress.org/plugins/adinav-accessibility-audit-eaa/#description) * [使用者評論](https://tw.wordpress.org/plugins/adinav-accessibility-audit-eaa/#reviews) * [安裝方式](https://tw.wordpress.org/plugins/adinav-accessibility-audit-eaa/#installation) * [開發資訊](https://tw.wordpress.org/plugins/adinav-accessibility-audit-eaa/#developers) [技術支援](https://wordpress.org/support/plugin/adinav-accessibility-audit-eaa/) ## 外掛說明 The European Accessibility Act (Directive (EU) 2019/882) has applied since **28 June 2025**. It covers e-commerce, banking, transport, telecoms and consumer digital services. The standard it requires is **EN 301 549**, which applies **WCAG 2.1 Level AA**. Enforcement is no longer theoretical. The first EAA lawsuits in Europe were filed in **France in November 2025**, and national market-surveillance authorities are now actively supervising. **Adinav Accessibility Audit for EAA scans the HTML your visitors actually receive** and reports every barrier it can prove is there — with the exact element, the WCAG success criterion it breaks, the EN 301 549 clause a regulator would cite, and how to fix it in code. #### This is not an overlay Overlay widgets that promise instant compliance from one line of JavaScript **do not deliver compliance**. The EU has never endorsed them, European disability organisations have rejected them, and their presence on a site is increasingly read by regulators as evidence that the site was never made accessible in the first place. This plugin changes nothing on your front end. It adds no script, no widget, no banner. It tells you the truth about your site and gets out of the way. #### What it checks Every check runs against WCAG 2.1 A and AA, mapped to the EN 301 549 clause: * Images with no alt attribute, and alt text that is just a file name * Form fields with no label — the single most common checkout blocker * Buttons and links with no accessible name (icon-only carts, hamburger menus, close buttons) * Link text that says nothing out of context (“Read more”, “Cliquez ici”) * Missing page language, missing page title * Skipped heading levels, empty headings, missing h1 * iframes with no title * Data tables with no header cells * Duplicate ids that silently break label associations * Positive tabindex that wrecks keyboard order * `aria-hidden` containers that still trap keyboard focus * Pinch-to-zoom disabled on mobile (`user-scalable=no`) * Timed page refreshes * Video without captions; audio or video that autoplays with sound * Missing `autocomplete` on personal-data fields (WCAG 1.3.5 AA — inside the EAA’s required level, and almost universally missed) * Missing `main` landmark * Colour contrast below 4.5:1, where it can be verified with certainty #### It tells you what it cannot know Automated testing cannot prove compliance, and this plugin will never tell you it has. Colour contrast defined in stylesheets, keyboard focus order, and the behaviour of dynamic content can only be confirmed by a manual test with assistive technology. The report says so, plainly, instead of handing you a green tick you cannot rely on in front of a regulator. A false positive is worse than a missed issue. Every rule here fires only on evidence present in the page source. #### Accessibility statement generator The EAA does not only require an accessible service — it requires you to **publish information about how you meet the requirements**. This plugin generates that statement from your real scan results, **including the failures it found**. It will not write“ fully compliant” for you: a compliance claim that a regulator can disprove in thirty seconds with a screen reader turns an accessibility problem into a false-declaration problem. ### Privacy This plugin sends no data anywhere. It makes HTTP requests only to your own site’s public pages, exactly as a visitor’s browser would, and stores the results in your own database. There is no telemetry, no external API, no account, and no tracking. Uninstalling it removes its table and its options completely. ## 螢幕擷圖 [⌊The dashboard: what is broken, most damaging first.⌉⌊The dashboard: what is broken, most damaging first.⌉[ The dashboard: what is broken, most damaging first. [⌊Every occurrence, with the element, the criterion, and the fix.⌉⌊Every occurrence, with the element, the criterion, and the fix.⌉[ Every occurrence, with the element, the criterion, and the fix. [⌊The accessibility statement, generated from real results.⌉⌊The accessibility statement, generated from real results.⌉[ The accessibility statement, generated from real results. ## 安裝方式 1. Upload the plugin to `/wp-content/plugins/`, or install it from the Plugins screen. 2. Activate it. 3. Go to **Accessibility Audit** and press **Run accessibility scan**. It changes nothing on your site. It only reads your pages, the way a visitor would. ## 常見問題集 ### Does this make my site compliant? No, and be suspicious of anything that says it does. This finds barriers and tells you how to fix them. The fixes happen in your theme and your content. That is the only kind of compliance that exists. ### Is an accessibility overlay easier? It is easier, and it does not work. Overlays are not recognised by EU regulators as meeting the EAA, and disability organisations have consistently rejected them. Installing one does not remove your legal exposure; it documents that you looked for a shortcut. ### Which pages are scanned? The highest-risk ones first: home, shop, cart, checkout, and account, then your pages and posts. Checkout is prioritised because an inaccessible checkout form is where an accessibility barrier stops being an inconvenience and becomes a lost sale and a legal exposure. ### Does it work with WooCommerce? Yes. If WooCommerce is active, its shop, cart, checkout and account pages are scanned first. ## 使用者評論 這個外掛目前沒有任何使用者評論。 ## 參與者及開發者 以下人員參與了開源軟體〈Adinav Accessibility Audit for EAA〉的開發相關工作。 參與者 * [ adinav ](https://profiles.wordpress.org/adinav/) [將〈Adinav Accessibility Audit for EAA〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/adinav-accessibility-audit-eaa) ### 對開發相關資訊感興趣？ 任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/adinav-accessibility-audit-eaa/)、 查看 [SVN 存放庫](https://plugins.svn.wordpress.org/adinav-accessibility-audit-eaa/)， 或透過 [RSS](https://plugins.trac.wordpress.org/log/adinav-accessibility-audit-eaa/?limit=100&mode=stop_on_copy&format=rss) 訂閱[開發記錄](https://plugins.trac.wordpress.org/log/adinav-accessibility-audit-eaa/)。 ## 變更記錄 #### 0.1.0 * First release. ## 中繼資料 * 版本 **0.1.0** * 最後更新 **6 天前** * 啟用安裝數 **少於 10 次** * WordPress 版本需求 ** 6.0 或更新版本 ** * 已測試相容的 WordPress 版本 **7.0.2** * PHP 版本需求 ** 7.4 或更新版本 ** * 語言 * [English (US)](https://wordpress.org/plugins/adinav-accessibility-audit-eaa/) * 標籤: * [a11y](https://tw.wordpress.org/plugins/tags/a11y/)[accessibility](https://tw.wordpress.org/plugins/tags/accessibility/) [audit](https://tw.wordpress.org/plugins/tags/audit/)[compliance](https://tw.wordpress.org/plugins/tags/compliance/) [wcag](https://tw.wordpress.org/plugins/tags/wcag/) * [進階檢視](https://tw.wordpress.org/plugins/adinav-accessibility-audit-eaa/advanced/) ## 評分 這個項目尚無任何評論記錄。 [Your review](https://wordpress.org/support/plugin/adinav-accessibility-audit-eaa/reviews/#new-post) [查看全部使用者評論](https://wordpress.org/support/plugin/adinav-accessibility-audit-eaa/reviews/) ## 參與者 * [ adinav ](https://profiles.wordpress.org/adinav/) ## 技術支援 使用者可在技術支援論壇提出意見反應或使用問題。 [檢視技術支援論壇](https://wordpress.org/support/plugin/adinav-accessibility-audit-eaa/)