Clara Accessibility Audit & AI Alt Text

Clara helps you find the accessibility problems in your own site and fix the
most common one — images with no alt text.

Find the problems: accessibility audits

Choose any public page of your site and audit it for the issues a visitor
using assistive technology would run into: errors, contrast failures, heading
and structure problems, and ARIA issues, each listed with the element it was
found on. Every report is saved, so you can work through it, come back to it,
compare it with the next audit, and download it as a PDF to hand to whoever
builds your site.

Fix your images: AI alt text

The AI Image Alt Text screen lists the images in your Media Library and shows
which ones have no alt text. Pick the ones you want, or all of them, and Clara
writes a short description for each. Descriptions are saved where WordPress
keeps alt text — so they stay if you ever remove the plugin — and every change
is recorded. You can review and edit each one, and regenerate any you are not
happy with.

What it does not do

Clara adds nothing to your site’s public pages. There is no visitor-facing
widget, no script on your front end and no automatic rewriting of your pages.
It works on your content, from your dashboard, when you ask it to.

Everything is free right now

There is no paid tier, no trial and nothing to buy. Audits and AI alt text use
AI credits, and every install currently has unlimited credits. If paid plans
are introduced later this page will say so before anything changes.

Accessibility is a process

No plugin can make a site compliant with WCAG, the ADA or the European
Accessibility Act, and this one does not claim to. An audit finds problems;
fixing them is work you or your developer do in your own pages. Clara makes
that work faster to start and easier to track.

External services

Clara uses services run by Accessify (accessify.app), the plugin’s author.
Nothing is sent anywhere when you activate the plugin or open its screens.
What is sent, when, and why:

1. AI alt text — api.accessify.app

Used only when you press “Generate with AI” on the AI Image Alt Text screen,
for the images you chose. For each image, one of WordPress’s own smaller
copies is sent — never the original upload — together with the instruction to
describe it. Your site’s address, the plugin’s site ID and version, and your
licence key if you have entered one, travel in the request headers so the work
can be metered against your account.

2. Accessibility audits — audit.accessify.app

Used only when you run an audit. The address of the page you chose is sent;
the service fetches that page as a visitor would and returns the report, which
is stored on your site. Only public pages of your own site can be audited.

3. Licensing — api.accessify.app

Used only if you enter a licence key. Your key and your site’s address are sent
so the plan can be checked, and re-checked about once a day. If the service
cannot be reached, your plan keeps working for a fortnight rather than being
switched off.

4. Support chat — Crisp (client.crisp.chat)

Accessify’s support chat, provided by Crisp (crisp.chat). Nothing is loaded
from Crisp until you press a “Contact us” button — opening the plugin’s
screens contacts nobody. When you do press it, Crisp receives what a support
chat needs to answer you: your site’s name and address, the administration
email WordPress has on file, and which plan you are on, together with the
details any browser sends (IP address, user agent). It is used on this
plugin’s admin screens only, and never for a user who cannot manage options.

To remove it, add this to wp-config.php:

define( 'CLARA_AUDIT_DISABLE_SUPPORT_CHAT', true );

or filter it in a theme or plugin:

add_filter( 'clara_audit_support_chat', '__return_false' );

With it off, nothing is loaded from Crisp and the “Contact us” links open a
pre-filled email instead.

Crisp terms: https://crisp.chat/en/terms/ — Crisp privacy: https://crisp.chat/en/privacy/

Accessify terms: https://accessify.app/terms — Accessify privacy: https://accessify.app/privacy

Post content, visitor data and WordPress user accounts are never sent to any
of these services.

Data stored on your site

Two tables in your own database: saved audit reports, and the record of alt
text Clara has written. The most recent 200 audit reports are kept and older
ones are removed by a daily maintenance job; to keep a different number:

add_filter( 'clara_audit_reports_kept', function () { return 500; } );

Return 0 to keep every report.

Alt text itself is stored where WordPress stores it, in each image’s own alt
field, so it stays whatever you do with the plugin.

Deleting the plugin keeps your settings and reports unless you tick the
option to delete them on the Plans & Licence screen first. Deleting and
reinstalling is a common way to fix a broken update and should not cost you
your history. On a multisite network, deleting a site also deletes this
plugin’s tables for that site.

Sites that deploy from source can set the licence key in wp-config.php
instead of typing it into the admin:

define( 'CLARA_AUDIT_LICENSE_KEY', 'your-key' );

The service addresses can be overridden the same way, with
CLARA_AUDIT_CLOUD_API and CLARA_AUDIT_AUDIT_API — for example to point a
staging site at a staging environment.

Source code

The admin screens are a React application. What WordPress loads is the built
bundle in assets/build/, which is minified.

The source it is built from ships inside this plugin, under admin-app/,
along with the build configuration and a lockfile pinning every dependency:

• admin-app/src/ — the application
• admin-app/package.json and package-lock.json — the exact dependency tree
• admin-app/vite.config.js and vite.pdf.config.js — the build

To rebuild the bundles from that source, with Node 18 or newer:

cd admin-app && npm ci && npm run build

All bundled libraries are GPL-compatible: React, Shopify Polaris, i18next,
jsPDF and Tailwind are MIT.

The PHP is not built and needs no toolchain — it is exactly what runs.