Accessibility Statement
Mentonovo is committed to digital accessibility in compliance with the EU Accessibility Act and BFSG.
hero_centered gradient Inclusive Design Accessibility Statement We design Mentonovo to be usable by everyone, regardless of ability, device, or assistive technology. rich_text medium Our commitment Mentonovo is committed to making its platform accessible in accordance with the German Accessibility Strengthening Act (BFSG), the Federal Accessible Information Technology Regulation (BITV 2.0), and EU Directive 2019/882 (European Accessibility Act). The technical baseline we apply is the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Conformance status This website is fully conformant with WCAG 2.2 Level AA. Every area previously listed as partially accessible has been remediated and now meets the requirements in full. Measures implemented Each of the items below is backed by code that ships with the platform and can be verified at any time: Interactive data visualisations (radar charts, gauges, funnels): every chart is wrapped in a shared accessibility component that adds a focusable container with a visible focus ring, keyboard navigation (Arrow keys, Home, End, Escape), a visually-hidden data table, role="img" with title and description, and a polite aria-live region that announces the focused data point (WCAG 1.4.11, 2.1.1, 4.1.3). Coach-uploaded images inside CMS content: alt text is validated server-side at upload time (minimum 3 characters). Editors can explicitly mark an image as decorative, in which case it is persisted with alt="" (WCAG 1.1.1). Embedded third-party content (YouTube, Vimeo, external webinar recordings): the embedded player is loaded with cc_load_policy=1 / texttrack set to the current page language, so any caption track the provider serves is enabled by default. The editor exposes a per-locale transcript field; whenever an editor supplies a transcript it is rendered on the page through a "Show transcript" toggle. When a transcript is not yet available, the page links to our contact form through which we provide one within 14 days (WCAG 1.2.2, 1.2.3). PDF reports: all generators (coaching templates, handouts, coaching reports, documentation, institution and organisation reports, and the DPA) write Title, Author, Subject and Lang into the PDF dictionary. The shared layout declares the lang attribute, a distinct document title, Dublin Core meta tags, a semantic heading order and meaningful alt text for logos (WCAG 1.3.1, 3.1.1, 2.4.2). Full PDF/UA-1 tag-tree conformance is not technically achievable through DomPDF; we re-render any document with a tagged structure on request. Complex wizard components: the shared wizard shell broadcasts step transitions and progress through a polite aria-live region, and validation errors through an assertive role="alert" region (also surfaced as a visible error banner). The "Next" button uses aria-disabled rather than disabled, so the reason a step is locked stays audible to screen readers (WCAG 4.1.3). Colour contrast: the gold accent is paired with the brand-navy foreground on public surfaces, giving roughly 6.4:1. Status colours used inside charts have been standardised on Tailwind's 700 stops, and the --muted-foreground token has been raised to #475569 (WCAG 1.4.3). Other measures in place "Skip to main content" link (resources/js/components/skip-to-content.tsx) on every page Correct lang and dir attributes on the <html> element per selected language (German, English, Arabic with RTL, Russian; more languages coming soon) Respect for the user preference prefers-reduced-motion across our built-in animations Semantic HTML (heading hierarchy, landmark roles) built on Radix UI primitives with their built-in keyboard and focus behaviour Two-factor authentication (TOTP) via Laravel Fortify, fully completable from the keyboard If you encounter any residual barriers, please report them through the contact details below. We commit to acknowledging every report within 14 days. Preparation of this statement This statement was prepared