AccessibilityAccessibility at PulseSafety

Built for every
officer.
Every ability.

CommandCORE is designed to work for everyone — keyboard-first navigation, screen reader support, high-contrast interfaces, and scalable text built into every module.

AA
WCAG 2.1 target
508
Section 508 aligned
ARIA
Semantic markup
Accessibility

Designed for everyone.

PulseSafety is committed to building software that works for every user — regardless of ability, device, or assistive technology. Accessibility is not an afterthought; it is foundational to how we design and develop CommandCORE.

We follow the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our baseline standard for all web properties, including this marketing site and the CommandCORE platform.

Our engineering and design teams review new features against accessibility criteria before release, and we conduct periodic audits to surface and remediate issues in existing interfaces.

WCAG 2.1 AA
Our accessibility standard

We target WCAG 2.1 Level AA compliance across all PulseSafety web properties and actively work toward Level AAA on critical user paths.

Our approach

Built on four principles.

The WCAG guidelines are organized around four core principles. Our work is guided by all four.

Perceivable
Perceivable

Information and user-interface components must be presentable to users in ways they can perceive. We provide text alternatives, captions, and sufficient color contrast throughout.

Operable
Operable

All UI components and navigation must be operable without a mouse. Every feature supports full keyboard navigation and avoids interactions that could cause physical discomfort.

Understandable
Understandable

Information and operation of the UI must be understandable. We use plain language, predictable navigation, and consistent labeling to reduce cognitive load.

Robust
Robust

Content must be interpreted reliably by a wide variety of user agents and assistive technologies. We write semantic HTML and test with screen readers on major platforms.

What we've built

Accessibility features
in CommandCORE.

These are some of the specific accessibility provisions built into the CommandCORE platform and this marketing site.

Full keyboard navigation

Every interactive element is reachable and operable via keyboard. Focus order follows a logical reading sequence on every screen.

Screen reader support

We use semantic HTML5 elements, ARIA landmarks, and descriptive labels so assistive technologies can accurately convey page structure and interactive controls.

Color contrast

All text and interactive elements meet or exceed the WCAG AA contrast ratio requirements (4.5:1 for normal text, 3:1 for large text).

Scalable text

Interfaces support text resizing up to 200% without loss of content or functionality, using relative font units throughout.

Touch target sizing

Interactive controls on mobile surfaces meet minimum 44×44px touch target guidelines so they're easy to activate on any device.

Error identification

Form errors are identified in text — not color alone — and describe what went wrong and how to correct it, meeting WCAG 3.3.1 and 3.3.3.

Compliance & standards

Where we stand.

We are transparent about our current compliance posture. We are actively improving.

WCAG 2.1 AAIn progress
Web Content Accessibility Guidelines

We target WCAG 2.1 AA across all web properties. Periodic third-party audits identify gaps we remediate on a rolling basis.

Section 508Aligned
U.S. Section 508 (Rehabilitation Act)

CommandCORE is designed to align with Section 508 requirements for federal and federally-funded programs. We provide a VPAT upon request.

ADA Title IIAligned
Americans with Disabilities Act — Title II

As a vendor to state and local government agencies, we design to meet the digital accessibility obligations under ADA Title II regulations effective 2026.

Need help?

Accessibility
support.

If you experience barriers using any PulseSafety web property or the CommandCORE platform, please let us know. We take every report seriously and respond within two business days.

[email protected]

When you contact us, please describe the barrier you encountered, the assistive technology or browser you are using, and the URL or screen where it occurred.

Agency customers with active contracts may also raise accessibility concerns directly with their named success lead for expedited review.

Reporting a barrier
  • Describe the barrier you encountered
  • Include your browser and assistive technology
  • Share the URL or screen where it occurred
Let's talk

Questions about
accessibility?

Our team is happy to discuss our accessibility roadmap, provide a VPAT, or schedule a walkthrough for users with specific access needs.