24 questions, scored locally in your browser. No account, no email gate, nothing uploaded — answer honestly and you'll get a readiness score, a category breakdown, and the risks most likely to block an Arabic launch.
Prefer the full manual version? Use the RTL testing checklist.
Arabic routes set dir="rtl" and lang="ar" at the document level
Layout uses logical CSS properties instead of hardcoded left/right
Drawers, menus, steppers, and directional icons mirror correctly
An Arabic-appropriate font is loaded with tuned sizes and line-height
Product codes, emails, and brand names render intact inside Arabic text
Long Arabic labels don't overflow buttons, tabs, or badges
Phone, OTP, and email inputs stay LTR inside RTL forms
Validation messages appear in Arabic on the correct side
Signup/login flows were tested end-to-end in Arabic
Tables read correctly in RTL with a deliberate numeric-alignment rule
Charts, legends, and tooltips were reviewed for RTL
Exports (CSV/PDF) open readably for Arabic users
The full purchase/billing path was completed in Arabic on desktop and mobile
Address forms match the target market's structure (not street/ZIP order)
Currency display and totals are unambiguous in Arabic sentences
Navigation drawers and gestures behave correctly in RTL on real devices
Correct keyboards appear per field (Arabic text vs numeric phone/OTP)
No horizontal overflow at 320–375px in Arabic
Arabic pages have their own titles, descriptions, and canonicals
hreflang links only real equivalents, reciprocally
Locale routing has a clean URL strategy with no duplicate-content leaks
Emails render RTL in real clients (tested, not assumed)
Invoices/PDFs lay out RTL with correct column order
Push/SMS/WhatsApp templates keep variables in position in Arabic
