Build an Arabic and English experience people can use

Arabic needs right-to-left reading order, while phone numbers, email addresses and some technical values need isolated left-to-right presentation. Review icons, breadcrumbs and form alignment in both languages. Preserve meaning throughout the journey rather than translating individual labels without checking how their context and order change.

Give fields visible labels and explain expected formats. Place errors near the relevant input and preserve valid entries when one value fails. Use appropriate autocomplete and show a clear submission result. Test long names, mixed-language text and phone numbers in the formats your customers actually use.

Navigate by keyboard and check visible focus, logical order and usable dialogs. Review contrast, text resizing and meaningful image alternatives. Icon-only controls need accessible names. Respect reduced motion preferences and keep content available when decorative animation is disabled. These checks let more people complete tasks using different devices and assistive tools.

Ask people to find a service, compare options and send an inquiry without coaching. Record hesitation and failed actions, then improve the flow. Test small screens with longer translated text. A polished prototype is a starting point; successful task completion provides better evidence that the design actually works.

Ask an Arabic-speaking user and an English-speaking user to find the same service and send the same type of inquiry. Observe whether instructions, error messages and the confirmation preserve the same meaning.

Check mixed-direction values such as a phone number inside an Arabic sentence. Layout mirroring should help reading without reversing the digits, breaking an email address or changing a technical identifier.

• Complete the main task with a keyboard.
• Check visible focus and a logical tab order.
• Verify field labels and useful error explanations.
• Resize text and inspect content on narrow screens.
• Review contrast and alternatives for meaningful images.
• Respect reduced motion preferences.

Use these as working checks, not a declaration of full conformance. Formal accessibility assessment requires an appropriate scope and a documented evaluation.

Separate what participants struggled to do from what they merely liked or disliked. A small font that prevents reading deserves a different priority from a preference for another shade of blue.

Describe the issue, the affected audience and a proposed change, then repeat the task after revision. Keep both language versions in the review so improving one does not quietly break the other.