Decision-first experience
Every page leads with clear decisions and dependencies before introducing new actions.
Draft for owner review
Accessibility is a build requirement, not an unverified badge.
Core journeys target WCAG 2.2 AA with English LTR and Arabic RTL, but no conformance claim will be made without current test evidence and an accessible feedback route.
A clearer homepage view
What this preview is optimized for
Each page keeps the family journey legible: what is available now, what is blocked, and what opens only after approved safeguards and policies.
Owner-controlled rollout
Operational gates remain active, so next features appear only after the matching readiness checks complete.
Protected learning relationship
Teacher access, child details, payments, and support paths stay constrained to approved roles and workflows.
Guardrails activeTransparent milestones
Every section ends with an explicit state label and a clear next action, so families can orient without guessing.
Decision state, no guessingHomepage upgrade highlights
What this version improves on every page
The updated preview adds clearer guidance, stronger visual rhythm, and explicit blocked states so users know what is possible now.
Single language and direction rhythm
English and Arabic flows follow the same structure and interaction rules, including direction-aware spacing and icon behavior.
Stronger page transitions
Sections reveal with predictable animation timing and consistent spacing so each step feels complete.
Decision-first marketing
Feature descriptions focus on what is available now and what is locked behind approvals.
Operational transparency
Every public and portal route shows explicit status, scope, and next-step guidance.
Move forward with confidence
What this page unlocks next
Each section points to one next step. These options reflect current public capabilities before enrollment and billing become active.
Review the next-step policy
Open the related page to confirm launch gates, roles, and what remains gated.
Open launch guardrailsUnderstand your path
Check the journey, progress evidence, and what a family should expect before scheduling starts.
Read how it worksStart with a safe assessment
Continue from this page into the planned assessment flow and preparation notes.
Assessment informationUse this page without confusion
3 quick checks before you move to the next section
Each route follows the same safe reading pattern: what matters now, what is waiting on approvals, and where to continue after the next verified gate.
Current status
See at a glance what is currently open, closed, or still waiting for policy and approval.
Read then act
The primary actions are available only where your journey can continue safely and audibly.
Keep momentum
Small steps and explicit labels help families and operators move only when the required conditions are met.
Accessibility is a build requirement, not an unverified badge.
Core interaction standard
Keyboard access, visible focus, semantic landmarks, labels, announced errors, contrast, reduced motion, touch targets, 200% zoom, and 360-pixel reflow are release requirements.
Both languages and directions
Arabic and English are tested as first-class experiences, including mixed-script names, numbers, dates, currencies, time zones, directional icons, and expanded text.
Evidence and feedback before claim
Automated checks must be supplemented by keyboard and selected screen-reader review. A named response route and remediation process are required before publication as an effective statement.
How this page moves forward
What happens after this section
These public checkpoints are shared language for planning and review before the next launch phase.
Decision clarity
Public copy remains decision-oriented until safeguards, policy scope, and owner approvals are complete.
Capability confirmation
Only approved capabilities and authorized relations can open the next operational step.
Reliability by design
Fallback, denied, and retry-safe paths stay visible for both families and operators.
Release readiness
The next layer opens after deployment and review evidence passes the current release checks.