Accessibility Support in Reporting

Updated 

Accessible reporting covers a wide range of recommendations for making dashboards and reports more accessible. Accessibility Support will make content more accessible to everyone and will also often make dashboard and report data more usable to every users in general. Sprinklr Accessibility Support is accessible according to WCAG Level AA compliance standards. We are committed to improving the user experience in terms of accessibility and compatibility for one and all. WCAG relies on four guiding principles for building accessible UIs:

  • Perceivable: Information and user interface components must be presentable to users in ways they can perceive.

  • Operable: User interface components and navigation must be operable.

  • Understandable: Information and the operation of the user interface must be understandable.

  • Robust: Content must be robust enough that it can be interpreted by a wide variety of user agents.

Service Analytics reporting promotes screen-reader compatibility, enabling essential information in widgets and tables to be articulated distinctly and with appropriate context. This facilitates comprehensive access to insights while preserving thoroughness and precision.

Business Use Cases

  • Enable users to navigate dashboards efficiently by breaking displayed information into readable elements with clear labels and structured descriptions for screen readers.

  • Ensure compliance with accessibility standards across reporting interfaces by providing consistent, meaningful context instead of raw or ambiguous values.

Reporting View

The accessibility of Service Analytics Table Widgets in reports is supported in both Enterprise View and Persona View.

This guarantees uniform accessibility functionality across frequently utilized reporting interfaces.

To enhance clarity for screen-reader users, it is essential to provide enriched, contextual read-outs in the following formats:

  • Post Formatter

  • Case Formatter

This ensures that key case identifiers and context are communicated clearly in a single, understandable narration.

Support at Widget Level

The specified enhancements target specific components, such as tables, charts, and tooltips:

Area

Improvement

Data Table Accessibility

Made tables easier to use by adding proper semantic HTML, so screen readers can interpret them accurately and assistive technologies are better supported.

Tooltip Accessibility

Improved tooltips so they show up on hover and keyboard focus, stay visible while focused, and can be fully navigated using the keyboard.

Chart Accessibility

Updated charts with proper toggle-button behavior for legend items and made all chart controls fully keyboard accessible, including arrow-key support for the WorkQueue Slider.

Visual Contrast

Ensured lines, bars, areas, and legend color swatches have at least a 3:1 contrast ratio against backgrounds, making them easier to see.

Button Accessibility

Added clear, descriptive names for buttons using aria-label or aria-labelledby, including helpful context like case numbers or row details for screen readers.

Media Controls Accessibility

Gave media buttons meaningful names using aria-label, aria-labelledby, or descriptive alt text so users can easily understand what each control does.

Support at Dashboard Level

The specified enhancements are done at the Dashboard Level:

Area

Improvement

Zoom & Text Scaling

Made 200% zoom and text enlargement work smoothly so content and controls adjust correctly without getting cut off, while keeping the minimum 3:1 contrast ratio for readability.

Keyboard Accessibility

Improved keyboard support—now you can use the ESC key to close overlays or active content, and single-character shortcuts can be turned off or modified, only activating when focused.

Focus Management

Cleaned up keyboard focus order by skipping non-functional elements, reducing extra stops, and preventing screen readers from announcing things that aren’t interactive.

Language & Input Accessibility

Made it easier to work with different languages and inputs by clearly marking or translating text, providing labels for fields, showing required fields, and giving guidance on correct formats.

Multilingual Support

Added translation support for interactive components so users can access and use content comfortably in multiple languages.