Axon 911 Frontend Docs
    Loading navigation…
U
User
Switch to light mode
  1. Components
  3. Data Color
  5. Accessibility

Data color

Accessibility

What the system handles
  • Paint isolation. DataColor flows through internal runtime variables on Shape and Swatch, not through author style attributes.
  • Invalid data. Failed validation paints none at render time so a bad payload does not inject CSS.
What you must provide
  • Color is never the only carrier of meaning. Pair vendor-colored marks with visible labels, legend text, or tooltips. Operators who cannot distinguish two layer colors must still read the layer name.
  • Contrast is the data owner's responsibility. Third-party palettes are not tuned for your surface theme. When a mark sits on UI chrome you control, verify contrast against the background or add a neutral outline via token stroke on Swatch or Shape.
  • Decorative swatches. Legend keys are usually decorative: true; the row or tooltip carries the name. Meaningful marks need label copy like any other Shape or Swatch.
Semantics
DataColor does not change roles or names. Accessibility follows the host Shape or Swatch contract (role="img" when labelled, aria-hidden when decorative).
Known caveats
  • Dark mode. Vendor colors may fail on dark surfaces; do not assume the same hex works in both themes without checking.
  • Live map overlays. Fast layer toggles should not rely on color alone; keep layer names in the legend or panel list in sync with swatch paint.
Previous
Data color / API and Development
Next
Data list / Usage
On this page
What the system handles
What you must provide
Semantics
Known caveats