ComplyClear Accessibility
| 开发者 | dmdstar |
|---|---|
| 更新时间 | 2026年7月27日 21:25 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
An accessibility tool that works on your site's real markup.
Most "accessibility" plugins add a floating widget that recolors text or reads pages aloud. Those overlays do not make a site compliant, and overlay vendors have been named in hundreds of ADA lawsuits because the underlying markup stays inaccessible.
ComplyClear Accessibility works the other way around. It surfaces real WCAG problems in your content and helps your team fix them at the source. It is purpose-built for government and public-sector websites with Section 508 and ADA Title II obligations.
Key features
- Real-time editor audit. A sidebar in the Elementor and block editors that scans the page you're editing and lists issues as errors and warnings, with click-to-navigate to the exact element.
- WCAG 2.1 vs 2.2 AA selector. 2.1 AA by default (the DOJ Title II technical standard). The auditor adjusts its rules to the chosen standard.
- One-click Accessibility Statement generator. A complete, properly structured draft page covering conformance status, feedback channels, known limitations, assessment approach, and formal-complaint rights.
- Site-wide accessibility report. Server-side scan of all published pages and posts.
- Code-level improvements. Skip-navigation links (2.4.1), enforced visible focus indicators (2.4.7), and
<html lang>enforcement (3.1.1). - Accessibility widgets for Elementor. Statement, issue-report contact form, conformance checklist, and accessibility status badge.
- Images missing alt text, and alt text that looks like a file name instead of a description (1.1.1).
- Heading structure: skipped levels and empty headings (1.3.1 / 2.4.6).
- Links and buttons with no accessible name, and vague link text like "click here" (2.4.4 / 4.1.2).
- Form fields with no label, and missing input-purpose autocomplete on contact fields (1.3.1 / 1.3.5).
- Data tables with no header cells or caption, with layout tables recognized and handled separately (1.3.1).
- Mouse-only event handlers and click handlers on non-interactive elements, which keyboard users cannot reach (2.1.1).
- Color contrast of text against its real background (1.4.3).
- In-text links set apart by color alone, with no underline or other cue (1.4.1).
- Required fields whose visible label does not say they are required (3.3.2), and form status messages that screen readers will not announce (4.1.3).
- Buttons and links whose visible text is missing from their accessible name, which breaks voice control (2.5.3).
- Links that open a new window without warning, iframes with no title (4.1.2), very long alt text that may be an image of text (1.4.5), videos without caption tracks, embedded video to verify (1.2.2), and media that autoplays with sound (1.4.2).
- Duplicate IDs (4.1.1). On WCAG 2.2: tap-target size (2.5.8), focus not obscured (2.4.11), and dragging alternatives (2.5.7).
- Keyboard reachability and tab-order signals (2.1.1 / 2.4.3), raised as "verify this" advisories.
- Page title (2.4.2), site language (3.1.1), viewport zoom blocking (1.4.4), timed refresh or redirect (2.2.1), and a skip link or main landmark (2.4.1), plus the structural checks above that can be read from the page markup.
- PDF and Word files in the Media Library: tagging, language, a title that displays, a real text layer, heading structure, image alt text, and table headers.
- Whether alt text and captions are actually accurate and meaningful, not only present.
- Keyboard operation end to end: tab through the published page, operate every control, and confirm the focus order makes sense.
- A screen-reader pass: NVDA on Windows, VoiceOver on macOS, or Orca on Linux.
- Visible focus styles in practice (2.4.7). The plugin can add a global focus style for you under Settings, but it does not grade your theme's own focus styling.
- Color or shape used as the only way to convey meaning beyond links, for example "required fields are red," or status shown by color alone.
- Captions and transcripts for video and audio. For YouTube embeds, turn captions on and review the auto-generated text for accuracy, or upload your own.
- Meaning, reading order, and page context that only a person can judge.
安装:
- Upload the
complyclear-accessibilityfolder to/wp-content/plugins/, or install the ZIP via Plugins → Add New → Upload Plugin. - Activate the plugin through the Plugins menu.
- Go to Settings → ComplyClear to choose your WCAG standard and enter your agency details.
- (Optional) Edit a page in Elementor and open the "Accessibility" tab on the right edge of the editor panel.
屏幕截图:
常见问题:
Does this make my site ADA compliant?
No tool can do that alone. Compliance requires both automated and manual testing plus human judgement. This plugin gives you a prioritized, standards-mapped to-do list and helps you fix issues in your real content.
What page builders are supported?
The real-time editor panel, with click-to-navigate highlighting and plain-language guidance, works in both the Elementor editor and the WordPress block editor today. Support for more builders is being considered and will be prioritized by demand, so tell us which one your team uses.
Does it work without a page builder?
Yes. The site-wide accessibility report with per-page findings, the PDF and Word document checks, the accessibility statement generator, and the code-level improvements (skip-to-content links, visible focus outlines, and the page language attribute) all run on any theme, with or without a page builder. Only the in-editor panel is builder-specific.
What's the difference between WCAG 2.1 and 2.2?
2.2 is the current W3C standard and adds criteria such as Target Size (2.5.8) and Focus Not Obscured (2.4.11), while removing the deprecated 4.1.1 Parsing criterion. Choose 2.1 only if a specific contract or policy requires it.
Is this an accessibility overlay?
No, and that is deliberate. Overlays are widely criticized and have been the subject of numerous lawsuits. This plugin helps you remediate the underlying markup instead.
Where is the data stored?
Audit results are computed on demand and cached transiently. No content is sent to any third-party service.
更新日志:
1.0.6
- Accuracy pass. Several checks were reporting problems that were not actually there, and a few were reported with more certainty than a page scan can support. Findings are now labelled by how well they can be established, so a real failure is never confused with something that just needs a look.
- Every finding now says whether it is a confirmed failure, something that needs review, a manual check, or advisory guidance. Confirmed means the page itself shows the problem. Nothing else is presented as a failure.
- Removed checks that were applying the wrong standard: a CAPTCHA on an ordinary page is not an Accessible Authentication failure, a page without a help link is not a Consistent Help failure, and a form with several fields is not evidence of Redundant Entry.
- A missing table caption and an unwarned new-window link are now advisory notes rather than failures. Both are recommended techniques, not requirements.
- Colour contrast is now a manual check. The previous check guessed at the background when it could not see one, which produced false failures on dark sections and quietly skipped light text entirely. It now tells you what to check instead of guessing.
- Tap target size is now a manual check. It was estimating from link text length rather than the rendered size, which is not something a page scan can measure.
- Decorative images marked with role="presentation" or aria-hidden are no longer reported as missing alt text. An image with empty alt that is the only content of a link is still reported, because that link has no name.
- Hidden form fields, including spam honeypots, are no longer reported as unlabelled. They are not shown to anyone.
- Timed refresh: a redirect with no delay is no longer flagged, and very long delays are exempt as the standard intends.
- Fixed a missed failure: a link whose aria-labelledby pointed at an element that does not exist was treated as if it had a name. That is a real problem for screen reader users and was being skipped.
- The numeric score has been removed for now, since it was calculated from the checks corrected above. Findings and coverage are shown instead.
- Fixed the "Report an Issue" contact form in the accessibility widget, which could not submit. Reports now send properly, show a confirmation message in place, and work even with JavaScript turned off. If your site shows this widget with the contact form, please update.
- Vague link text such as "Read more" is no longer flagged when the link has a descriptive accessible name from aria-label, aria-labelledby, or a title attribute. This matches how screen readers announce the link and how the in-editor check already judged it, so the site report and the editor now agree.
- Hardened the PDF document scanner against malformed files: a damaged or crafted PDF can no longer crash the media uploader, and files that cannot be read are now reported honestly as "could not be checked" instead of failing silently.
- PDFs saved with incremental updates are no longer misread as scanned, image-only documents.
- Code snippets in the site-wide report now display correctly instead of showing raw HTML entity codes.
- Word (.docx) documents are now scanned with the same safeguards as PDFs, and unusually large or highly compressed files are handled gracefully instead of straining the server.
- The plugin no longer adds its own viewport tag, which could duplicate the one your theme already sets. Skip links now hide automatically when their target is not present in the theme, so a visitor never lands on a broken skip link.
- The Documents report and the Media Library accessibility column are now more accurate. A file that changed after it was scanned, or whose type no longer matches, is shown as needing a rescan instead of keeping an old result.
- Very large or unusually complex pages now report as incomplete with guidance, rather than returning a partial score, so a page that could not be fully checked is never mistaken for a clean pass.
- Additional security hardening in document parsing and the Elementor editor preview.
- Fixed a false contrast error in the block editor. Text placed over a Cover block or a page-builder color overlay was being measured against the wrong background and could be reported as failing when it was fine. The editor now reads the actual color behind the text, so white text on a colored hero passes as it should. Genuine low-contrast text is still caught.
- Fewer false positives on tables used for visual layout. A table with no header cells and no caption is usually a layout table, so instead of asking you to add headers and a caption (the wrong fix for layout), the tool now raises a single advisory to confirm it and, if it is layout, add role="presentation". Real data tables are still checked for headers and a caption.
- New keyboard checks: elements that respond only to the mouse (a hover handler with no keyboard equivalent) and click handlers placed on something that is not a button or link, both of which leave keyboard users stuck (2.1.1).
- Links injected by a CDN such as Cloudflare (paths under /cdn-cgi/) are no longer flagged, since they are not part of your source and you cannot edit them.
- Detection results were cross-checked against axe-core and WAVE on a standard test page to keep this tool consistent with the checkers people already use.
- Six new detections, checked in the editors and in the site-wide report: form status messages that screen readers will not announce (4.1.3), buttons and links whose visible text is missing from their accessible name, which breaks voice control (2.5.3), media that autoplays with sound and no controls (1.4.2), pages that refresh or redirect themselves on a timer (2.2.1), required fields whose label does not say they are required (3.3.2), and pages with no skip link or main landmark (2.4.1).
- The editor panel now also checks what the site report already covered, so the two never disagree: very long alt text that may be an image of text (1.4.5), iframes with no title (4.1.2), links that open a new window without warning (4.1.2), and videos without caption tracks (1.2.2).
- Fewer false flags: a muted background video with no controls is no longer asked for captions, and the new name matching ignores punctuation and arrows so a "Read more" link with a longer aria-label passes.
- Verified against WordPress 7.0.1 in both editors.
- Fewer false positives on page-builder layouts. A plain section with no accessible name is no longer flagged as an unlabeled landmark. Builders like Elementor wrap content in many sections, and an unnamed section is not announced as a landmark, so it does not belong in that check. Multiple navigation or complementary regions without unique labels are still flagged.
- Clearer contrast results for text over background images. When a solid color overlay sits over the image, the tool now measures the real contrast against it instead of asking for a manual review. The cases that genuinely cannot be measured are grouped into a single advisory rather than one warning per element.
- The focus-obscured check (WCAG 2.4.11) no longer flags small corner widgets such as the reCAPTCHA badge, chat bubbles, or back-to-top buttons. It now looks only at wide sticky bars that could actually cover a focused element.
- Clearer wording on the autocomplete suggestion for email and phone fields, explaining that the autocomplete attribute is separate from the field type and what it does for people who rely on auto-fill.
- More accurate contrast on tinted sections. A translucent background color (such as a light color overlay on a section) is now blended with the background behind it before measuring, instead of being read as a solid color. This removes false contrast failures on text that sits on a subtle tint.
- One detection engine for both editors, environment-aware so each check runs only where it reads reliably.
- New checks: alt text that looks like a file name (1.1.1) and in-text links distinguished by color alone (1.4.1).
- Accuracy: image and logo links now take their accessible name from the image they contain, and images explicitly marked decorative no longer raise an empty-alt advisory.
- The readme now spells out what the scan checks and what still needs a human (alt and caption accuracy, end-to-end keyboard, screen-reader testing, real focus styles).
- The admin bar now shows a "ComplyClear Accessibility" menu that links to each settings section (Report, Documents, Statement, Settings), and it works on the block editor and on sites without a page builder.
- Settings tabs are now extensible, so the Pro add-on can add its own License tab.
- Renamed the report section to "Accessibility Report."
- The block editor panel now scans automatically the first time you open it, so issues appear without clicking Run scan first. This matches the Elementor panel.
- Both editor panels now share one accessibility engine, so the Elementor and block editor audits apply the same checks wherever they can be measured reliably. The block editor gains checks it did not run before, including empty headings, missing form autocomplete, tables marked as presentational, duplicate landmark labels, and tap-target size on WCAG 2.2.
- The full audit, click-to-locate, and plain-language fix guidance remain free in both editors. One-click fixes and live auto-scan are moving to the upcoming Pro add-on.
- A manual rescan now clears the list while it re-checks, so it is clear the scan has started over.
- Elementor panel: the audit tab now shows a separate amber count for warnings alongside the red error count, so a page with only warnings is no longer mistaken for a clean one at a glance.
- Elementor panel: fixed the audit tab lingering over the canvas after the panel was dragged loose. While the panel floats it carries its own close button, and the tab returns when the panel is closed or re-docked.
- Block editor panel: each image with empty alt text now has its own "scroll to block" link instead of one combined note.
- Block editor panel: text placed over a background image is now flagged for manual contrast review, rather than skipped, since its contrast cannot be measured automatically.
- Block editor panel: scan results are kept when you switch to another sidebar (such as Settings) and back, so you no longer have to re-run the scan.
- New: real-time accessibility panel in the block editor (Gutenberg). A pinnable sidebar scans the page you are editing, lists issues with plain-language guidance, and scrolls straight to the block that needs attention. It works alongside the existing Elementor panel and on sites that do not use a page builder.
- Rebranded to ComplyClear Accessibility. The plugin, settings, REST API, and assets now use the ComplyClear name and the complyclear-accessibility slug. Existing settings carry over automatically. References to the WCAG standard itself are unchanged.
- Documents are now scanned automatically the moment they are uploaded, so problems surface right away.
- The Media Library list view shows an Accessibility column for each PDF and Word file (errors, warnings, or passed), linking to the Documents report.
- New: Document accessibility scanning. A "Documents" tab in the Compliance area scans the PDF and Word files in your Media Library and reports issues with plain-language fixes. Posted documents fall under the same ADA Title II obligation as web pages, and nothing else in WordPress surfaces these problems.
- PDF checks: tagging, document language, a title that displays, a real text layer versus a scanned image, bookmarks on long files, and encryption. Reads real-world PDFs correctly, including compressed cross-reference and object streams.
- Word (.docx) checks: language, title, heading styles for structure, image alternative text, and table header rows. Scanning the source is where most problems start and where they are fixable, and a well-structured source also exports a clean PDF.
- This is detection only and is part of the free feature set. It flags issues and explains how to fix them at the source; it does not change your files.
- Elementor's colour picker and other control popovers now appear above the audit panel instead of behind it. The panel sits below Elementor's popup layer while staying above the canvas, so picking a colour over the panel area works normally.
- Versioning note: ahead of the public 1.0.0 launch the plugin adopted 0.x pre-release version numbers.
- The audit panel now sits just below the editor's top bar, matching the Elements panel, instead of overlapping it.