Our approach
KaroGerman is being developed toward WCAG 2.2 Level AA practices. We use semantic page structure, visible focus states, labelled controls, text alternatives, responsive layouts, and automated and browser-based accessibility checks.
This is an ongoing process rather than a claim that every page is already free of barriers.
What we work to support
Our accessibility work includes:
- Keyboard navigation and logical focus order
- Screen-reader names for navigation, forms, buttons, and status messages
- Readable contrast, scalable text, and responsive layouts
- Captions, transcripts, or text alternatives for learning media where available
- Clear loading, error, empty, and success states
- Reduced-motion preferences for non-essential animation
Known and changing areas
Live-class accessibility can depend on the classroom provider, device permissions, captions, and the material supplied by a tutor. Generated or uploaded documents may not always have complete semantic structure when first received.
We review newly identified control-labeling, focus, media, and document-accessibility issues as part of product QA.
Request help or report a barrier
Email hello@karogerman.com with the page or feature, device/browser, assistive technology if relevant, and what you were trying to do. Do not include passwords, payment data, or private application documents.
If a format is inaccessible, ask for a reasonable alternative and we will assess the available options.