Techbanq

Web · Arabic parity

The Arabic site was finished last, and every visitor can tell

Truncated labels, a stray left-aligned form, an Arabic page still announcing last year’s offer — small tells, and your Arabic-reading majority reads all of them the same way: this organisation speaks to me second. The defect is not in the translation. It is in the workflow that always produces Arabic last.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

High-rise towers in the Riyadh business district at dusk

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The tells

Small defects, one message: the signals an afterthought Arabic site sends

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

The symptoms are recognisable anywhere in the Gulf. A menu label cut short because the Arabic phrase outgrew a box sized for English. A date, a price or a phone number rendering left-to-right in the middle of an Arabic sentence. A news section whose English side updated last week and whose Arabic side stopped months ago. A form that flips its layout but not its logic, so the fields read right-to-left and the error messages arrive in English. Each defect is minor; the pattern is not, because the pattern is legible.

What it tells the visitor is that the organisation composed its message in English and had it converted. For a business whose customers, regulators and staff mostly read Arabic, that is a strange thing to keep broadcasting — and no amount of spot-fixing changes the broadcast, because the next release reproduces it. The defects are the exhaust of a process. It is the process that needs the repair.

The mechanism

How a bolt-on translation step keeps regenerating a second-class Arabic site

Follow one piece of content through the usual pipeline and the symptoms stop being mysterious. Every stage is reasonable; the sum is a site that is always behind in one language.

A pipeline — written in English, designed left-to-right, sent for translation, squeezed into finished layouts, published late — with a branch showing the parity model: one workflow producing Arabic and English as equal outputs.

  1. 01

    Written and approved in English

    The argument, the tone and the emphasis are all settled in one language, for one kind of reader.

  2. 02

    Designed left-to-right

    Layouts, boxes and buttons are sized for English strings; Arabic will have to fit whatever remains.

  3. 03

    Sent out for translation

    A vendor converts sentences without the context, the audience or the authority to reorder the argument.

  4. 04

    Squeezed into finished layouts

    The Arabic text meets components that were never tested with it — and the truncations and leaks are born here.

  5. 05

    Published late, then left

    The Arabic page goes live days or weeks after the English one — and the next English edit restarts the whole loop without it.

Always available

The parity model

One workflow, two first-class outputs: content is briefed once, authored for each language by people with authority over both, laid out in components tested in both directions, and a change publishes when both languages are ready. Lateness becomes structurally impossible rather than personally discouraged.

The design debt

What a mirrored-after interface still owes its Arabic readers

Even with the workflow repaired, the front end carries debts from every year it was built English-first. These are the usual accounts to settle.

01

Type set to Latin metrics

Arabic script needs its own sizes, line heights and typeface choices to read comfortably at interface sizes; inheriting the Latin settings leaves it cramped, small and visibly borrowed.

02

Direction patched, not tokenised

Hard-coded left and right values mean every new component ships broken in Arabic until someone notices. Direction-aware logical properties fix the class of bug instead of each instance.

03

Forms that fight mixed input

Names in Arabic, emails in Latin, numbers in either — a real Saudi form is mixed-direction by nature, and fields that were never tested that way lose enquiries silently.

04

Layouts that assume English lengths

Arabic phrases run longer or shorter than their English counterparts unpredictably; boxes, buttons and navigation sized to one language truncate or float awkwardly in the other.

Our role

Repairing the operation that produces the pages, then the pages themselves

  1. 01

    The parity review

    A concrete accounting of where the Arabic experience trails — stale pages, missing pages, layout defects, workflow lag — so the repair is scoped on evidence rather than embarrassment.

  2. 02

    The workflow, rebuilt

    We redesign the content operation with your teams so Arabic and English are two required outputs of one process, and wire the rule into the publishing tools — a page ships when both languages ship.

  3. 03

    The front-end debt, settled

    Typography, direction handling and mixed-direction forms are repaired as a class in the component layer, so the next feature ships correct in Arabic on the day it ships at all.

Where the parity review finds the structure itself was built English-first beyond economical repair, the honest next step is an Arabic-first rebuild — a separate engagement, scoped by our Arabic website development service — and we will say so rather than sell you patches.

Common questions

What buyers ask

Why does our Arabic content keep going stale when we pay for every translation?+

Because payment buys the conversion, not the parity. In a bolt-on workflow, every English edit creates Arabic work that sits in a queue: someone must notice the change, brief the vendor, wait for the text, place it and publish it — five small delays that recur on every update, forever. Miss any step once and the two versions fork. The repair is not a better vendor; it is a workflow in which a change cannot be published in one language alone. When the publish action itself requires both languages, staleness stops being a discipline problem and becomes structurally impossible.

Is fixing the Arabic side of the site a translation project or an engineering one?+

Neither alone, which is why it keeps failing when bought as either. Retranslating everything produces better sentences inside the same broken layouts, on the same lagging schedule — visibly improved for a quarter, then back where it was. Fixing only the front end produces components that handle Arabic beautifully and receive it late. The durable repair has three parts: the workflow, so both languages publish together; the component layer, so right-to-left behaviour is correct by construction; and then the content, written rather than converted where it matters most. The order matters — content poured into an unrepaired system drains away again.

Do we need separate teams to run the Arabic and English sites properly?+

No — separate teams usually make the problem worse, because two teams with two backlogs drift exactly the way two sites do. What parity needs is one team whose definition of done includes both languages: a content operation with Arabic editorial capability inside it, not downstream of it, and publishing tools that treat the two versions as one unit of work. The Arabic capability can be in-house or ours; where it sits organisationally matters less than where it sits in the process. Inside the workflow, parity is routine. After the workflow, it is a permanent apology.

A parity review that shows exactly where and why your Arabic experience trails the English one, and what changing the workflow — not just the words — would take.

Review your Arabic parity