KAI Conversations Ltd is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.
This statement was updated on Jan 7, 2025.
Measures to Support Accessibility
KAI Conversations takes the following measures to ensure accessibility of the KAI App and Portal:
- Include accessibility as part of our mission statement.
- Integrate accessibility into our procurement practices.
- Appoint an accessibility officer and/or ombudsperson.
- Provide continual accessibility training for our staff.
- Assign clear accessibility targets and responsibilities.
Conformance Status
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. KAI Conversations App and Portal are partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. KAI is committed to improving accessibility and working towards WCAG 2.1 AA rating.
Feedback and Contact Information
We welcome your feedback on the accessibility of [Your Website/App Name]. Please let us know if you encounter accessibility barriers:
- Phone: +447824397097
- E-mail: help@kaiconversations.com
We try to respond to feedback within 5 business days.
Known Issues and Limitations
This statement outlines the known accessibility limitations of our web application and the steps we are taking to address them. We are actively working to improve the user experience for everyone and are committed to ensuring our application is accessible to the widest possible audience, regardless of ability or technology.
General Accessibility Limitation:
Keyboard navigation
Limitation: Keyboard navigation of the KAI Portal is not supported.
Reason: Legacy platform to be removed
Solution: Replacement of KAI Portal is to be delivered
Screen reader
Limitation: Portal and App have limited screen reader support
Reason: Portal is a legacy platform to be replaced. App improvements planned as part of next upgrade
Solution: Replacement of the KAI Portal. Roadmap items to delivery screen reader support for App
Non-Accessible Content
The content listed below is non-accessible for the following reasons. We have detailed the limitations, the likely reasons for their occurrence, and our proposed solutions to bring them into compliance with accessibility standards.
1. Aria and Button Elements
- Limitation: Several ARIA (Accessible Rich Internet Applications) input fields and buttons lack accessible names. This means that screen readers cannot adequately describe the function of these elements to visually impaired users.
- Reason: This issue likely stems from a development oversight where aria-label or aria-labelledby attributes were not included for these interactive elements.
- Solution: We will add appropriate aria-label or aria-labelledby attributes to all interactive ARIA and button elements to ensure they are properly described by screen readers. For example, a button that currently has no accessible name will be updated with a descriptive label such as "Save PDF" or "Zoom In".
2. Color Contrast
- Limitation: The color contrast between the text and background on certain elements, specifically the "PUBLISHED" badge, is insufficient. This can make the text difficult to read for users with low vision or color blindness.
- Reason: The current color scheme for these badges does not meet the minimum contrast ratio of 4.5:1 as recommended by the Web Content Accessibility Guidelines (WCAG).
- Solution: We will adjust the color palette of our badges to ensure a sufficient contrast ratio. This will likely involve using a darker text color on a light background or vice versa to meet accessibility standards.
3. Frame Titles
- Limitation: An <iframe> element on our pages is missing a descriptive title. Without a title, screen reader users may not understand the content or purpose of the embedded frame.
- Reason: The title attribute was not added to the <iframe> during development.
- Solution: We will add a descriptive title attribute to all <iframe> elements to clearly communicate their content to users of assistive technologies. For instance, the <iframe> for the Jira Service Desk widget will be given a title such as "Jira Service Desk Widget".
4. Viewport Zooming
- Limitation: The ability to zoom in on the page is disabled in the viewport's meta tag. This prevents users with low vision from magnifying the content to a comfortable reading size.
- Reason: The user-scalable=no attribute was included in the <meta name="viewport"> tag, and the maximum-scale is set to less than 5.
- Solution: We will remove the user-scalable=no attribute and ensure the maximum-scale attribute is set to 5 or greater in the viewport meta tag. This will enable users to zoom in on the page as needed.
5. Touch Target Size
- Limitation: Some interactive elements, such as buttons for moment tag controls, have a touch target size that is too small. This can make it difficult for users with motor impairments to accurately activate these controls.
- Reason: The size of these buttons does not meet the minimum recommended touch target size of 24x24 pixels.
- Solution: We will increase the size of all touch targets to a minimum of 24x24 pixels to ensure they are easily activated by all users. This may involve increasing the padding or the overall dimensions of the interactive elements.
Technical Specifications
Accessibility of KAI Conversations App and Portal relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
- HTML
- WAI-ARIA
- CSS
- JavaScript
These technologies are relied upon for conformance with the accessibility standards used.
Assessment Approach
KAI Conversations assessed the accessibility by the following approaches:
- Self-evaluation with automated tools and manual review