Accessibility & Localization

The Mine CMP banner is designed to be usable by every visitor, regardless of how they interact with the web or which language they speak. This article covers the accessibility standards the banner meets and how localized banner content is selected and displayed.

Accessibility

The CMP UI complies with WCAG 2.1 Level AA, the standard most privacy and accessibility regulations require for public-facing web interfaces.

This compliance is built into the banner — there's no configuration step required to enable it.

Keyboard navigation

The banner is fully operable from the keyboard:

• Tab moves focus between buttons, toggles, and links
• Enter activates the focused button or toggle
• Escape closes the banner

For modal banners, focus is trapped inside the banner while it's open — Tab cycles within the modal rather than escaping to the rest of the page. When the banner closes, focus returns to the element that opened it.

Screen reader support

The banner uses semantic HTML and ARIA labels to communicate its purpose and state to screen readers. Both layers are marked as dialogs, category and provider expand/collapse buttons announce their expanded state, and all interactive elements have accessible names.

Visual accessibility

• Color contrast meets WCAG AA thresholds across all banner elements
• Focus indicators are visible for every interactive element
• Text remains readable at standard zoom levels

If you customize the banner's colors via the branding page or custom CSS, make sure your color choices preserve sufficient contrast — the CMP's defaults are AA-compliant, but custom themes are the customer's responsibility.

Localization

The banner is displayed in your visitor's language automatically. You configure the localized content for each language you want to support in the MineOS portal, and the CMP picks the right one at runtime based on the visitor's browser settings.

How the language is selected

The CMP picks a language using this fallback order:

1. Browser language, if it is available in your banner's configured content
2. English (en), if the browser language is not available
3. First available language in the configuration, if neither of the above matches

This means English is the safe default — as long as you have English content configured, every visitor will see a readable banner even if their browser language isn't one you've localized for.

Configuring localized content

Localized content is configured per banner in the MineOS portal. For each banner, you provide translations for every text element — title, body, button labels, category descriptions, and so on — keyed by language code (e.g., en, de, fr, es).

You only need to configure the languages you actually want to support. Anything not configured falls through to English or your first available language via the fallback chain above.

Testing different languages

To preview your banner in a specific language without changing your browser settings, append the cmp-mock-lang URL parameter to any page on your site:

https://example.com?cmp-mock-lang=de

This overrides the browser language for localization only and is useful for verifying translations end-to-end. See the Testing, Debugging & Troubleshooting article for the full set of mock parameters.