ComplyClear Accessibility

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.