Accessibility Statement

Our commitment to accessibility

Mercemur believes that an online business should be accessible to anyone who wants to run one and anyone who wants to shop from one. We treat accessibility as a core product concern, not a compliance afterthought. That means we design, build, and test for people using keyboards, screen readers, voice dictation, screen magnifiers, and other assistive technologies alongside people using a standard mouse and monitor.

Conformance target

We target Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across the Mercemur marketing site, merchant admin dashboard, and default storefront themes. WCAG 2.1 AA is the global benchmark used by the EU Web Accessibility Directive, the US ADA/Section 508, and the UK’s Equality Act. Where we haven’t met the target yet, we say so under Known limitations below.

How we build and test

Accessibility work happens at three layers:

• Design, color contrast, focus visibility, reduced-motion support, and keyboard affordances are part of every component spec before any code is written.
• Build, we use semantic HTML elements (<nav>, <main>, <button>, <address>, and so on) rather than ARIA overrides. ARIA is used only where native semantics fall short.
• Test, automated checks (axe-core) run in CI for every pull request, and we supplement with manual keyboard-only sweeps and NVDA / VoiceOver screen-reader sessions on high-traffic flows (signup, checkout, admin).

Accessibility features

• Full keyboard navigation, including visible focus rings on every interactive element
• Semantic landmarks (<header>, <nav>, <main>, <footer>) for screen-reader navigation
• Skip-to-content links at the top of every page
• Color contrast that meets or exceeds WCAG 2.1 AA minimums (4.5:1 for body text, 3:1 for large text and non-text components)
• Text can be resized up to 200% without loss of content or functionality
• prefers-reduced-motion respected for animations and transitions
• Form fields with associated labels, inline error messages, and meaningful validation
• Descriptive link text (“View pricing” instead of “click here”)

Merchant-controlled storefronts

Mercemur powers tens of thousands of storefronts operated by independent merchants. Default storefront themes ship with WCAG 2.1 AA conformance, but merchants can customize themes, add their own images, alt text, and third-party apps, all of which can affect the final accessibility of any specific store. Each merchant is responsible for the accessibility of their own storefront, and we encourage merchants to follow our theme-level accessibility guidance. If you encounter an accessibility barrier on a specific merchant’s store, please contact the merchant directly; we can help escalate if needed.

Known limitations

We’re transparent about gaps we’re still working on:

• Some legacy admin surfaces predate the current component library and have not been re-audited. We’re porting them to the shared components quarter by quarter.
• Embedded third-party widgets (payment iframes, chat, video) are governed by the accessibility of those providers.
• User-generated product content (names, descriptions, images) depends on each merchant’s input quality; missing alt text on a product image is outside our direct control.
• Complex data tables in the admin dashboard are gradually being migrated to accessible equivalents with sortable headers, row captions, and keyboard shortcuts.

Alternative formats

If you need any content from this site in an alternative format, large print, plain text, a different language, or an accessible PDF, email us at support@mercemur.com and we’ll do our best to help.

Report an accessibility issue

If something on Mercemur isn’t working for you, please tell us. We take every report seriously and respond within two business days.

Updates to this statement

We review this accessibility statement when we ship major product changes. For the underlying standards, see the W3C WCAG overview.