Making Kailvex content and tools easier to use.
Kailvex aims to provide a clear, responsive and keyboard-friendly website while continuing to improve accessibility across pages and browser tools.
Our approach
We work toward practical accessibility using semantic HTML, labelled form controls, readable contrast, responsive layouts, keyboard interaction and reduced-motion support where appropriate.
Accessibility features
The website includes skip links, visible headings, descriptive links, alternative text for meaningful images, form labels, focus states and support for users who prefer reduced motion.
Known limitations
Accessibility can vary across browsers, assistive technologies, third-party embeds and generated documents. Automated checks alone cannot confirm complete accessibility. We continue to review important user journeys and tool interfaces.
Accessibility feedback
To report an accessibility barrier, email support@kailvex.com with the page URL, the issue experienced and the browser or assistive technology used. We will review reasonable feedback and prioritise practical improvements.
Last updated: 28 June 2026
Accessibility is checked across important journeys.
We review navigation, keyboard focus, headings, forms, buttons, colour contrast, motion preferences and responsive layouts when pages or browser tools change. Automated testing can identify common issues, but it cannot replace manual use with a keyboard, screen reader or different zoom levels. Priority is given to barriers that prevent people from reading content, submitting an enquiry or using a public tool.
Browsers and assistive technology can behave differently.
The website is designed for current versions of major browsers and common mobile devices. Older browsers, browser extensions, translated content and third-party services may create differences outside Kailvex control. When reporting a barrier, include the page address, device, browser, assistive technology and the step that failed so the issue can be reproduced and assessed accurately. When possible, include a screenshot or short screen recording and explain the expected result. This helps the team confirm impact, test a correction and communicate a practical resolution.