Make your app accessible

Two agents work together: sonenta-surface (decides which surfaces exist) and sonenta-a11y (fills + applies the values). Install: sonenta agents add sonenta-surface and sonenta agents add sonenta-a11y.

Configure surfaces

Prompt:

Using sonenta-surface, audit my surface configuration and recommend which a11y surfaces to enable.

Produces: a recommendation of which surfaces to enable - a11y (aria_label, alt_text, screen_reader, plain_language) and device (desktop/mobile/tablet + custom). Review: proposed config shown before changes; active surfaces appear in the dashboard. Apply: on acceptance it enables/renames the surfaces (config only, 0 credits). It then hands value-filling to sonenta-a11y.

Audit accessibility

Prompt:

Using sonenta-a11y, audit my app's accessibility and show me the remediation plan.

Produces: a code-aware WCAG 2.2 audit + a remediation plan, plus local readability/cognitive scores. Nothing is written yet. Review: the plan, the per-gap fixes, and the before coverage rate. Apply: nothing until you accept.

Generate + review a11y values

Prompt:

Generate the aria-labels, alt text, and plain-language rewrites from the plan, then submit them for my review.

Produces: draft a11y surface values (0 credits; server-side AI is an opt-in fallback). Review: the variants + cognitive scores appear in the dashboard review queue - approve or edit. Rejected items are regenerated from your reject reason. Apply: approving publishes the surfaces.

Wire the surfaces into your code

Approved aria_label / alt_text / screen_reader surfaces only render once your components read them (via @sonenta/react-i18next).

Prompt:

Wire my published a11y surfaces into the code.

Produces: the one-time code bindings (aria-label={t.aria(key)}, alt={t.alt(key)}, screen-reader nodes) added to the components that render those keys, idempotently. Review: a normal code diff. Apply: on acceptance. After this, future approved changes flow live via the CDN with no further wiring. (Plain language needs no wiring - it auto-applies via the FALC toggle.)

Produce a conformance statement

Prompt:

Produce a WCAG 2.2 conformance statement and an EAA / EN 301 549 statement.

Produces: formal conformance + accessibility statements you can publish.