This page explains how accessibility compliance relates to email content created with Mapp Engage and clarifies responsibilities between Mapp and clients. It is intended for orientation only and does not provide legal advice.
What accessibility compliance means
Accessibility compliance refers to meeting applicable legal and regulatory requirements that ensure digital content can be accessed and used by people with disabilities. These requirements may be defined by regional or national regulations, such as accessibility laws or standards based on the Web Content Accessibility Guidelines (WCAG).
Legal requirements vary by region, industry, and use case, and may change over time.
Accessibility requirements may apply differently to HTML email compared to web content.
Responsibility for compliance
Mapp does not certify or guarantee legal accessibility compliance.
Clients are responsible for ensuring that their email content, campaigns, and linked destinations meet applicable accessibility requirements. This includes decisions related to content, design, language, and usage.
Mapp provides tools, templates, and technical foundations that support accessible email creation. However, accessibility compliance can only be achieved when both the technical implementation and the actual email content are accessible.
How Mapp supports accessibility
Mapp Engage provides accessibility-supporting capabilities, such as:
HTML frameworks and content blocks designed to support accessible markup
Features that enable the use of alternative text, semantic structure, and readable layouts
Compatibility with common assistive technologies and modern email clients
These capabilities help reduce technical barriers but do not replace the need for accessible content decisions made by the client.
Content and implementation considerations
Even when using accessibility-ready templates or frameworks, compliance depends on how content is created and maintained. For example:
Text, images, links, and buttons must be used in an accessible way
Visual design choices can affect readability and usability
Linked content, such as landing pages or documents, may also need to meet accessibility requirements
For practical guidance on implementation, refer to the relevant How-to documentation.