Accessibility Statement

REDP!NG aims to make its emergency communication and coordination workflows more accessible to a broad range of users, including people with disabilities.

Last Updated: September 27, 2025 | Version: 2.0

Public overview of current accessibility goals and implementation direction

Visual Accessibility

  • • High contrast color schemes for readability
  • • Screen reader support improvements
  • • Scalable fonts and adjustable text sizes
  • • Alternative text for key images and icons

Hearing Accessibility

  • • Visual alerts for audio emergency notifications
  • • Text-based emergency communication options
  • • Device-based vibration alerts where supported
  • • Captions or transcripts for supported media content

Motor Accessibility

  • • Voice-assisted activation where supported
  • • Large touch targets for mobile interfaces
  • • Keyboard navigation support
  • • Gesture alternatives for critical functions

Cognitive Accessibility

  • • Simple, clear emergency interface design
  • • Consistent navigation and layout
  • • Minimal cognitive load for emergency actions
  • • Clear instructions and help documentation

Emergency Response Accessibility

Critical Emergency Features

REDP!NG includes accessibility-oriented workflow options intended to help more users interact with alerts, messages, and coordination features:

Emergency Activation
  • • One-touch emergency button
  • • Voice-assisted activation where supported
  • • Automated detection features where available
  • • Alternative activation methods where supported
Communication Options
  • • Text-to-speech support for incoming content where available
  • • Speech-to-text support for compatible voice workflows
  • • Pre-written emergency messages
  • • Visual status indicators

Accessibility Approach

Accessibility References

  • WCAG guidance: Used as a reference for accessibility improvements
  • ADA considerations: Reviewed as part of accessibility planning
  • Section 508 references: Considered where relevant to supported interfaces
  • Regional requirements: May vary by deployment and jurisdiction

Technical Implementation

  • ARIA labels: Used to improve assistive-technology support
  • Semantic markup: Structured content for better navigation
  • Color contrast: Reviewed as part of interface design
  • Focus management: Keyboard and focus behavior are considered during implementation

Accessibility Support

We are committed to continuous improvement of our accessibility features. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

Accessibility Team: accessibility@redping.org

Phone: Contact options may vary by region and support channel

Response Time: Reply timing depends on request volume and support availability

Emergency Accessibility Support

If you need help using accessibility-related features during an emergency, available support options and alternative communication methods will depend on the current workflow and service conditions.