by Startec Web Solutions 0 (0 reviews)

ComplyClear Accessibility

Name: ComplyClear Accessibility
Author: Startec Web Solutions

Audit WCAG 2.1/2.2 AA and Section 508 in real time. Build accessibly in Elementor, generate an accessibility statement, and report site-wide.

ComplyClear Accessibility ranks #70,254 among WordPress.org plugins with 0+ active installations, is #496 of 765 in the Accessibility category, and was last updated Sep 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.1.0 Current Version v1.1.0

Updated 1 month ago Last Update on 21 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#496 of 765 in Accessibility

View on WordPress.org

Rank

#70,254

— No change

Active Installs

-100%

KW Avg Position

100.3

1 worse

Downloads

693

+8 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

42,686

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 10 more installs to reach 10+

Rank Changes

Current #70,254

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.1.0
Last Updated: Sep 21, 2026
Requires WP: 6.0+
Tested Up To: 7.1.4
PHP Version: 8.1 or higher
Author: Startec Web Solutions

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

accessibility accessibility checker ada Section 508 wcag

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades

100K+ installs

#360

Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)

100K+ installs

#428

404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring

100K+ installs

#429

Accessibility by UserWay

80K+ installs

#509

Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar

AccessiYes Accessibility Widget for ADA, EAA & WCAG Readiness

20K+ installs

#1,116

View all Accessibility plugins

Frequently Asked Questions

Common questions about ComplyClear Accessibility

No tool can do that alone. Compliance requires both automated and manual testing plus human judgment. This plugin gives you a prioritized, standards-mapped to-do list and helps you fix issues in your real content.

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.

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.

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. The plugin defaults to 2.2 AA because it is good practice, not because it is required of you. 2.1 AA is the technical standard the DOJ Title II rule sets, so choose it if you want to audit against that minimum on its own, or if a contract or policy names it.

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.

WordPress does not have a clock of its own. Scheduled work is checked when somebody loads a page on the site, so when you save a page the audit is queued rather than run on the spot. On a site with visitors that means a short delay. On a quiet site, or one behind a full-page cache that serves visitors without ever reaching WordPress, it can be a long one, because nothing has prompted WordPress to look. Opening the plugin's own screens counts as a page load, so if a result looks stale, loading the Report tab is usually enough to prompt it. Some hosts already replace this mechanism with a real scheduler, and some do not let you set up your own. Before changing anything, check the documentation for your host or ask their support. If you do need to set it up yourself, the standard approach is to stop WordPress checking on page loads by adding define( 'DISABLE_WP_CRON', true ); to wp-config.php, and then arrange for something to request wp-cron.php?doing_wp_cron on your site every fifteen minutes instead. A scheduled task in your hosting control panel can do that without any command line; so can a server cron entry, wp cron event run --due-now if your host provides WP-CLI, or an external scheduling service. That removes the dependency on visitor traffic, which is the common cause of a delay. It does not make anything certain: a run can still fail because the site was unreachable at that moment, because a server time limit cut it short, or because the scheduled task quietly stopped being run. Treat what the plugin shows you as the record of what actually happened.

Everything stays on your own site, in your WordPress database. No content is sent to any third-party service.

ComplyClear stores your settings, your scan results, and the details you enter for your accessibility statement. Scan results are stored against each page. It does not create any database tables of its own. Deactivating or deleting the plugin leaves that data in place by default, so you do not lose your scan history by turning the plugin off and on again. If you do want it removed, there is a setting for it on the Settings screen, under "Removing this plugin". Tick it and this plugin's data is deleted when you delete this plugin. It is off unless you turn it on, deactivating does not trigger it, and there is no export step, so read the warning on that screen before you use it. Each plugin removes only its own data. This setting covers ComplyClear Accessibility: the scan results stored on each page, your accessibility statement details, and its settings. ComplyClear Accessibility Pro keeps its own scan history, schedule and dismissed issues, and those are removed when you delete Pro. Deleting both removes both. Your published accessibility statement page is not deleted, because it is a page your site owns. A ComplyClear Pro license is never deleted either. Automatic removal is not supported on multisite networks. On multisite nothing is deleted, because a network delete would clear one site and silently leave every other site's data behind.