Loading
Products that work in Arabic and in French or English, with real right-to-left layout rather than a mirrored afterthought.
Most teams discover too late that right-to-left is not a CSS flip. Logical properties, bidirectional text, mixed Latin and Arabic runs, date and number formats, form validation, PDF and email output: each one breaks differently. We build products that ship in both directions from the first commit, and we have done it on an EPC group site with full RTL and LTR switching across every component, and on this site, which runs three locales including Arabic.
What already breaks in Arabic: layout, typography, inputs, exports.
Physical left and right give way to start and end, once, across the codebase.
Routing, metadata, hreflang and fonts per locale, not a language toggle over one layout.
Every screen reviewed in Arabic before launch, because that is where the errors are visible.
Usually yes. The work is proportional to how much of the layout uses physical left and right instead of logical start and end, which the audit measures in the first days.
Arabic and French are native languages here, so we can write and review interface copy directly. Long-form or legal translation is worth a specialist, and we will say so.
No. Done with logical properties it is the same stylesheet, and the Arabic font is the only extra weight, loaded only for that locale.
Teams selling into Saudi Arabia, the UAE, Qatar and North Africa, and French or European products that need a credible Arabic version rather than a machine-translated one.
Tell us what you are working on. Reply within 24 hours, one-page diagnostic within 48.