Fix Custom Font Fallback Overrides in Samsung Email — Campaign Monitor Guide for WCAG Accessibility Violations
Accessibility failures prevent screen readers from navigating templates, isolating disabled subscribers and increasing unsubscribe rates. Below is the targeted integration guide to fix Custom Font Fallback Overrides inside Samsung Email templates when using Campaign Monitor.
Technical Breakdown
Samsung Email uses the WebKit which lacks support for standard rendering rules. This causes Custom Font Fallback Overrides elements to break or collapse when rendering templates.
Campaign Monitor Behaviors
Campaign Monitor wraps custom blocks in dynamic edit tags, which can break the column flow inside Outlook. Ensuring correct class names is essential. Inject correct table roles (role='presentation') and keep color pairings above the WCAG AA contrast threshold of 4.5:1.
Remediation Code Block
To prevent Outlook's Times New Roman fallback override, wrap your custom font declarations inside an @media block that Outlook ignores, or use MSO conditional statements to override font-families specifically for Microsoft Word rendering engines. In your Campaign Monitor campaign manager, make sure you configure your links to run via [unsubscribe].
<!--[if mso]>
<style type="text/css">
body, table, td { font-family: Arial, sans-serif !important; }
</style>
<![endif]-->
<style>
@import url('https://fonts.googleapis.com/css2?family=Montserrat&display=swap');
</style>Live Code Sandbox Test
How to Deploy inside Campaign Monitor
Copy the fixed VML or table wrapper code block from the remediation box above.
In Campaign Monitor, click the 'Source' button on your selected editable text region, or edit the template code files directly. Ensure you append the 'class="cs-editable"' flag if you need inline editing later.