High-Contrast Mode vs. Custom Dashboard Themes: Datadog Accessibility Trade-off

When building shared monitoring dashboards in Datadog, teams must decide between enforcing the platform's built-in high-contrast mode or preserving customizable light and dark themes with manually adjusted widget colors. High-contrast mode applies WCAG AA contrast ratios across all UI elements, but it overrides any user-selected dashboard color palettes. Customizable themes, by contrast, allow per-dashboard branding and personal color choices, yet they place the burden of contrast compliance on individual users.

This trade-off is complicated by scoping differences: high-contrast mode is toggled globally in user profile settings and takes effect immediately across every page, whereas theme adjustments are scoped to the current dashboard and require a page refresh. Teams that need both compliance and visual consistency currently have no documented way to apply a custom palette that automatically meets contrast thresholds.

An unresolved behavior regarding keyboard focus order in the monitor creation wizard adds further uncertainty for assistive technology users. Because this behavior is not yet addressed in current releases and may vary by browser, assistive technology, and Datadog UI version, it remains unclear whether the wizard's focus order will be corrected independently of the theme and contrast settings.

Given these constraints, which accessibility strategy should teams prioritize for shared Datadog dashboards? Is there a supported method to enforce contrast compliance without globally overriding custom widget colors? Does the unresolved focus order in the monitor creation wizard affect the choice between global high-contrast mode and per-dashboard theme customization?