Key takeaways
- Design and build RTL from the start; retrofitting is expensive.
- Handle bidirectional text, numerals and Hijri dates deliberately.
- Normalise Arabic for search, and test PDFs and exports with real Arabic content.
Mirror the layout, not just the text
In right-to-left interfaces, navigation, progress indicators, sliders and most icons flip. Using logical CSS properties such as margin-inline-start instead of margin-left lets one stylesheet serve both directions. Some icons, such as clocks and media controls, should not be mirrored.
Bidirectional text and numbers
Arabic text often contains Latin brand names, phone numbers and IDs. Isolate these runs so punctuation and numbers do not jump around, and decide deliberately whether to display Western or Arabic-Indic digits, then apply it consistently.
Hijri dates
Many Saudi processes use the Umm al-Qura Hijri calendar alongside Gregorian dates. Store dates in a single canonical form, convert for display, and let users enter and read both. Remember that Hijri months move through the Gregorian year, which matters for seasonal planning.
Search, sorting and forms
- Normalise variants such as different forms of alef and ya, and ignore diacritics when searching
- Use locale-aware sorting for Arabic names
- Accept both Arabic and English input in name and address fields
Documents and exports
PDF and Excel exports are where Arabic support often breaks: disconnected letters, reversed words or missing fonts. Test every generated document with real Arabic content, and review the interface with native speakers before launch.
This article is general information, not legal advice. Please confirm current requirements with the relevant authority.
Want this for your organisation?
Talk to our team about Enterprise Digital Solutions.