What we support, and what we have not solved yet.
This statement is maintained by Genetrix for MCT. It describes current behaviour honestly, including the parts we are still working on. It is not an independent audit or certification.
WCAG 2.1 Level AA is the working standard.
We design and test the MCT block against WCAG 2.1 AA. Where a criterion is not fully met, it is listed under known gaps rather than quietly omitted.
Every control in the MCT block can be reached and operated with a keyboard alone, in a logical tab order, with a visible focus ring.
Headings, lists, labels and buttons use native elements so screen readers announce roles and states correctly.
Language pickers, folder selectors and naming inputs have persistent visible labels and programmatic associations.
Text and interface elements are designed to meet at least a 4.5 to 1 contrast ratio, and colour is never the only signal for state.
Translation progress, success and failure are announced through live regions rather than colour changes alone.
The block interface reflows at 200 percent zoom without loss of content or horizontal scrolling at typical widths.
Where we fall short today.
Listed so a procurement review does not have to discover them in a demo.
The source and translation comparison view is dense. At narrow widths it stacks, but it remains a heavy reading experience for magnification users.
MCT renders inside Content Builder. Some framing, iframe focus behaviour and dialog handling belong to Salesforce and are outside our control.
MCT preserves the accessibility of the email you give it. It does not add alt text, language attributes or heading structure that the source template is missing.
Manual first, tooling second.
Every release goes through keyboard only navigation of the full translate flow, a screen reader pass on the block interface, and an automated contrast and semantics check. Findings that block a task are fixed before release. Findings that degrade an experience are logged and appear on this page until resolved.
A formal VPAT or ACR can be produced for an enterprise procurement process. Request one at support@genetrix.tech and tell us which template you need it in.
Tell us what blocked you.
Accessibility reports are treated as functional defects, not feedback.
Email accessibility@genetrix.tech with the page or block screen, the assistive technology and browser you were using, and what you were trying to do. We acknowledge within two business days and give you a fix or a workaround plus a target date. If the barrier stops you completing a send, raise it as a P1 through support and reference this page.
Need an accessibility review before you buy?
We will walk the MCT block with your accessibility team and answer criterion by criterion.
