AI & Automation
AI for every conversation, campaign, and customer
Khoros is committed to ensuring digital accessibility for all users. Below is an overview of the accessibility status across each version of the Khoros Communities solution.
Khoros Communities: Aurora Version
Khoros adheres to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA and plans to adhere to WCAG 2.2, Level AA in connection with the Aurora version of the Khoros Communities solution (“Aurora”).
To ensure that we meet these standards, we have rigorous automated and manual internal testing that is part of the standard Aurora development process. For each release, we test keyboard navigation, heading levels, field labels, and interactive page elements to ensure that content is accessible and being read out correctly by screen readers. We also use a third-party vendor to help manually assess the user flows, identifying and resolving accessibility violations. As part of Aurora, we have also added several accessibility features. We have also completed a Voluntary Product Accessibility Template (“VPAT”) against WCAG 2.1 AA guidelines and plan to re-evaluate Aurora against WCAG 2.2 AA guidelines.
To ensure compliance with the European Accessibility Act (“EAA”), which goes into effect in June 2025, we plan to test Aurora against the EN 301 549 standard, which is the presumptive standard for EAA. The EN 301 549 standard is expected to be updated to follow WCAG 2.2 AA guidelines.
Khoros Communities: Classic Version
We will not seek accessibility certification for the Classic version of the Khoros Communities solution (“Classic”), as the platform does not meet W3C or ADA accessibility standards. Any accessibility issues that Khoros finds are classified by Khoros as Critical/Serious/Moderate/Minor, and are prioritized for resolution accordingly.
Khoros offers an accessibility plugin that can be enabled within individual instances, however it may conflict with customizations. This plugin may help customers on Classic score higher on accessibility tests, but does not give full compliance with any standards.
Additionally, customers’ accessibility architects may monitor and report to Khoros any accessibility issues that they would like Khoros to consider. Once Khoros examines the submitted issue, Khoros may either: (i) engage its Professional Services team so that the resolution can be implemented within the customer’s product instance; or (ii) submit the issue to Khoros’s Engineering team to be evaluated for inclusion in a future out of the box product release.