Accessibility
We build OneVoice so that content is perceivable and operable.
Implemented
- semantic HTML with a clear heading hierarchy
- keyboard operability and visible focus states
- skip link to the main content
- alternative text for meaningful images
- contrast that stays readable on light and dark surfaces
- status information is never conveyed by colour alone
Feedback
Responsible for accessibility: Markus Illing
We welcome reports of barriers: markus.illing@one-voice.io