Accessibility statement.
Last updated
A feed nobody can read isn't social proof. We build Vitraz — and the embeds it generates — to be usable with a keyboard, a screen reader, and at any zoom level.
The standard we build to
We target WCAG 2.2 Level AA. That covers the marketing site, the application, and the feed markup rendered into your visitors’ pages.
What that means in practice
- Every interactive control is reachable and operable by keyboard, with a visible focus ring that meets contrast requirements.
- Text meets 4.5:1 contrast against its background; large text and UI boundaries meet 3:1.
- Post images carry alternative text derived from the post, and purely decorative elements are hidden from assistive technology.
- Dialogs trap and restore focus, and announce themselves; validation errors are linked to their fields.
- Motion — carousels, transitions, celebratory effects — is reduced or removed when you set prefers-reduced-motion in your operating system.
- Layouts reflow to 320px and tolerate 200% zoom without loss of content.
What your embed inherits
Feeds render semantic markup with real headings, lists and links, so they announce sensibly inside your page. Two things stay in your control: the colours you pick in the feed editor, and the surrounding page. If you choose a custom accent with low contrast against your chosen background, the embed will inherit that — the editor warns you when a combination falls below AA.
Known gaps
We would rather name these than imply full conformance:
- Some analytics charts convey trends visually; the underlying figures are available as text beside them, but the charts themselves are not yet fully described.
- Content pulled from third-party networks arrives with whatever alternative text its author supplied. Where none exists we fall back to the post caption, which is imperfect.
- The feed editor’s drag-to-reorder has a keyboard alternative, but its announcements are terser than we would like.
Tell us about a barrier
If something blocks you, email accessibility@vitraz.io with the page and what happened. We aim to acknowledge within two working days and will tell you our plan and timeline for a fix. If you need information from the product in another format while we resolve it, ask and we will provide it.