Title: ComplyClear Accessibility
Author: Startec Web Solutions
Published: <strong>July 9, 2026</strong>
Last modified: July 9, 2026

---

Search plugins

![](https://s.w.org/plugins/geopattern-icon/complyclear-accessibility.svg)

# ComplyClear Accessibility

 By [Startec Web Solutions](https://profiles.wordpress.org/dmdstar/)

[Download](https://downloads.wordpress.org/plugin/complyclear-accessibility.1.0.1.zip)

 * [Details](https://wordpress.org/plugins/complyclear-accessibility/#description)
 * [Reviews](https://wordpress.org/plugins/complyclear-accessibility/#reviews)
 *  [Installation](https://wordpress.org/plugins/complyclear-accessibility/#installation)
 * [Development](https://wordpress.org/plugins/complyclear-accessibility/#developers)

 [Support](https://wordpress.org/support/plugin/complyclear-accessibility/)

## Description

**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.

#### What the automated scan checks

While you edit a page (Elementor or the block editor), the live scan checks:

 * 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 (1.3.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).
 * 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.

The site-wide report scans every published page, post, and uploaded document on 
the server:

 * Page title (2.4.2), site language (3.1.1), iframe titles, video caption tracks(
   1.2.2), and viewport zoom blocking (1.4.4), 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.

#### What still needs a human

Automated testing reliably catches roughly 30 to 50% of WCAG success criteria. The
rest need a person, and this plugin is built to tell you plainly what it could not
check for you, so nothing gets mistaken for a clean bill of health:

 * 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.

#### Important disclaimer

This plugin assists with building and maintaining accessible content. It does not
by itself guarantee or certify legal WCAG, ADA, or Section 508 conformance, and 
no tool can. Pair it with the manual checks above.

## Installation

 1. Upload the `complyclear-accessibility` folder to `/wp-content/plugins/`, or install
    the ZIP via **Plugins  Add New  Upload Plugin**.
 2. Activate the plugin through the **Plugins** menu.
 3. Go to **Settings  ComplyClear** to choose your WCAG standard and enter your agency
    details.
 4. (Optional) Edit a page in Elementor and open the **“Accessibility”** tab on the
    right edge of the editor panel.

## FAQ

### 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.

### Do I need Elementor?

No. The site-wide report, statement generator, and code-level improvements work 
on any theme. Elementor is required only for the real-time editor panel and the 
accessibility widgets.

### 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.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“ComplyClear Accessibility” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ Startec Web Solutions ](https://profiles.wordpress.org/dmdstar/)

[Translate “ComplyClear Accessibility” into your language.](https://translate.wordpress.org/projects/wp-plugins/complyclear-accessibility)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/complyclear-accessibility/),
check out the [SVN repository](https://plugins.svn.wordpress.org/complyclear-accessibility/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/complyclear-accessibility/)
by [RSS](https://plugins.trac.wordpress.org/log/complyclear-accessibility/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.1

 * 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.

#### 1.0.0

First public release. ComplyClear Accessibility audits your content against WCAG
2.1 and 2.2 AA and Section 508, in the Elementor and block editors and across your
whole site, with plain-language fixes and an accessibility statement generator.
*
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).

#### 0.5.2

 * 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.”

#### 0.5.1

 * 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.

#### 0.5.0

 * 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.

#### 0.4.2

 * 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.

#### 0.4.1

 * 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.

#### 0.4.0

 * 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.

#### 0.3.0

 * 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.

#### 0.2.1

 * 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.

#### 0.2.0

 * 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.

#### 0.1.17

 * 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.

#### 0.1.16

 * 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.

## Meta

 *  Version **1.0.1**
 *  Last updated **13 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.0.1**
 *  PHP version ** 8.1 or higher **
 * Tags
 * [accessibility](https://wordpress.org/plugins/tags/accessibility/)[accessibility checker](https://wordpress.org/plugins/tags/accessibility-checker/)
   [ada](https://wordpress.org/plugins/tags/ada/)[Section 508](https://wordpress.org/plugins/tags/section-508/)
   [wcag](https://wordpress.org/plugins/tags/wcag/)
 *  [Advanced View](https://wordpress.org/plugins/complyclear-accessibility/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/complyclear-accessibility/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/complyclear-accessibility/reviews/)

## Contributors

 *   [ Startec Web Solutions ](https://profiles.wordpress.org/dmdstar/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/complyclear-accessibility/)