Skip to main content
Back to Web SDK Overview The Web SDK chat widget is designed to meet WCAG 2.2 Level AA (ADA AA) standards. This page covers compliance status, supported components, and developer guidelines for maintaining accessibility in customizations. For a full overview of the SDK, see How the Web SDK Works.

​
Compliance Status

ProductCompliance Level
Kore Web SDKFull compliance — WCAG 2.2 Level AA
For details, see the official WCAG 2.2 documentation or download the Voluntary Product Accessibility Template (VPAT).

​
Accessibility Support by Component

ComponentAccessiblePreview
Chat IconYesChat Icon
Chat WindowYesChat Window
Welcome ScreenYesWelcome Screen
HeaderYesHeader
FooterYesFooter
TemplatesYesTemplates
The SDK is fully compatible with screen readers.

​
Themes and Color Contrast

Default light and dark themes maintain a color contrast ratio of 4.5:1 or higher, meeting WCAG 2.2 Level AA out of the box. For custom themes, follow the Virtual Assistant Theme & Design guidelines. Ensure:
  • All color combinations meet minimum contrast ratios (4.5:1 normal text, 3:1 large text and UI elements).
  • Interactive elements are clearly distinguishable.
  • Focus indicators meet contrast requirements.
  • Custom themes are tested with assistive technologies before deployment.

​
Developer Guidelines

When customizing or extending the SDK, follow these practices to maintain compliance:
PracticeRequirement
Semantic HTMLUse appropriate HTML5 elements to define structure and meaning
ARIA attributesAdd ARIA roles and attributes for dynamic content and custom controls. See WAI-ARIA Authoring Practices
Keyboard navigationAll interactive elements must be focusable and keyboard-operable in a logical order
Color contrastNormal text: 4.5:1 minimum; large text and graphics: 3:1 minimum
Text alternativesProvide alt text for all non-text content (icons, images)
Responsive designEnsure the widget is accessible across screen sizes and orientations
TestingRegularly test with tools and assistive technologies (NVDA, JAWS, VoiceOver)
For customization reference, see the Web SDK Customization Documentation. Accessibility compliance for any customizations made beyond the default SDK is the responsibility of your organization.

​
Support

If you encounter an accessibility issue or want to share feedback: