Releases · Transparency
Version history
Each release note shows what has changed — no vague „improvements and bug fixes". Security fixes are highlighted, AI changes are listed separately.
Version scheme
How we assign versions
We follow Semantic Versioning according to the scheme MAJOR.MINOR.PATCH:
- PATCH (e.g. 1.5.26 → 1.5.27): Bug fix, security patch, language update. Ready to play immediately, no site customization required.
- MINOR (e.g. 1.5 → 1.6): New modules, new features, backward compatible extensions.
- MAJOR (e.g. 1.x → 2.0): Breaking changes in filter API or module structure. Very rare — and always with migration instructions.
Releases (newest at the top)
v1.5.26
- Frontend panel: Touch target size for slider set to 48 px (WCAG 2.5.5 strict).
- AI Alt Text: Bulk mode now includes pause/resume.
- Bugfix: In rare cases, ARIA-Manager set `aria-label` twice on buttons that already had labels.
v1.5.25
- New module: Touch Target Size (WCAG 2.5.5).
- AI Audit Assistant: History tracking introduced — now you can see the issue development over time.
- Performance: Frontend JS reduced by another 3 KB (now 25 KB gzip).
v1.5.24
- Improved TranslatePress integration: Language detection is now reliable even with language subdomain configuration.
- Compatibility: tested with Bricks Builder 1.10.
v1.5.23
- Security fix: Improved sanitization in admin settings (CVE risk: Low).
- AI ARIA Assistant: Cache layer for recurring components.
v1.5.22
- Reviews feature: Integration with Google Places API for aggregated reviews.
- Filter `sp_get_aggregate_rating()` for content packages.
v1.5.20 – 1.5.21
- Various minor bug fixes, language updates.
v1.5.0
- Major milestone: 4 AI modules introduced.
- Frontend panel completely redesigned (touch-first design).
- New module overview in the admin panel (filter, search, quick toggle).
v1.0.0
- First public version. 12 mechanical modules + front-end panel.
Older versions (Versions < 1.0) are not publicly documented. Available upon request.
Update Policy
What we promise
- Security fixes within 48 hours after it became known.
- WCAG updates within 30 days after official W3C publication.
- Compatibility update for new WP major versions within 14 days after WP release.
- The existing filter API remains. at least 12 months backwards compatible.
- Automatic update via WP-Cron or manually — whichever you prefer.
Stay up to date
If you use the plugin, you'll automatically receive new versions via WP-Updater. Optional: a short email with the diff of this page for each release.