{"id":22113,"date":"2025-08-11T09:33:31","date_gmt":"2025-08-11T09:33:31","guid":{"rendered":"https:\/\/mautic.org\/blog\/"},"modified":"2025-08-16T00:30:43","modified_gmt":"2025-08-16T00:30:43","slug":"eaa-compliance-for-mautic-users","status":"publish","type":"post","link":"https:\/\/mautic.org\/blog\/eaa-compliance-for-mautic-users","title":{"rendered":"How to achieve EAA compliance for Mautic users"},"content":{"rendered":"\n

As marketers and developers, we’re used to adapting to evolving regulations, from GDPR to privacy-first analytics. Now, it\u2019s time to prepare for another major shift: the European Accessibility Act (EAA), taking effect in June 2025.<\/p>\n\n\n\n

While accessibility has long been a best practice, the EAA will soon make it a legal requirement for many organisations, including those who send emails within or into the European Union. If you’re using Mautic to manage email communications, here\u2019s what you need to know.<\/p>\n\n\n\n

Importance of EAA and why it matters<\/h2>\n\n\n\n

The EAA is a directive designed to ensure digital products and services are accessible to people with disabilities. It applies to a wide range of services, including websites, mobile apps, e-commerce platforms\u2026 and yes, emails. If your organisation operates within the EU, or targets EU citizens, this law could affect you. Failure to comply may result in legal penalties, loss of trust, or being excluded from public sector partnerships. This is serious stuff.<\/p>\n\n\n\n

While the EAA primarily targets larger companies and public sector organisations, small businesses shouldn’t ignore these requirements. Microenterprises, defined as having fewer than 10 employees and an annual turnover below \u20ac2M, may be temporarily exempt from certain obligations, but this could change as the regulation evolves, and EU is will known for that.<\/p>\n\n\n\n

Being proactive now not only prevents costly future adjustments but also signals a genuine commitment to accessibility and user inclusion from the outset.<\/p>\n\n\n\n

How does it affect Mautic users?<\/h2>\n\n\n\n

Here are some common areas where Mautic users may fall short:<\/p>\n\n\n\n

\ud83d\uddbc\ufe0f Missing alt text for images<\/h3>\n\n\n\n

Images without descriptive alt attributes can create major barriers for users relying on screen readers. If your email includes buttons, banners, or visual CTAs rendered as images, those users won\u2019t understand their purpose unless meaningful alt text is provided. Mautic users should ensure all image elements include concise, descriptive alternatives.<\/p>\n\n\n\n

\"GrapeJS<\/figure>\n\n\n\n

\ud83c\udfa8 Poor colour contrast<\/h3>\n\n\n\n

Text placed over backgrounds, buttons with low contrast, or pastel colour schemes may look elegant, but can be unreadable for users with visual impairments or colour blindness. The EAA requires a minimum contrast ratio of 4.5:1 for normal text, which means design choices need to balance style with readability.<\/p>\n\n\n\n

\"Section<\/figure>\n\n\n\n

\ud83d\udca1 Good structure = better experience<\/h3>\n\n\n\n

Just like a well-organised blog post or a clear landing page, your email also needs a logical structure, not just for the eye, but for assistive technologies like screen readers.<\/p>\n\n\n\n

If your email content isn\u2019t structured clearly in the code (even if it looks fine visually), some users might not be able to read or navigate it properly. For example, screen reader users rely on headings, lists, and content order to understand what\u2019s on the page, and where to go next.<\/p>\n\n\n\n

\"Newsletter<\/figure>\n\n\n\n

\ud83d\udd17 Unclear or inconsistent navigation<\/h3>\n\n\n\n

If you’re using Mautic to create onboarding sequences or multi-step forms, navigation must be intuitive and predictable. Users should always understand where a link leads and what the next action is. Keyboard accessibility and screen reader compatibility are especially important here.<\/p>\n\n\n\n

\"Newsletter<\/figure>\n\n\n\n

\ud83d\udcce Non-descriptive links (e.g. \u201cclick here\u201d)<\/h3>\n\n\n\n

Generic phrases like \u201cclick here\u201d provide no context for screen reader users. Instead, links should describe the destination or action clearly, for example, \u201cDownload the accessibility guide\u201d or \u201cView your subscription settings\u201d. This improves both accessibility and usability.<\/p>\n\n\n\n

\"Comparison<\/figure>\n\n\n\n

\ud83e\udded Inconsistent design can create confusion<\/h3>\n\n\n\n

When users interact with your emails, they rely on familiar patterns to understand what\u2019s clickable and what action to take next. If your buttons, links, or call-to-actions (CTAs) change appearance from one email to the next, or even within the same email, it can make the experience harder to follow.<\/p>\n\n\n\n

Using different colours, shapes, or placements for similar actions forces users to relearn the interface each time, which increases cognitive load and may lead to missed opportunities.<\/p>\n\n\n\n

\"Side-by-side<\/figure>\n\n\n\n

\ud83d\udcf1 Lack of responsive design<\/h3>\n\n\n\n

Accessibility isn\u2019t just about screen readers or colour contrast, it\u2019s also about making sure your email is easy to read and interact with, no matter the device.<\/p>\n\n\n\n

If your email or landing page layout breaks on small screens, uses tiny text, or forces users to pinch and zoom, that\u2019s a barrier. Many people with disabilities rely on mobile devices, and poorly optimised designs make your content harder to access.<\/p>\n\n\n\n

\"Welcome<\/figure>\n\n\n\n

Practical steps you can take<\/h2>\n\n\n\n

You don\u2019t need to stress, here\u2019s what you can start doing now and from now on:<\/p>\n\n\n\n