Creaiter

What we have done, and what we have not.

This page does not claim WCAG conformance, because no audit has been done. Claiming it would be worse than saying nothing: someone who relies on that claim and then cannot use the product has been misled rather than merely disappointed.

In place today

Touch targets are at least 44px on phones

Every button, link and menu row has a 44 pixel minimum hit area on a small screen, and returns to its normal density on desktop. This is a project-wide standard with an automated test behind it, not a one-off pass.

Motion respects your system setting

If your device is set to reduce motion, entrance animations do not play and the 3D background is replaced with a flat one. That also skips loading the graphics context entirely rather than hiding it after the fact.

Real HTML underneath

Headings are headings, lists are lists, buttons are buttons and links are links. Navigation is standard markup, so browser and assistive-technology features that depend on structure have something to work with.

Content pages work without JavaScript

Every guide, glossary entry, template and documentation page is delivered as complete HTML. If scripts fail or are blocked, the words are still there.

Known gaps

These are the things we have not done. They are listed so you can judge whether the product is usable for you before you spend time on it.

  • No formal accessibility audit has been carried out, by us or by anyone else. There is no VPAT and no conformance statement, because neither would be honest yet.
  • Colour contrast has not been measured across the site. This is a dark interface with several levels of lower-opacity text, and some of it may not meet the usual contrast thresholds.
  • Screen reader testing has been limited. We have not run a systematic pass with NVDA, JAWS or VoiceOver across the application.
  • Keyboard navigation has not been fully audited, particularly inside the more complex parts of the app such as the chat and the campaign builder.
  • The interactive free tools have had no dedicated accessibility review beyond the standards above.

If something blocks you

Email support@creaiter-in.me and tell us what you were trying to do, what stopped you, and which assistive technology you use if any. An accessibility barrier is treated as a bug, not a feature request, and we are small enough that it will reach the person who can fix it.

If you need something on this site in another format in the meantime, ask and we will send it.