New Features

No New Features

Feature Enhancements

Improved Accessibility for Links, Buttons, and Inputs

• What - Updated link, button, and input element naming to ensure all interactive elements are uniquely identifiable, descriptive, and compatible with assistive technologies, improving overall accessibility and usability across the platform.
• Why - Clear and consistent labeling is critical for users relying on screen readers and other assistive tools, ensuring they can accurately understand and navigate the interface without confusion.
• How
  • Navigate to any module with interactive elements (links, buttons, forms)
  • Interact with updated UI elements
  • Observe:
    • More descriptive link and button labels
    • Properly labeled input fields
    • Improved screen reader announcements
  • Note:
    • Changes align with WCAG accessibility standards
• Use Case - A user utilizing a screen reader can now clearly distinguish between multiple actions on a page, such as submitting a form or navigating to a specific section, improving efficiency and reducing errors during time-sensitive operations.

Improved Heading Structure and Page Titles

• What - Enhanced page structure by implementing proper heading hierarchy and ensuring all pages include clear, descriptive titles to improve navigation and accessibility.
• Why - Proper document structure enables assistive technologies to interpret content correctly, allowing users to navigate quickly and understand page context more effectively.
• How
  • Navigate to any page within the application
  • Review:
    • Presence of a single primary H1 heading
    • Logical heading progression (H1 → H2 → H3)
    • Updated browser tab titles
  • Note:
    • All updates follow WCAG accessibility guidelines
• Use Case - A user navigating via screen reader shortcuts can jump between sections of a page efficiently, improving situational awareness during active incident management.

Enhanced Table Accessibility and Structure

• What - Improved table semantics by properly defining headers and distinguishing between layout and data tables, ensuring assistive technologies can accurately interpret table content.
• Why - Tables without proper structure can lead to confusion for users relying on screen readers, making it difficult to understand relationships between data points.
• How
  • Navigate to any page displaying tabular data
  • Interact with tables and observe:
    • Clearly defined column and row headers
    • Improved navigation using assistive tools
  • Note:
    • Layout tables are now ignored by screen readers when appropriate
• Use Case - A user reviewing incident data in a table can now accurately interpret row and column relationships, ensuring correct understanding of unit assignments and statuses.Command – PAR Support for Unassigned Units Within Divisions

• What - Enhanced the Personnel Accountability Report (PAR) functionality to include all units within a division, even if those units are not assigned to a specific task. Units in the division’s Unassigned section are now automatically included in division-level PAR checks.

• Why - Previously, PAR checks focused primarily on units assigned to tasks, which could leave unassigned units outside the accountability process. Including all division units ensures full accountability coverage and prevents personnel from being unintentionally excluded during critical PAR verification events.

• How

  • Navigate to Incident Command

  • Open the appropriate Division board

  • Initiate a PAR check

  • The system will automatically include:

    • Units assigned to tasks

    • Units located in the Unassigned section within the division

  • Notes:

    • PAR responses function the same for assigned and unassigned units

    • Action Log entries maintain the existing format and behavior

• Use Case - During a working incident, several units are staged within a division but not yet assigned to tasks. When a PAR check is initiated, those units are automatically included in the accountability process, ensuring the commander receives confirmation of all personnel operating within that division.

Command Board Benchmark Menu Auto-Dismiss

• What - Enhanced the Command Board Benchmark Menu to automatically close after a short period of inactivity and to immediately dismiss when users click or tap outside of the menu. This update aligns the Benchmark Menu with the behavior of other Command Board menus, preventing persistent overlays and improving overall interaction consistency during active incident management.

• Why - Persistent menus can obstruct critical assignment and incident information, especially during high-tempo operations. By introducing auto-dismiss and outside-click behavior, this enhancement reduces screen clutter, improves visibility of key data, and ensures a more predictable and consistent user experience across Command Board interactions.

• How

  • Open the Command Board.

  • Select a Benchmark Menu from the available options.

  • Interact with the menu as needed.

  • The menu will automatically close after 5 seconds of inactivity.

  • Click or tap anywhere outside the menu to immediately dismiss it.

  • Behavior is consistent with other Command Board menus and requires no configuration.

• Use Case - During an active incident, a user opens the Benchmark Menu to review assignment benchmarks but then shifts focus to other tasks. Instead of the menu remaining on screen and blocking assignment visibility, it automatically closes after a few seconds, allowing the user to maintain a clear view of the Command Board without manual cleanup.

Fixes

Command – Assignment Order Preservation from Mobile Command

• What - Fixed an issue where assignment order from templates was not preserved when command was initiated from the mobile application. The API now ensures assignments are inserted in the correct sequence so that template-defined ordering remains consistent across both web and mobile Incident Command views.

• Why - When assignments were created from a template through the mobile command workflow, the order could become inconsistent due to missing ordering logic during API insertion. This could cause assignments to appear out of sequence or appear missing, making the command board harder to manage.

• How

  • Initiate command from the Responder Mobile App

  • Select a Command Template

  • The system creates assignments through the POST /api/v1.7/command endpoint

  • The API now applies proper ORDER BY logic when inserting assignments

  • Notes:

    • Assignment order now matches the template configuration

    • Behavior is consistent between Web and Mobile Incident Command

• Use Case - A chief officer takes command using a preconfigured incident template on a tablet. The template includes assignments such as Attack, Search, Ventilation, and Rapid Intervention. After the fix, the assignments appear in the exact order defined in the template, allowing command staff to manage resources more effectively.

Command Board Rank Color Consistency

• What - Fixed an issue where rank text and background colors were inconsistent between the Assignment Board and the Incident Command Board (Units section). Rank styling now correctly reflects the configured settings across all Command Board views, ensuring uniform visual representation.

• Why - Inconsistent rank colors can lead to confusion and reduce the effectiveness of visual cues used to quickly identify roles and hierarchy. Aligning styling across all views improves clarity and ensures users can rely on consistent visual indicators during operations.

• How

  • Open the Command Board.

  • View personnel within the Assignment Board and Incident Command Board.

  • Confirm that rank colors and styling match configured settings across both areas.

  • No configuration changes are required for this fix.

• Use Case - A command staff member reviewing personnel assignments across multiple board views can now quickly identify ranks without second-guessing inconsistencies, improving situational awareness and decision-making speed.

Command Board Assignment Layout Stability (iPad)

• What - Resolved an issue on iPad Command Board where assignment buckets could display random gaps, causing assignments to be pushed off-screen and layout corruption to persist across devices. The fix ensures a stable, packed layout with proper assignment ordering and improved handling of long assignment names.

• Why - Layout inconsistencies can hide critical assignment information and disrupt operational workflows, especially when changes persist across devices. This fix restores predictable layout behavior and ensures assignments remain visible and accessible at all times.

• How

  • Open the Command Board on an iPad.

  • Review assignment buckets and unit placements.

  • Confirm assignments are displayed in a packed, gap-free layout.

  • Add or modify assignments to observe correct positioning and ordering.

  • Long assignment names will display properly, with full names available via tooltip where applicable.

• Use Case - During an incident, a user managing assignments on an iPad can now trust that all assignments are visible and properly arranged without needing to refresh or manually correct the layout, ensuring no units or roles are overlooked.