Skip to content
AdVellum

Last updated September 1, 2026

Accessibility

The short version

  • We target WCAG 2.1 Level AA across the site and the app.
  • Keyboard, screen-reader semantics, visible focus, reduced motion and AA colour contrast are built into the design system, not bolted on.
  • Some areas are still being verified — they are listed below, not hidden.
  • If something blocks you, email us and a human will fix it or find you a path around it.

1. The standard we work to

AdVellum aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA for the marketing site and the application. This statement describes where we are honestly: we consider the product partially conformant — most of the experience meets the standard, and the exceptions we know about are listed in section 3.

2. What is in place

  • Keyboard: every interactive element is reachable and operable by keyboard, with a visible focus indicator throughout and a skip-to-content link on every page. There are no keyboard traps.
  • Screen readers: semantic HTML with ARIA where it adds meaning — labelled icon buttons, live status regions for asynchronous work, table captions, and form fields programmatically linked to their labels and error messages.
  • Colour and contrast: the colour system is token-based and checked against AA ratios in both light and dark themes, including secondary text and status colours. Colour is never the only carrier of meaning — status is always paired with text.
  • Motion: all animation respects your prefers-reduced-motion setting, including decorative counters and transitions.
  • Resizing: text is set in relative units; the layout works with browser zoom and text scaling to 200%.
  • Generated images: every image creative the product generates carries descriptive alternative text derived from its concept and headline.

3. Known limitations

  • The results workspace (tabs within tabs, card grids) is functional with a screen reader but its reading order is still being refined; we are reviewing it against real screen-reader sessions.
  • Alternative text for generated images is machine-written. It is descriptive, but it may occasionally describe the intended concept rather than the exact rendered pixels.
  • Exported PDFs (video scripts) are visually formatted documents and are not yet tagged for assistive technology; the same content is available as plain text in the app.
  • Third-party surfaces we link into — checkout and the billing portal (Stripe) — are governed by their own accessibility programmes.

4. Feedback and enforcement

If any part of AdVellum is hard or impossible for you to use, tell us: contact@acctan.com. Describe what you were trying to do and the assistive technology involved, and we will respond within 3 business days — with a fix where we can, and a workaround in the meantime where we cannot.

This statement is reviewed whenever the design system changes materially, and at least yearly.