Accessibility Statement
Kairos is committed to making its website and digital experiences usable by as many people as possible, including people who use assistive technologies.
Our approach
We aim to build clear structure, readable content, keyboard-friendly interactions, sufficient contrast, and responsive layouts across supported devices.
Accessibility is considered during planning, design, implementation, testing, and ongoing improvement.
We use recognized accessibility practices as a guide, including the Web Content Accessibility Guidelines, while recognizing that conformance depends on the specific experience and content.
Some third-party tools, embedded content, or older material may not be fully under our control.
When we identify an issue, we aim to understand its impact and prioritize a practical correction.
Current accessibility priorities
We focus on semantic content, keyboard access, focus visibility, text alternatives, form labels, error messaging, motion preferences, and clear language.
- Use headings and landmarks to support navigation
- Provide meaningful labels and alternative text
- Preserve visible focus and keyboard access
- Maintain readable contrast and scalable text
- Avoid unnecessary motion and flashing content
Known limitations
Accessibility can vary across browsers, devices, assistive technologies, and third-party integrations. Some documents or legacy components may need additional remediation.
If an interaction is difficult to use, please tell us what you were trying to do and which technology or device you used.
Feedback
We welcome feedback about barriers, confusing content, missing alternatives, or features that do not work with your assistive technology.
Please contact agency@kairos.online with the page address, a description of the issue, and your preferred way to receive a response.
We will review reports and, where possible, provide an accessible alternative or a practical workaround while the issue is being addressed.
Client products
For a website or product delivered to a client, accessibility responsibilities, target standards, supported environments, and remediation priorities should be agreed in the project scope.
A client product may also contain content, integrations, or workflows managed by the client or another provider.
Testing and improvement
We combine manual review, keyboard checks, responsive testing, and appropriate automated checks. Automated tools help find patterns but cannot replace testing with real users and assistive technologies.
- Keyboard access and visible focus
- Headings, labels, landmarks, and alternative text
- Readable contrast, sizing, and reflow
- Clear forms, instructions, and error states
- Reduced-motion and non-flashing behavior
- A route for reporting accessibility barriers
A practical next step
If you encounter a barrier, send us the page, task, device, browser, assistive technology, and any error message you saw. This helps us reproduce the issue and decide on the right fix.
Updates
We may update this statement as our website, standards, and accessibility practices develop.
This statement describes our current intent and approach. It is not a certification or a guarantee that every page is fully accessible in every environment.
Conclusion
Accessibility works best as an ongoing practice. Your feedback helps us find barriers earlier and make digital products more useful to more people.
We build and improve digital products for real operating workflows.
Tell us where the product is now and where it needs to go. We’ll help define the clearest next step. See all FAQs
