Use case
Accessible content
The European Accessibility Act has applied since June 2025, and the part of accessibility that lives in content can be handled where the content already lives.
The problem
- Alt text and ARIA labels get written at the end of a project, once the context has been forgotten.
- They are written in one language, then translated without review.
- Nobody knows what share of the content actually has them.
What Sonenta changes
- Four accessibility surfaces live next to the key:
aria_label,alt_text,screen_reader,plain_language. - The agent generates them from the visible text and its context, in every one of your languages, during development.
- A readability score is computed locally, with no server call.
- The
wcag_reportMCP tool measures the content layer criterion by criterion, and the coverage report can be exported.
Where to start
// les surfaces vivent à côté de la clé
t("checkout.pay") // « Payer »
t("checkout.pay", { surface: "aria_label" })
t("checkout.pay", { surface: "plain_language" })
// depuis l'agent, via MCP
generate_a11y_variant key=checkout.pay surface=aria_label
wcag_report // mesure de la couche de contenuKnown limits, and they matter
- Sonenta issues neither a certification nor a conformance report. What you get is a coverage report for accessible content, not a verdict on your application.
- The DOM, the keyboard and focus are not observed. An application's accessibility is not reducible to its content, and the rest is yours.
- The EAA accessibility statement is a document you publish. Sonenta helps gather the material, it does not attest to it.
Down to the last word.
Ready to adapt your product to every user?
Start free in minutes. No credit card, no commitment, and your exports always open.