Adaptation pillar · accessibility
Accessibility, in the same layer as your content
Accessibility is part of the adaptive content layer, not a separate audit you run at the end. The right content for every screen and every user: assistive-tech surfaces live next to your translations, your AI generates them, and you ship them to the CDN with everything else.
What you get
Accessibility surfaces in the key
Each key can carry its accessible surfaces alongside the visible text: aria-label, image alt text, screen-reader-only text and a plain-language variant, translated into every locale like any other string.
AI-generated, in your workflow
Your AI assistant drafts alt text, ARIA labels and plain-language rewrites from context, via the Sonenta MCP, right where you create and translate keys. No separate tool.
Accessibility coverage report
A report on the accessibility surfaces carried by your content: which keys have an aria-label, an alt text, screen-reader-only text or a plain-language variant, in which languages, and what is missing. It measures completeness and coverage, plus a real readability score per language (Flesch and LIX, computed locally, zero AI credits). It does not attest to any WCAG conformance level and produces no A, AA or AAA rating. Conformance depends on the rendered DOM, on interaction and on context that a content layer cannot observe. Use it to find the gaps in your accessible content, not as a conformance audit.
The sonenta-a11y agent
Install the sonenta-a11y agent (Sonenta MCP + @sonenta/cli) to scan your keys, propose accessible surfaces in bulk and keep them in sync as your content changes.
European Accessibility Act, what we provide
The European Accessibility Act applies since June 2025. Sonenta exports the state of your accessible content (HTML and JSON), language by language, which you can attach to the accessibility statement you are answerable for. It is not the statement itself, and it attests to no conformance: it is one document to file with the record you build.
Reviewed in the dashboard
Accessibility content is moderated like the rest: your team reviews and approves AI proposals in the dashboard before they go live.
Install the agent
Add the sonenta-a11y agent to your editor in one command, it writes .claude/agents/sonenta-a11y.md:
npx @sonenta/cli agents add sonenta-a11y
Prerequisite: the @sonenta/mcp server configured with a SONENTA_API_KEY (scope mcp:*). The agent runs local-first, it scans your keys and proposes accessible surfaces on your machine, so routine audits cost zero AI credits.
How it fits your pipeline
The same loop as the rest of your content, accessibility included.
1 · Adapt
Accessible surfaces (alt text, ARIA, plain-language) live in the key.
2 · Automate
Your AI generates them via the MCP and the sonenta-a11y agent.
3 · Evaluate
The coverage report flags gaps; your team moderates in the dashboard.
4 · Deliver
Published live to the CDN, no rebuild.
Accessibility is the Adaptation block of our five capabilities, Translation, Adaptation, Automation, Evaluation, Delivery.