1. Our commitment
We design and develop with accessibility as a first-class requirement, targeting conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, as published by the World Wide Web Consortium (W3C).
2. Conformance status
The Triforce website is partially conformant with WCAG 2.1 Level AA. Partial conformance means that some parts of the content do not yet fully conform to the standard — primarily the complex interactive features documented in Section 4 below.
3. Measures we take
We have implemented, or are actively implementing, the following accessibility measures:
- Semantic HTML5. Headings, landmarks, lists, and tables use correct markup so screen readers can navigate document structure efficiently.
- Keyboard operability. All core navigation paths — homepage, request flow, fleet listings, route pages — are fully keyboard-operable with visible focus indicators.
- Motion reduction (WCAG 2.3.3). All animated components respect the
prefers-reduced-motionOS preference. TheScrollStoryparallax crossfade,StackingCardshover transforms, andCardRailhorizontal scroll all degrade to reduced or zero motion when the user has set this preference in their operating system. - Color contrast. Text and interactive element contrast meets the WCAG AA 4.5:1 ratio for normal text and 3:1 for large text and UI components.
- ARIA. WAI-ARIA 1.2 attributes are applied to dynamic widgets — the chat concierge panel, the card rail navigation, and the install prompt — to expose roles, states, and properties to assistive technologies.
- Bilingual RTL layout. The Arabic (
/ar) site uses CSS logical properties and Tailwind RTL utilities to ensure correct right-to-left rendering. Latin-only runs (phone numbers, brand names) are explicitly isolated withunicode-bidi: isolate. - Error identification. Form validation errors are associated with their inputs via
aria-describedbyand surfaced in descriptive language, not by colour alone. - Images. Decorative images carry
alt="". Informative images and aircraft illustrations carry descriptivealttext. - Zoom. The layout is tested to 200% zoom without loss of content or functionality. Font sizes are specified in
rem/emunits throughout. Form inputs are set to a minimum of 16 px to prevent iOS Safari’s automatic viewport zoom on focus. - Session timeouts. The magic-link sign-in token expires after 15 minutes, but users are notified and can request a new link without losing form state.
4. Known limitations
The following features do not currently meet full WCAG 2.1 AA conformance and are tracked for remediation:
- WebGL flight simulator (/simulator). The simulator requires keyboard and pointer interaction that does not yet have a fully accessible alternative for motor-impaired users who rely solely on a switch device or voice-control. All textual aircraft specifications and non-simulator content remain fully accessible. Remediation target: Q3 2026.
- Route preview maps. Vector-based airport and route maps are currently visual-only. Equivalent text information (airports, distances, flight times) is provided immediately below each map. Remediation target: Q3 2026.
- Live mission board (/missions). The real-time mission board uses WebSocket data with dynamic DOM updates; ARIA live-region announcements are partial. Remediation target: Q4 2026.
5. Feedback and contact
We actively want to hear about accessibility barriers. If you encounter an issue:
- Email: accessibility@triforce.flights — monitored by our engineering team.
- Phone: 00 800 TRI FORCE — 24/7 mission control; ask to escalate to the technical team.
We aim to acknowledge accessibility feedback within 2 business days and to resolve the issue or communicate a remediation plan within 14 calendar days.
6. Formal complaints
If you are not satisfied with our response to an accessibility complaint, you may refer the matter to:
- United Kingdom: Equality and Human Rights Commission (EHRC) —
equalityhumanrights.com - European Union: the supervisory or equality authority in your member state.
- United States: U.S. Department of Justice, Civil Rights Division —
ada.gov - UAE / Saudi Arabia / Qatar: the relevant national digital-accessibility or consumer-protection authority in your jurisdiction.
7. Technical specifications
This website relies on the following technologies for its accessibility conformance:
- HTML5
- CSS3 (Tailwind v4 with logical properties and RTL utilities)
- JavaScript / TypeScript (ES2023)
- WAI-ARIA 1.2
- WebGL (flight simulator only — not on the critical navigation path)
8. Assessment approach
We assess accessibility through:
- Self-evaluation by the development team during code review, with accessibility criteria as merge-blocking requirements.
- Automated checks using
axe-coreand browser DevTools accessibility panels. - Manual keyboard-navigation testing on desktop (macOS, Windows) and mobile (iOS, Android).
- Screen-reader spot-testing with VoiceOver (macOS / iOS) and NVDA (Windows).
We intend to commission an independent third-party WCAG 2.1 AA audit before the service’s first major commercial launch.
9. Changes to this statement
We will update this statement as known limitations are resolved and as the independent audit is completed. Material changes will update the effective date above. The current version is always at /accessibility.
10. Contact
Accessibility enquiries: accessibility@triforce.flights
Triforce Mission Control — 00 800 TRI FORCE