Arabic–English website QA for Egypt and Saudi Arabia
A practical acceptance checklist for mixed text, phone numbers, bookings, language routes and complete mobile journeys.
Test whether someone can finish the task
Complete an enquiry or booking on a phone in each language, deliberately make an error and recover. RTL styling is one requirement. The question, choices and confirmation must also make sense independently, and visitors must be able to review the information they submit.
A compact test set for a bilingual release
Combine an Arabic name, English email and Egyptian telephone number; repeat with a Saudi number. Try national and international phone formats and copying the confirmed value. Switch language from a service detail page and verify equivalent intent. Compare booking times in Cairo and Riyadh on different dates of the year. Test narrow screens with the keyboard open.
Discovery depends on real language pages
Give each language a crawlable URL, clear title and useful body content. Pair equivalent pages with language alternatives. Google’s multilingual guidance supports separate language URLs, while its generative-search guidance emphasizes useful content and sound technical foundations. Neither translated navigation alone nor special ‘AI SEO’ prose substitutes for a complete page.
Put acceptance into the scope
List the journeys that must pass, the devices you will actually inspect and the person responsible for Arabic writing and review. Verify keyboard focus, validation recovery and confirmation language. A screenshot or an automated audit is one piece of evidence, not acceptance of the complete experience.
Test a complete task
Choose a service, fill a form, recover from an error and read the confirmation using a keyboard and a narrow screen. Check wrapping, focus order, touch targets and the effect of an open mobile keyboard. Visual inspection matters, but a complete task reveals failures that a screenshot cannot.