Arabic Readiness Certification
An Arabic website audit that ends in a certificate
A pre-launch audit by people who read Arabic, ending in a certificate.
- Price
- $1.5K–$3K fixed fee
- Timeline
- 5–8 working days
- Starts with
- A free scan
your-site.example
Improved from 84 to 100 (+16)
Reviewed by hand, 25 pages
A record of a measurement on a date, with a re-verification date, because any deploy can change the result.
The scanner is deterministic, which is its strength and its limit: it finds what can be proven from the DOM and the rendered page. It cannot tell you that a translation is stilted, that a form asks for a surname in a culture that does not use one, or that your date format is technically correct and still reads as foreign. Certification is the pass where a person looks, with the scan as the starting map rather than the finding.
This is for you if
The situations this engagement was built for.
You are launching an Arabic version and want a second pair of eyes before customers see it
Your Arabic was translated by a vendor and nobody on the team can judge the result
A partner, investor or regulator is asking for evidence that the Arabic product is ready
You ran the free scan and want to know which findings actually matter
The review
Knowing which findings to ignore
A 35-issue scan sorts into three real defects worth a developer's afternoon, eleven instances of one CSS rule, and a long tail of low-confidence attribute findings that a reviewer strikes out in ten minutes. The value of the pass is not the count going down: it is knowing which of the 35 you can ignore.
A news site scoring 84. Each square is one finding from the free scan.
- 3Real defectsWorth a developer's afternoon. Fix these first.
- 11One CSS rule, eleven timesEleven findings, one stylesheet fix.
- 21Struck as noiseLow-confidence attribute findings, ruled out in minutes.
Illustrative: a news site at 84. Drawn from our own fixtures and public-site scans, not a client engagement.
Scope
What is in the engagement
What you get
- A full crawl of up to 25 pages, every issue reviewed by hand and annotated
- False positives struck out explicitly, so you can trust what remains
- The judgment calls a deterministic engine will not make: tone, terminology, cultural fit
- A one-hour findings call with whoever will do the fixing
- A dated certificate and an embeddable badge, issued on a clean re-scan
What we need from you
- The URL, and staging credentials if the Arabic version is not public yet
- Your brand and product terms, so we do not flag them as untranslated
- Who to talk to on the findings call
Process
How it runs
Timeline: 5–8 working days. Every step ends with something you can see.
Crawl and scan
We crawl up to 25 pages of the Arabic build, public or staging, and run every check at every breakpoint. That report is the map, not the verdict.
Review by hand
A reviewer who reads Arabic works through each finding: confirms it, strikes it as a false positive, or ranks it. Then looks for what no engine can: tone, terminology, forms that do not fit the culture.
Findings call
One hour with whoever will do the fixing. You leave with a short ranked list and the reasoning behind each item, not a spreadsheet of 400 rows.
Re-scan and certify
We scan again. A clean result, or one whose remaining findings you have accepted in writing, is issued as a dated public certificate with an embeddable badge.
Backed by the engine
The checks this engagement leans on
Every finding starts as one of these, with evidence attached. Each has its own page explaining when it fires and how to fix it. Browse every check.
- Document direction missing, contradicted, or declared only in CSSWhether
<html>says right-to-left and the page actually renders that way: a missing or overriddendirflips the whole layout for an Arabic reader. - Visible Latin-script body text above thresholds on an Arabic pageLatin-script passages left on an Arabic page, a single sentence or a large share of the whole page, tell the reader the translation stopped partway.
- Forced-LTR container, or a bidi override, over Arabic contentUnder a
dir="ltr"ordirection: ltrbox, mostly Arabic text starts at the wrong edge with punctuation out of order, and abidi-overridecan mirror its letters or reverse embedded numbers. - Unisolated bidi hazards: phones, emails, Latin tokens inside Arabic textIn right-to-left text a phone number like
+966 55 123 4567displays as4567 123 55 966+unless it is isolated in<bdi>, and figures with brackets or signs can flip the same way. - Letter-spacing applied to Arabic text (breaks the connected script)Arabic letters join along a baseline, so positive tracking breaks the joins and negative tracking overlaps the letterforms, typically from a Latin type scale never scoped away from Arabic.
- 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.
- Tel/email/url inputs rendered RTL (these must stay LTR)Phone, email and URL fields left right-to-left on an Arabic page: their values are left-to-right strings, so digit groups and punctuation can display out of order as users type.
- 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.
Get started
Scan first. Then we talk about your findings.
The scan takes about a minute and costs nothing. Your inquiry arrives with it attached, so the reply starts from evidence about your site rather than questions about it.
- Paste the URL of your Arabic page.
- See your score and top findings.
- Tell us what you need. A person replies within one working day.
Start with a scan
We would rather look before we talk. Give us the URL and we will run the same scan the homepage runs, then you can tell us what you need.
FAQ
Questions about the certification
The rest of the ladder
Other ways we can help
- 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
Find out where your Arabic stands
A free scan of one page, scored and explained in about a minute. If it tells you everything you needed, that is a good outcome too.
Start with a free scanAll services