Overview#
Platform Accessibility Standards raises the interface baseline toward WCAG 2.2 AAA, giving dispatchers, analysts, and field staff guaranteed touch-target sizes, dark-theme contrast beyond enhanced thresholds, keyboard-operable selection controls, and standard autofill semantics.
Operational software fails quietly when a gloved finger misses an undersized button or a night-shift operator squints at low-contrast statistics. The platform now enforces its accessibility floor in the shared interface primitives themselves: every button guarantees a minimum 44-pixel touch target that styling cannot override, dark-theme contrast has been raised well past AAA thresholds, complex selection controls work entirely from the keyboard, and personal-data forms advertise proper autofill semantics. The baseline benefits every user, and it is decisive for operators with motor or vision impairments and for agencies that procure against accessibility requirements.
Key Features#
- Guaranteed Touch Targets: All button primitives enforce a 44-pixel minimum touch target, including icon buttons in the global navigation, matching the WCAG 2.2 AAA target-size criterion.
- Style-Proof Enforcement: The size floors live inside the shared primitives rather than in per-screen styling, so no individual screen can accidentally ship an undersized control.
- Dark-Theme Contrast Past AAA: Border and input contrast in the dark theme was raised from 1.30:1 to 3.56:1, and text colour pairs now clear 7.39:1, above the 7:1 enhanced-contrast threshold.
- Readable Operational Surfaces: Stat cards, the help centre, and profile surfaces were corrected for dark-mode readability, including the trend colours on statistics.
- Keyboard-Operable Complex Controls: Multi-select entity pickers are fully keyboard operable, so selection-heavy workflows never depend on a pointer.
- Autofill Semantics on Personal Data: Personal-data inputs across six components advertise standard autocomplete tokens, including postal-code hints, so browsers and assistive technology can identify and fill fields correctly.
- One Accessible Primitive Set: Dead, inaccessible duplicate interface primitives were deleted, leaving only the accessible versions for every product team to build on.
Use Cases#
- Touch Operation Under Pressure: A field responder, or an operator with a motor impairment, reliably hits every button on a touch device because no button target falls below 44 pixels.
- Night-Shift Control Room: A dispatcher working overnight in dark mode reads every statistic, border, and trend indicator without strain because contrast now exceeds AAA thresholds.
- Keyboard-Only Analysis: An analyst who works without a pointer drives multi-select entity pickers from the keyboard alone, from opening the picker to confirming a selection.
- Accurate Personal-Data Entry: A records officer completes forms quickly and correctly because fields announce their purpose through standard autofill semantics.
- Procurement and Compliance Evidence: An accessibility officer cites the enforced target sizes and measured contrast ratios when answering WCAG-based procurement questionnaires.
Integration#
The accessibility baseline is delivered through the shared interface primitives used across the whole platform, so the emergency call-taking console, operational analytics dashboards such as the body-worn camera panels, workforce management workspaces, and evidence and case tools all inherit the same floors automatically. New modules built on the primitives receive the guarantees without any extra work, and the enforcement complements neighbouring capabilities such as dashboard layout customisation and the platform dark theme, keeping personalised layouts and themed surfaces inside the same accessible envelope.
Open Standards#
- WCAG 2.2 Target Size, Enhanced (2.5.5, Level AAA): The 44-pixel minimum touch target floor on all button primitives meets the enhanced target-size criterion.
- WCAG 2.2 Contrast, Enhanced (1.4.6, Level AAA): Dark-theme text colour pairs at 7.39:1 and above exceed the 7:1 enhanced-contrast threshold.
- WCAG 2.2 Non-text Contrast (1.4.11): Borders and input outlines at 3.56:1 exceed the 3:1 minimum required for user interface components.
- WCAG 2.2 Keyboard (2.1.1): Complex selection controls such as multi-select entity pickers are operable through the keyboard alone.
- WCAG 2.2 Identify Input Purpose (1.3.5): Personal-data inputs carry standard input-purpose tokens so their meaning is programmatically determinable.
- HTML Living Standard Autofill Vocabulary: Field purposes, including postal-code hints, use the standard autocomplete token vocabulary understood by browsers and assistive technology.
- EN 301 549: The European ICT accessibility standard incorporates WCAG success criteria, so raising the platform's WCAG floor directly supports assessments against it.
Last Reviewed: 2026-07-16 Last Updated: 2026-07-16