1. Our commitment
We want every marketing team to be able to use Triggerize regardless of ability. Accessibility is treated as part of how we build the product, not a one-off project — new interface work is expected to meet the standards below, and accessibility rules run automatically on every build.
2. Conformance target
Triggerize aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We are currently partially conformant: most of the platform meets Level AA, and we are actively closing the remaining gaps (see Known limitations below). “Partially conformant” means some content does not yet fully meet the standard.
3. Measures we take
- Semantic structure & landmarks — pages use meaningful HTML and a
<main>landmark so assistive technology can navigate the layout. - Skip to content— a keyboard-reachable “Skip to main content” link lets users bypass the navigation (WCAG 2.4.1).
- Keyboard operability — interactive controls are reachable and operable with the keyboard, and activate on both Enter and Space (WCAG 2.1.1).
- Visible focus — a consistent focus indicator is shown for keyboard users on links, buttons, form fields, and custom controls (WCAG 2.4.7).
- Labelled forms — form fields are programmatically associated with their labels so screen readers announce them correctly (WCAG 1.3.1, 4.1.2).
- Reduced motion — when your device requests reduced motion, animations and transitions are minimised across the app (WCAG 2.3.3).
- Light & dark themes — both themes are designed for legible text contrast.
- Automated checks — accessibility linting (
eslint-plugin-jsx-a11y) runs on every build to catch common regressions before they ship.
4. Known limitations
We are honest about where we fall short. We are working to resolve the following:
- Some data-dense, interactive screens (for example the content calendar and the Kanban pipeline) have complex drag-and-drop and grid interactions that may not yet be fully operable with a keyboard or optimally announced by a screen reader.
- Colour-contrast ratios have not yet been independently audited across every state and component.
- Triggerize has not yet undergone a formal third-party accessibility audit or screen-reader certification. Our current assessment is a self-evaluation supported by automated tooling.
5. Assessment approach
This statement is based on a self-assessment of the platform combined with automated static analysis of the interface code. A formal, independent audit (including manual screen-reader testing and a full colour-contrast review) is planned; this statement will be updated with its outcome.
6. Compatibility
Triggerize is designed to work with current versions of major browsers (Chrome, Edge, Firefox, and Safari) together with their built-in or commonly paired screen readers. It may not work reliably with browser versions more than two major releases old.
7. Feedback & contact
If you encounter an accessibility barrier, or need information from Triggerize in a different format, please tell us — your feedback directly shapes our priorities. Email accessibility@triggerize.io and describe the page and the problem. We aim to respond within five working days.
8. Enforcement
If you are in the EU and are not satisfied with our response, you may be entitled to raise the matter with the relevant national accessibility supervisory body under your local implementation of the European Accessibility Act.
9. Changes
We update this statement as the platform improves and as audits complete. The “last updated” date above always reflects the current version.