Ran the RTL migration? Scan it.
Setting dir and swapping margins for logical properties fixes the layout. It does not fix bidirectional text, numerals, Arabic fonts, inputs or the strings nobody translated. One free scan shows what the migration left behind.
Done by the migration
dir="rtl"on the page- Logical properties
- Mirrored layout
Left for the scan
- Text that reorders
- Arabic type
- Inputs and icons
- Untranslated strings
- Arabic that does not fit
A flip fixes the layout. Arabic needs more.
The migration's checklist ends where these begin. Each is a check the scan runs on the rendered page.
Text that reorders
Phone numbers, emails, prices and dates move around inside an Arabic sentence unless each one is isolated, and two numeral systems in one view read as a mistake.
Arabic type
A font with no Arabic falls back silently, and letter-spacing or a synthesised italic breaks a connected script that was never meant to stretch or slant.
Inputs and icons
Name fields that type left to right, phone fields that flipped when they should not, and arrows that still point the English way.
Strings nobody translated
Button labels, menus and the long tail of body copy that stayed English on a page that is otherwise Arabic.
Arabic that does not fit
Arabic runs longer and needs taller lines, so boxes sized for English clip it, and small detail text below 14px stops being legible.
The migration's own work, confirmed
The scan also checks what the migration was for, so a passing report is evidence rather than assumption.
One page, about a minute, no account
- 1
Give it a URL
Any Arabic page the public can reach. The scan reads the rendered page the way a visitor's browser does.
- 2
Read the report
A score, and for each finding a screenshot, the selector and the change that fixes it.
- 3
Fix and re-scan
The next scan says what was fixed, what is new and what did not move.
Questions after a migration
We converted our CSS with a tool. Is that enough?
It is the part a tool can do: direction-sensitive properties. It does not see text order, fonts, inputs or translation, which only show up on the rendered page. That is what the scan checks.
Does the scan need our code?
No. It reads the page at a URL, like a visitor, at desktop, tablet and phone widths.
What if we want help fixing what it finds?
Every finding says what to change. If you would rather hand it over, the RTL conversion service takes a site from its measured score to a clean one, and the scan is the receipt.
See what the migration left behind
Scan the Arabic page that matters most. It is free and takes about a minute.