Accessibility Statement

Last updated: 2026-06-22

This statement applies to canopybeacon.uk. It was prepared on 27 May 2026 and last reviewed on 22 June 2026. Northern Edge Software Ltd is committed to making CanopyBeacon Pro accessible in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (“Accessibility Regulations”).

Compliance Status

CanopyBeacon is partially compliant with WCAG 2.2 Level AA. The known issues listed below prevent full compliance.

Known Issues

Icon-only buttons (Lucide React icons): several action buttons in the Sidebar, MobileQuickBar, and map controls lack visible text labels. Screen readers may announce generic icon names. Fix planned: add aria-label to all icon-only buttons. (WCAG 4.1.2 — Name, Role, Value)
Colour contrast: the fire-600 accent colour (#e63946) against a white background achieves 4.5:1 for large text but may fall below 4.5:1 for small body text. Full audit in progress. (WCAG 1.4.3 — Contrast Minimum)
Focus rings: keyboard focus indicators are present on most interactive elements via Tailwind focus:ring-2, but several custom dropdown and map components lack visible focus outlines. (WCAG 2.4.7 — Focus Visible)
Map component: the Leaflet/MapLibre integration does not expose landmark data to assistive technologies. Keyboard navigation within the map is limited. (WCAG 2.1.1 — Keyboard)
Data tables: several incident and fleet tables lack scope attributes on header cells. (WCAG 1.3.1 — Info and Relationships)
Toast notifications: transient notifications use a custom Toast component; the ARIA live region role is set but the dismiss timeout may be too short for some users. (WCAG 2.2.1 — Timing Adjustable)
PDF/document downloads: PDFs generated for incident reports and training records have not been tested for PDF/UA accessibility standards. (WCAG 1.1.1 — Non-text Content)

What We Are Doing to Improve

We are working to address the icon-label and focus-ring issues in the next development sprint. A comprehensive WCAG 2.2 AA audit across all pages is scheduled for Q3 2026. We will update this statement following that audit.

How to Report an Accessibility Problem

If you find an accessibility barrier not listed above, please contact us:

Email: [email protected]
We aim to respond within 5 working days.

Enforcement

If you are not satisfied with our response to your accessibility complaint, you can contact the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com.

The Equality and Human Rights Commission (EHRC) is the enforcement body for the Public Sector Bodies Accessibility Regulations in Great Britain. If you are located in Northern Ireland, contact the Equality Commission for Northern Ireland (ECNI).

Technical Information

CanopyBeacon uses Next.js 15 (React 19), Radix UI primitives (which carry ARIA defaults), and Tailwind CSS. The platform was last tested against WCAG 2.2 AA criteria on 27 May 2026 using manual keyboard navigation and axe-core automated scanning. No third-party accessibility audit has been conducted to date.

This statement was prepared using the GOV.UK guidance on accessibility statements.