Accessibility

Meles puts surveys and announcements inside other people's products, so a widget that someone can't use makes our customers' products harder to use too. Here is what we aim for, what we've checked, and where we still fall short.

What we aim for

The widget your users see and the dashboard you build campaigns in are designed to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. We also check them against WCAG 2.2's newer criteria, and fix what we find there when we can.

How we check

• Automated checks run on every change: on every dashboard screen in light and dark themes, on every piece of the design system, on every page of this site, and on the widget in Chrome's engine. After a change to the widget, a nightly run checks it in Firefox's and Safari's engines too.
• Automated checks find only part of what matters, so on 5 October 2026 we audited the rest ourselves: every key journey by keyboard alone, what a screen reader is given, zoom to 400%, wider text spacing, Windows' high contrast mode and reduced motion.
• Before the private beta, and again before we launch, we'll test the key journeys with a screen reader too.

The audit was our own, not a third party's, and we don't publish a formal conformance report. If you need one, ask us.

Where we fall short

These are the gaps our audit found that aren't fixed yet. We're fixing them before the private beta.

• A banner shown over the top of a page can cover that page's own links as they take keyboard focus. Showing the banner in a reserved space at the top of the page avoids this.

Your survey's own content is yours: the theme editor warns you when your colours don't have enough contrast, but your wording and colours are your choice.

Tell us about a problem

If something in Meles doesn't work for you, or for your users, email support@meles.app. Tell us which page or campaign it was, what you were trying to do, and what you use to browse (a screen reader, magnification, a keyboard). Please don't send your users' personal data.