3 versions
EaseAccess history.
Every release of EaseAccess is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.
3 of 3 releases scanned clean
v2.2.0Latest
September 10, 20261.6 MBScanned
Added
- **Automatic plugin updates.** EaseAccess now ships with a built-in updater — customers see "Update available" in the Plugins list and can update in one click, no more manual downloads.
- **Deactivation feedback modal.** If you deactivate EaseAccess we ask a quick question about why. Optional — you can always skip.
- **Dictionary fallback.** When the primary dictionary provider (api.dictionaryapi.dev) returns 5xx or times out, the widget silently falls back to Wiktionary — end users no longer see "service unavailable" when the free API is down.
- **Translate fallback.** When Google's unofficial translate endpoint blocks the request (429 / 403 / HTML challenge page), the widget silently falls back to MyMemory — pages continue to translate on shared-IP hosts.
- underlines links inside paragraphs and lists so they're distinguishable without colour (WCAG 1.4.1). Buttons, menus and image links are left alone.
- server-side structural fixes. The plugin now repairs the delivered HTML on the server — removing zoom-blocking viewport settings, de-duplicating banner/footer landmarks, and giving repeated navigation/sidebar regions unique labels — so third-party audits (Lighthouse, WAVE, axe) see the fixes, not just the live browser.
- the accessibility scan now reports a real audit score. It counts passing rules and issues (like a professional audit) instead of a setup-only estimate, so the compliance score actually moves as you fix issues.
- scan results now show issue severity (critical / serious / moderate / minor), how many elements each issue affects, and how many checks passed.
- a "Needs review" section surfaces checks the scanner can't decide automatically (e.g. contrast over a background image) so nothing is silently hidden.
- added WCAG 2.2 minimum target-size (2.5.8) detection and a check for multiple ` ` headings on a page.
- **Unique Landmark Labels** — when a page has more than o
Fixed
- (Accessibility): the widget launcher, feature toggles, panel controls (Reset / Close / Language), Accessibility Profiles, Big Cursor variants and Pointer Trail colors are now native ` ` elements (or ` ` where a native button would fight the swatch styling) with proper `aria-pressed` / `aria-expanded` / `aria-modal` semantics, keyboard handlers and visible focus rings.
- (Accessibility): the Page Structure navigator now uses a real tablist and each heading / landmark is a keyboard-operable button.
- (Accessibility): **Reset** now guarantees cleanup of every feature style tag and CSS filter — no more stale Big Cursor or greyscale surviving a reset if state was out of sync.
- **Color Saturation** now writes its inline `filter` with `!important`, so themes and page-builder hover effects (Divi module animations, Elementor overlays) can no longer override it.
- **Icon-font glyphs no longer render as literal `` text** on Divi / Elementor pages when server-side auto-fix is active. `ServerFix::serialise()` now decodes DOMDocument's numeric-entity output back to raw UTF-8, so `content: attr(data-icon)` in CSS renders the original glyph instead of the escaped source.
- widget compatibility with **SiteGround Speed Optimizer**, **WP Rocket**, **LiteSpeed Cache** and **Autoptimize**. When those plugins relocate the main bundle to their own asset cache, webpack now still fetches the widget's lazy chunks from the correct plugin URL — fixes the "widget button does nothing" 404 on optimized sites.
- **AI settings admin page** — Save / Validate / Reset / Set-active API-key requests now go through `wp.apiFetch`, so cached admin pages and hosts that strip cookies from `/wp-json/*` no longer produce "Cookie check failed" on live sites.
- **ServerFix.php** — `$_SERVER['HTTP_X_WP_NONCE']` unslashed + sanitised (Plugin Check compliance).
- the Divi Marketplace build shipped without the Auto-Fix engine file, so enabling or toggling auto-fixes from the One-Click Setup page failed with a "Could not toggle engine" error. The Auto-Fix engine now ships with the Divi build and works as expected.
- Smart Color Contrast no longer changes text over a background-image or gradient. Previously it couldn't read those backgrounds, assumed white, and could turn light text dark (invisible on dark sections). It now leaves elements it can't measure untouched.
Improved
- the compliance score now reflects the real audit ratio (passing checks vs issues), the same way professional scanners (Lighthouse, WAVE, axe) score — no more inflated "setup bonus", so the number you see matches third-party audits.
- heading-order fix now also repairs skipped levels (e.g. an H2 followed by an H4) via aria-level, not just a missing H1.
- **Smart Color Contrast** is now OFF by default. Because it recolours text inline, it could override intentional designs (e.g. white text on a dark section). Existing sites that had it on are switched off once automatically; you can re-enable it any time from One-Click Setup.
May 25, 20261.5 MBScanned
* AI-assisted fix flow: per-provider API key storage, masked read-only key inputs, validate/save/reset/active controls.
* Saved AI fixes are now per-page OR site-wide (tick "Apply on every page" for shared header/footer elements).
* Color-contrast fixes are style-only — the original element's content is never modified, only the inline `style` attribute.
* Post-fix contrast verification — if the AI's suggested color still fails WCAG AA, the fix is automatically reverted with a clear toast.
* Admin bar quick actions: "Scan this page" and "Clear AI fixes for this page".
* REST namespace migrated to `easeaccess/v1` (with `zn7/v1` kept as a back-compat alias for one major release).
* AI endpoints (`/ai/fix-issue`, `/ai/generate-alt`, `/ai/settings*`) hardened with `current_user_can('edit_posts')` + nonce.
* Auto cleanup of broken saved AI fixes from earlier versions.
Why archive
Sometimes the latest release isn't the one you need. The archive lets you pin EaseAccess to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.