← Back to Helond

Accessibility Statement

Last audited: 2 July 2026 · Statement published: 2 July 2026

Our commitment

Helond is committed to making its platform accessible to all users, including those with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, as referenced by the European Accessibility Act 2025 and the EN 301 549 standard, and by Irish SI 358/2020 implementing the EU Web Accessibility Directive.

Conformance status

Partially conformant — WCAG 2.1 Level AA

All issues identified in our July 2026 audit have been remediated. A follow-up automated scan is scheduled for Q1 2027 to confirm full conformance across all routes.

Partially conformant means that some content does not fully conform to the standard. The non-conformances known at time of publication are listed in the Known issues section below.

Scope

This statement covers the following Helond web properties:

  • app.helond.com — the main product application (league admin, fixture secretary, match official portals)
  • helond.com — the marketing and documentation site

Third-party services embedded in or linked from Helond (e.g. Stripe payment pages, Revolut deep-links) are outside this scope and are subject to their own accessibility policies.

Audit — July 2026

A manual WCAG 2.1 AA audit was conducted on 2 July 2026 covering all primary user journeys: sign-up, league administration, fixture management, assignment workbench, referee portal, and payment flows. The audit identified 15 issues across four severity levels, all of which were remediated the same day.

Issues remediated (2 July 2026)

Critical

  • WCAG 1.3.1 / 3.3.2 — Login form inputs were missing programmatic label associations. Fixed: htmlFor/id pairs added.
  • WCAG 3.3.2 — Help chat textarea had no label (placeholder-only). Fixed: aria-label="Ask a question" added.

High

  • WCAG 1.1.1 / 4.1.2 — Multiple icon-only buttons (✕ close buttons) had no accessible name. Fixed: aria-label="Close" / aria-label="Dismiss" added.
  • WCAG 2.4.1 — No skip navigation mechanism existed. Fixed: "Skip to main content" link added as first focusable element; id="main-content" on main landmark.
  • WCAG 4.1.2 — Organisation switcher dropdown lacked ARIA state attributes. Fixed: aria-haspopup, aria-expanded, role="listbox" added.
  • WCAG 4.1.2 — Mobile navigation sidebar lacked dialog semantics. Fixed: role="dialog", aria-modal="true", ESC key handler added.
  • WCAG 2.1.2 — Contact modal had no keyboard focus trap. Fixed: full Tab cycling focus trap, ESC to close, role="dialog", aria-labelledby added.

Medium

  • WCAG 2.4.2 — 32 application pages had non-unique or missing <title> elements. Fixed: unique titles added to all pages via Next.js metadata exports; sibling layout.tsx files created for client-component auth/contact pages.
  • WCAG 1.4.3 — Avatar initials text (#FFFFFF on #B8960C) had a contrast ratio of 2.67:1, failing 4.5:1. Fixed: text changed to #0F2D1F (ratio ≈ 7:1).
  • WCAG 1.4.3 — Assignment workbench empty-state and filter chip text used text-gray-400 / text-gray-500 on white (ratios 1.9:1 – 3.95:1). Fixed: upgraded to text-gray-600 (ratio ≈ 5.9:1).
  • WCAG 2.4.7 — Availability calendar time inputs relied solely on a border-colour change for focus indication. Fixed: focus:ring-2 added alongside the existing border change.

Low

  • WCAG 2.4.6 — "View all" and "View →" links on the dashboard lacked descriptive accessible names. Fixed: aria-label attributes added.
  • WCAG 1.1.1 — Decorative product UI mockups on marketing pages were exposed to assistive technology. Fixed: aria-hidden="true" added to all mockup containers.
  • WCAG 1.3.1 / 3.3.2 — Sign-up, forgot-password, and reset-password forms had inputs without programmatic label associations. Fixed: htmlFor/id pairs added to all inputs.
  • WCAG 1.4.3 — Several secondary text colours failed 4.5:1 on their backgrounds (dashboard subtext #4A7A5A on #0F2D1F; disabled input prefix text text-gray-500 on bg-gray-50). Fixed: colours updated to meet or exceed 4.5:1.

Known issues

No known issues at time of publication. All identified non-conformances from the July 2026 audit have been resolved.

Technical specification

Helond relies on the following technologies for conformance:

  • HTML5 semantic elements (main, nav, header, footer, section)
  • WAI-ARIA 1.2 roles, states, and properties
  • CSS (Tailwind CSS) — responsive, rem-based typography, no CSS that overrides user font-size preferences
  • JavaScript (React / Next.js) — progressive enhancement; keyboard navigation implemented without pointer-only assumptions

Feedback and contact

If you experience any accessibility barrier on Helond, or if you need information in an alternative format, please contact us:

We aim to acknowledge accessibility feedback within 5 working days and to resolve reported issues within 30 days where technically feasible.

Enforcement procedure

If you are not satisfied with our response to an accessibility complaint, you may contact the relevant regulatory body:

This statement was prepared on 2 July 2026 and will be reviewed following each accessibility audit. Next scheduled review: Q1 2027.