Accessibility & bilingual standards
The bar is WCAG 2.2 AA, which also aligns with UAE government digital accessibility expectations, and full Arabic readiness even if launch is English-first.
| Area | Standard |
|---|---|
| Contrast | 4.5:1 minimum for text, 3:1 for large text and UI parts. The pairs in the Colour section are pre-verified; do not invent new ones. |
| Keyboard | Everything operable by keyboard; visible 2px orange focus ring on both surfaces; skip-to-content link on every page. |
| Touch | 44px minimum targets; primary actions reachable one-handed on mobile. |
| Structure | One h1 per page, landmarks (header, nav, main, footer), alt text on all meaningful images, labels tied to every input. |
| Motion | prefers-reduced-motion removes reveals, lattice animation and hero sequences. |
| Performance | LCP under 2.0s on mid-range mobile, CLS under 0.05, total page weight under 1 MB before imagery. Fast is part of trust. |
Arabic & RTL rules
| Rule | Detail |
|---|---|
| Typeface | IBM Plex Sans Arabic for all Arabic text, weights 400/500/700 matching the Latin roles. |
| Sizing | Arabic runs ~10% larger than the Latin equivalent with line height 1.8 minimum; no letterspacing, ever. |
| Direction | Full layout mirroring with CSS logical properties (padding-inline, margin-inline, inset-inline) from day one. The triangle cue flips to point left in RTL. |
| What doesn’t flip | The logo, numerals in data, and media playback controls. |
| Numerals | Western Arabic numerals (0-9) in both languages for data consistency. |
| Tone | Formal register (fusha) for corporate copy; have a native speaker review all Arabic before publication. |