← Sovatela

Accessibility statement

Applies to: Sovatela v1.2.0 · Last reviewed: 2026-08-05

Our position

We want Sovatela to be usable by everyone. It currently is not fully accessible, and this statement says where it falls short rather than claiming otherwise. The gaps below are real, were found by review of the source, and are tracked as work — not as acceptable.

Conformance status: partially conformant with WCAG 2.1 level AA. "Partially conformant" means some parts do not fully conform. We have not commissioned an independent audit; treat this as a self-assessment.

What works today

Known gaps

We consider these defects. They are listed with the standard they engage.

Gap Impact WCAG
Text scales to 150%, not 200%, and spacing does not scale with it. The type ramp is now in rem and the app provides its own size control, but the criterion asks for 200%, and padding is still fixed so larger settings tighten the layout rather than growing it. Readers who need more than 150% are not served. 1.4.4 Resize Text (AA)
Sparse ARIA coverage — around 30 attributes across the whole interface. Panels, lists, and the history sidebar lack landmark roles and structural labelling. Screen-reader users get a flat, hard-to-navigate structure. 1.3.1, 4.1.2
No keyboard shortcuts beyond Enter and Esc — no way to start a new chat, focus the composer, open settings, or move between panels without a pointer. Keyboard-only users must tab through everything. 2.1.1
Focus management on panel open/close is not explicitly handled — focus may not move into a dialog or return to the trigger. Disorientation for screen-reader and keyboard users. 2.4.3
Colour contrast has not been formally measured against either theme. Unknown; likely acceptable for body text, uncertain for muted secondary text. 1.4.3
No screen-reader testing has been performed with VoiceOver, NVDA, JAWS, or Orca. Real behaviour is unverified.
Streaming output announcement is untuned — a live region emitting a token stream can be overwhelming. Verbose, possibly unusable announcement during replies. 4.1.3

What we intend to do

In rough priority order:

  1. Add a keyboard shortcut set with an in-app reference, plus focus management on panel transitions.
  2. Add landmark roles and structural labelling; retune the live region to announce completion rather than every token.
  3. Carry text scaling to 200%, and decide whether spacing should scale with it. The remaining obstacle is that most padding is written in fixed pixels rather than relative units.
  4. Measure contrast in both themes and correct failures.
  5. Test with at least one screen reader per platform.

Done in 1.2.0: the type scale moved from px to rem with a text-size control to drive it, the 10px minimum was raised to 11px, and prefers-reduced-motion is now honoured throughout — including in scripted scrolling, which CSS alone cannot reach.

No date is promised, because this is a small project and a promised date would be a guess.

Compatibility

Sovatela is a desktop application rendering in a system webview (WebKit on macOS and Linux, WebView2 on Windows). Platform screen readers and system-level zoom generally apply, but per the gaps above, in-app text scaling does not respond to text-size settings.

Feedback

If you hit an accessibility barrier, tell us — it will be treated as a bug, not a request:

info@anaubi.com

Please include your assistive technology and version, your OS, and what you were trying to do. We aim to respond within 5 working days.

If you're not satisfied with our response, say so plainly and tell us again — we would rather hear it twice than have you give up. Sovatela is published by one person, so there is no second-line process to escalate to internally.

Legal note

The European Accessibility Act applies to certain consumer software from 28 June 2025. Whether it reaches this product is genuinely unsettled: Sovatela is published by an individual, free of charge, with no commercial activity — see the legal and compliance checklist.

We have deliberately not named a national enforcement body to escalate to, because we are not confident which Danish authority would be the right one for a product of this kind, and sending someone to the wrong regulator wastes their time rather than helping. If applicability is confirmed, the correct body will be named here.

None of that changes the substance: this statement is written to be useful, and the defects listed above are treated as defects, regardless of whether anyone is legally required to fix them.