Skip to content

Accessibility

Overview

The NISC Mustering System is designed to be usable by as many people as possible, including those who rely on assistive technologies such as screen readers, keyboard-only navigation, or display settings such as large text or high contrast. This page describes the accessibility features built into the system, known limitations, and how to report an accessibility issue.


Conformance Status

The NISC Mustering System aims to conform to WCAG 2.1 Level AA (Web Content Accessibility Guidelines, version 2.1, Level AA). This is the internationally recognised standard for accessible web content.

The assessment is based on self-evaluation against WCAG 2.1 Level AA success criteria, automated accessibility testing using axe-core, and manual keyboard navigation testing. The statement was last reviewed on 20 February 2026.


Accessibility Features

The following accessibility measures are applied throughout the application:

Semantic Structure

  • All pages use semantic HTML elements (<header>, <nav>, <main>, <section>, <article>) so that screen readers can understand the page structure.
  • Headings follow a logical hierarchy (H1, H2, H3) to allow users to navigate by heading level.

Keyboard Navigation

  • All interactive elements (buttons, links, form fields, navigation items) are reachable and operable using the keyboard alone.
  • A "Skip to main content" link is available at the top of every page. This link is the first focusable element when you press Tab after loading a page. Activating it jumps directly to the main page content, bypassing the header and navigation.
  • Navigation menus can be opened and closed using the Enter, Space, and Escape keys.
  • Tab order follows the visual reading order of the page.

ARIA Support

  • Interactive elements that change state (such as the sidebar toggle and the user menu) have aria-expanded attributes that communicate their current state to screen readers.
  • Navigation regions are labelled with aria-label so that users with multiple navigation areas can distinguish between them.
  • Live regions (aria-live) announce dynamic status changes — such as the connection status indicator — to screen reader users without requiring them to navigate to that element.
  • Form inputs have associated <label> elements and descriptive aria-describedby attributes linking to inline error messages.

Colour and Contrast

  • Text and interactive elements meet the WCAG 2.1 AA minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text and UI components.
  • Colour is not used as the sole means of conveying information. For example, error states are indicated by both colour and an explanatory text message.

Dark Mode

  • The system supports a dark colour theme that can reduce eye strain for users who are light-sensitive or prefer reduced brightness.
  • The dark/light toggle is available on both the Sign In page (top-right corner of the form) and in the application header after signing in.
  • The chosen theme is saved and persists across sessions.

Text Zoom

  • The interface is responsive and supports browser text zoom up to 200% without loss of content or functionality.
  • To increase text size in your browser: use Ctrl + (plus) on Windows or Cmd + (plus) on Mac. To reset, use Ctrl+0 or Cmd+0.

Form Accessibility

  • All form inputs have visible, descriptive labels.
  • Validation errors are presented as text messages directly below the relevant field, not just as colour changes.
  • Required fields are identified in the form markup.
  • The password field includes a show/hide toggle so users do not need to rely on correct typing alone.

Known Limitations

The following areas have identified accessibility gaps. We are working to address these in future releases:

Floor Plan Images

Uploaded floor plan images may not have alternative text descriptions. We recommend using descriptive file names when uploading floor plans (for example, building-a-ground-floor.png rather than image1.png). Screen reader users may not be able to interpret the spatial content of floor plan imagery directly.

Real-Time Interactive Map

The Leaflet-based indoor map (Floor Plan view) is partially keyboard accessible. Some map interactions — such as dragging to pan and scrolling to zoom — require a pointing device. Users who rely solely on a keyboard may have limited ability to explore the interactive map. The data shown on the map is also available in tabular format through the Dashboard and Emergency views.

BLE Scanner (Web Bluetooth)

The in-browser Bluetooth scanning interface relies on native browser dialog boxes provided by the operating system and browser. These dialogs may have varying levels of accessibility support depending on the browser and operating system in use. This limitation is outside the direct control of the NISC Mustering System.


Using Assistive Technologies

The system has been tested with the following assistive technology combinations:

  • NVDA (Windows) with Chrome
  • VoiceOver (macOS) with Safari
  • Keyboard-only navigation in Chrome and Firefox

If you use a different assistive technology and encounter a problem, please let us know using the contact details below.


How to Report an Accessibility Problem

We welcome feedback from users who encounter accessibility barriers. If something in the system is difficult or impossible to use with your assistive technology or access requirements, please contact us:

Email: support@nisc.com

Please include in your message:

  • A description of the problem you experienced
  • The page or feature where the problem occurred
  • The assistive technology and browser you were using (if known)

We aim to respond to accessibility feedback within 5 business days.


Requesting an Accessible Alternative

If a feature of the system is not accessible to you and an alternative format or process would help you complete your task, please contact support@nisc.com and describe what you need. We will work with you to find a suitable solution.


NISC Muster Tracking Documentation