- Market
- Saudi Arabia
- Written for
- Head of Digital, CTO, Head of CX
- Decision
- Learn how to design and verify an Arabic-first web experience
The working rules
Direction, type, numerals, navigation — each rule with its own check
A design rule you cannot test is a preference. These four are testable, and together they cover most of what separates an Arabic-first build from a flipped English one.
Direction and layout
Express layout in logical terms — start and end, not left and right — so the whole interface derives its direction from the document rather than from a per-component patch.
How to check it: Search the stylesheet for hard-coded left/right positioning; every hit is a place the Arabic layout will break under change.
Type scale and line height
Arabic script reads smaller than Latin at the same nominal size and its letterforms need more vertical room — so the Arabic scale is set on Arabic text, typically a step larger with looser leading, never inherited from the English tokens.
How to check it: Put a real Arabic paragraph beside its English counterpart at final sizes and read both at arm’s length on a phone; strained or clipped Arabic fails the check.
Numerals, dates and units
Choose one numeral style per audience and apply it everywhere — prices, dates, phone numbers — with calendar and formatting decisions written down, not left to whichever library renders the component.
How to check it: Walk one journey end to end and list every numeral and date encountered; any screen switching styles mid-journey fails.
Bilingual navigation
The language switch is reachable from every page, keeps the visitor on the equivalent page rather than dumping them on a homepage, and labels itself in the target language — «العربية», not “Arabic”.
How to check it: From five deep pages, switch language and note where you land; any landing that is not the same page in the other language fails.
The core idea
Right-to-left is a reading order, and only some things obey it
The mental model that produces good RTL work is simple: direction follows meaning. Anything that encodes sequence or flow follows the reading order — text alignment, the order of columns, breadcrumbs, carousels, a progress bar filling toward completion, a back arrow pointing to where the reader came from. Anything whose meaning is independent of reading order does not flip: media controls stay as they are because play and fast-forward are physical conventions, clocks and logos keep their form, phone numbers and code snippets remain left-to-right because that is how they are read, and a chart’s time axis is a modelling decision, not a mirroring one.
This is why the automated mirror is both necessary and insufficient. It gets the first category roughly right and the second category confidently wrong — flipped media icons, reversed phone numbers, question marks pointing the wrong way inside mixed text. The craft is in the exceptions list, and the exceptions list is why an Arabic reader has to see the interface before its users do: the categories above resolve most cases, but a real product always contains a handful of components where the right answer needs judgement, and judgement needs someone who reads the direction natively.
The recurring failures
The defects every Arabic build meets, and the fixture that exposes each
These four account for most of the bugs filed against Arabic interfaces. Each has a test fixture — a deliberately hostile piece of content — that surfaces it before a user does.
- 01
Truncation tuned to English lengths
Buttons, cards and menu items sized to English labels clip their Arabic counterparts, which often run longer and cannot always break where the design assumed. The fixture: your longest real Arabic strings in every component, at the smallest supported viewport.
- 02
Mixed-direction lines that scramble
An Arabic sentence holding an English brand name, a model number and a price is the ordinary case in this market, and naive text handling reorders it into nonsense. The fixture: a paragraph mixing Arabic, Latin brand names, digits and punctuation, checked character by character against how it should read.
- 03
Fonts that fall back and fake it
A missing Arabic weight makes the browser synthesise bold by smearing the letterforms, and a wrong fallback stack renders headings in a system font nobody chose. The fixture: every heading level and weight rendered in Arabic on a cold cache, compared against the specified typeface.
- 04
Forms that fight the writing hand
Input fields that force one direction garble whichever language the user actually types — an email address in an RTL field, an Arabic name in an LTR one — and misplace carets and placeholders. The fixture: every form filled twice, once in Arabic and once with mixed content, watching alignment, caret and validation messages.
The verification
A four-pass test plan that catches Arabic defects before release
The passes run in this order because each is cheaper than the one after it, and a defect caught early never reaches the pass where it costs more.
Build the hostile fixture set
Collect the content that breaks Arabic builds — longest real strings, mixed-direction sentences, every numeral and date format, names with Latin characters — into fixtures the team reuses on every feature. A fixture set that makes Arabic testing repeatable instead of heroic.
Automate the mechanical checks
Hard-coded directional styles, missing direction attributes, untranslated strings and absent Arabic font weights are all detectable by machine — wire them into the build so they fail a release, not a review. A build that refuses the defect classes machines can see.
Run the visual pass on real devices
Walk the key journeys in Arabic on the phones your audience actually holds, fixtures loaded, checking layout, truncation, type rendering and the components on the exceptions list from the direction rules. The defects that only render on glass, found on glass.
Put an Arabic reader on the release gate
A native reader reviews copy, tone and the judgement calls no automation reaches — and their sign-off is required for the release, which is the single practice that most reliably keeps an Arabic experience first-class. A release gate that speaks the audience’s language.
Our role
Where this guide ends and a reviewed Arabic build begins
- 01
The review against the checks
We run an existing site or product through the rules and fixtures above and return the defect list with severity and fix — a bounded piece of work whose output is useful whoever does the fixing.
- 02
The Arabic-first build itself
Where the honest verdict is that patching will not get there, we design and build Arabic-first — layout proven right-to-left before its mirror, native copy, the type scale set on Arabic text — with the English experience derived from it.
- 03
The discipline handed over
The fixture set, the automated checks and the release-gate practice are left running in your pipeline, so the Arabic experience stays first-class after we leave rather than for one launch.
The voice of your Arabic copy and the audience it addresses stay editorial decisions your team owns; we build and verify the engineering that lets that voice arrive on screen exactly as it was written.
Common questions
What buyers ask
Which parts of an interface should not flip when the layout goes right-to-left?+
Everything whose meaning does not come from reading order. Media controls keep their shape — play, pause and fast-forward are physical conventions, not linguistic ones. Phone numbers, email addresses, URLs and code stay left-to-right because that is how they are read everywhere. Logos and wordmarks keep their designed form. Clocks stay clockwise. Charts deserve a deliberate decision rather than a reflex: a time axis may read right-to-left for an Arabic audience, but only if the whole chart, its labels and its tooltips are designed for it — a half-mirrored chart is worse than an unmirrored one. Everything that does encode sequence — text, columns, breadcrumbs, progress, back arrows — follows the reading order. Keeping the two lists explicit in your design system is what stops each new component reopening the debate.
Does Arabic text need different type sizes and line heights from English?+
Yes, and inheriting the English tokens is one of the quietest ways an Arabic site ends up feeling second-class. At the same nominal pixel size, Arabic script tends to read smaller — its visual body sits differently in the em box — so body text usually needs a step up to feel equal. Its ascenders, descenders and diacritics also need more vertical room, so line height set for Latin text feels cramped and can clip marks. The practical approach is to define the Arabic scale as its own set of design tokens, tuned on real Arabic paragraphs in the actual typeface at final sizes, rather than as a percentage adjustment applied blindly. And test the weights: not every Arabic typeface ships the full range, and a browser asked for a missing weight will synthesise it badly.
How do we test Arabic layouts when nobody on the team reads Arabic?+
You can get surprisingly far, and then you hit a wall that only a reader crosses. Without Arabic, the team can still catch most structural defects: the fixture set exposes truncation and overflow whatever the tester reads; automated checks find hard-coded directions, missing attributes and absent font weights; and a pseudo-localisation pass — long strings, mixed-direction content — breaks fragile components on demand. What no non-reader can verify is whether mixed-direction sentences read correctly, whether the copy sounds like it was written rather than converted, and whether the judgement-call components resolved the right way. So budget for an Arabic reader at two points: reviewing the fixtures’ expected renderings once, and signing off releases. That is hours of a person’s time per release, and it is the difference between a site that passes its own tests and one that reads properly to its audience.
In this cluster
Have your Arabic build reviewed
A review of your Arabic experience against this guide’s checks, returning the specific direction, typography and truncation defects with the fix for each.
Start the conversation
