A commerce team shipping an Arabic storefront
Find the Arabic defects that cost your storefront sales
Checkout, price formatting and product copy are where Arabic breaks in ways that cost money rather than looking wrong. These are the checks that catch them, and the one case where an automated scan cannot reach you at all.
- Delivery
- Automated scan
- Measured at
- three breakpoints
- To try it
- Free, one page
Size guide · Free returns within 30 days · Ships in 2 to 4 days
- The steps run left to right, against the page
- A US dollar price on a riyal storefront
- Arabic-Indic and Western digits in one item
- Shipping terms left in English
- The pay button clips its own label
The problem
What breaks
With the mechanism, not a category, and the check that catches each one.
A checkout that mirrors everything except the part that matters
A form flips cleanly and the card field keeps its left-to-right numerals, which is correct. What does not flip is the step indicator built from physical margins, so the progress bar runs backwards against the flow of the page. Nobody reports it; they abandon.
The product
What it does about that, today
Automated scan, every page it can reach
Deterministic checks with the evidence attached: a screenshot, the selector, and the change that fixes it. Run at three breakpoints, because a defect that appears at one width is a defect at that width.
Scheduled scans, and an email when a release breaks something
A storefront changes weekly. Monitoring re-scans on a cadence and mails the owner when the score drops or a new critical appears, so a regression is caught by the scan rather than by a customer.
A report you can send to whoever has to approve the fix
An expiring link to the findings, with what was measured stated on it. The person who signs off on the work is rarely the person with the account.
Bot protection will sometimes stop us at the door
Commerce sites are the most likely to sit behind a bot check, and a bot check does its job: it refuses an automated browser, including ours. When that happens the scan says so instead of scoring a challenge page, and the failure routes you to a human audit. A score of a page we never rendered would be worse than no score.
One page, no account. If bot protection stops it, the result says so and offers the audit instead.
Deciding between approaches first? Compare the four.
Backed by the engine
The checks that matter most here
Each has its own page: when it fires, what it ignores and how to fix it. Browse every check.
- Foreign currency formatting in a SAR/AED market contextOn a Saudi or Emirati page, a dollar, euro or pound price on a button, card or table cell reads as the wrong market; amounts quoted within longer prose are skipped.
- Arabic-Indic and Western digits mixed in the same contextMixing ٣ and 3 within one table, list or
fieldsetmakes figures hard to compare at a glance; numbers in running prose outside those containers are not checked. - English month/day names or MM/DD/YYYY dates in Arabic textA date left in English or in American order breaks the localization of Arabic copy; only slash dates that are provably month-first count, so the regional 15/03/2026 passes.
- Direction-sensitive physical properties without an RTL overrideWhere the stylesheet shows signs of being written left-to-right first,
margin-left,padding-rightorleftleave Arabic spacing and offsets on the wrong side; otherwise it is reported as a lower-confidence risk. - Directional icon pointing against the sequence its control advancesOn a right-to-left page "next" runs leftward, so an arrow named
arrow-rightinside a next button, left unmirrored, tells an Arabic reader it goes back instead of forward. - Clipped text: content wider than its box with overflow hidden and no ellipsisArabic often runs wider than the English a box was sized for, so
overflow: hiddencuts words off; text with an ellipsis is still flagged, at low severity, to review the cut. - Untranslated form labels / validation / help textEnglish left in labels, hints and any visible error text inside a form on an Arabic page; a reader who cannot understand a field or its error cannot complete the form.
- Identity fields missing autocomplete tokensName, email, phone and address inputs, recognised by their name, id or label in English or Arabic, that lack
autocomplete, so Arabic users retype details the browser could fill.
FAQ
Questions buyers ask
When a scan is not enough
People behind the engine
A person reviewing, fixing or watching your Arabic, each engagement scoped from a scan.
- We look
Arabic Readiness Certification
A pre-launch audit by people who read Arabic, ending in a certificate.See the engagement - We fix
RTL conversion
We take the product from its measured score to a clean one, and the scan is the receipt.See the engagement - We look
Arabic Typography & Font Audit
The layer that decides whether Arabic looks native or merely present.See the engagement - We watch
Localization QA Retainer
For teams shipping continuously without an Arabic speaker on staff.See the engagement - We rebuild
Ritla UI rollout
We replace the components that keep breaking in Arabic with Ritla components, so the fixes stay fixed.See the engagement - We design
Custom theme
Your brand as a Ritla theme: a Figma file and code on the same tokens, Arabic-first.See the engagement - You deliver
Agency partners
Resell certification and conversion under your own brand.See the engagement
See what your Arabic pages look like to the engine
One page, about a minute, no account. The result says what it measured and what it could not.
Run a free scanCompare approaches