Interface text is part of the design. Clear words help people finish a task without help, in either language. This page covers English and Arabic. Write each language for its own readers: an Arabic screen should read as if it was written in Arabic first, not translated word for word.
Change the tone to suit the moment. A confirmation can be warm ("Your request has been sent"). An error stays neutral and practical. A destructive action is direct about the result ("This deletes the file for everyone").
A good error message says what went wrong and how to fix it, in plain words, next to the field it belongs to.
| Write | Avoid |
|---|---|
| Enter a national ID with 10 digits | Invalid input |
| The file is larger than 10 MB. Choose a smaller file. | Upload failed: error 413 |
| We couldn't save your changes. Check your connection and try again. | Something went wrong! |
| Choose an end date after the start date | You entered the wrong date |
Use these terms in both languages. Arabic terms follow the names used on this site.
| English | Arabic |
|---|---|
| Sign in / Sign out | تسجيل الدخول / تسجيل الخروج |
| Submit | إرسال |
| Save | حفظ |
| Cancel | إلغاء |
| Delete | حذف |
| Edit | تعديل |
| Search | بحث |
| Filter | تصفية |
| Upload | رفع |
| Download | تنزيل |
| Request | طلب |
| Required / Optional | مطلوب / اختياري |
| Settings | الإعدادات |
| Notifications | الإشعارات |
| Error / Warning / Success | خطأ / تحذير / نجاح |
Read your text aloud before you ship it. If it sounds like a form letter or a machine translation, rewrite it.
Labels and buttons use sentence case and start with a verb.
Error messages say what went wrong and how to fix it.
Terms match the terminology table in both languages.
Numbers, dates and currency use one consistent format.
The Arabic text was written or reviewed by a native writer.
Text still fits when it is 30% longer.
