What shapes design work for the UAE
No single user type dominates in the UAE. A design that works there has usually been simplified until it works for almost anyone.
| Topic | What it means for your product | Decide early |
|---|---|---|
| A population from everywhere | Most residents come from abroad, and many read English as a second or third language. Idiom, dense text and culturally specific icons cause errors | A reading level for interface text, and how it will be tested |
| Arabic alongside English | Arabic is the official language, and government-facing and citizen-facing content needs it at full quality. Commercial products vary in which language leads | Which language is primary for your audience, and who owns the other |
| The federal design system | The telecommunications and digital government regulator has published a design system for federal government websites. Its guidance follows WCAG 2.1 and asks federal entities to meet level AA | Whether your project falls under it, confirmed with the buyer |
| Accessibility beyond government | Banks, airlines, retailers and property firms serve the same varied public. Meeting a recognized accessibility level widens the audience and is increasingly asked for in tenders | The level you commit to, and how it will be evidenced |
| Premium expectations | Hospitality, retail and property in the UAE compete on presentation. Interfaces are expected to feel polished, and still to load quickly | Where visual richness matters, and where speed matters more |
| Identity and payment conventions | Users know the national digital identity app and wallet checkout. Products that use them should match what users see elsewhere | Which of these appear in your journeys |
| Different rules by zone | Data protection rules differ between the federal law and the financial free zones. Consent screens may need to vary accordingly | Which regime applies, stated by your legal adviser |
Design work we do for UAE products
Four engagements, each with a defined output.
Product design for a mixed audience
For consumer and business products used across the country.
- Research with users from several language backgrounds
- Journeys simplified and agreed
- Interface designed in English and Arabic
- Wording tested for comprehension
- Prototype tested on phones
- Specification handed over
Accessibility audit and remediation
For organizations asked to show conformance.
- Key journeys tested against WCAG 2.1 AA
- Tested with a keyboard and a screen reader
- Issues ranked by impact
- Components corrected in design
- Findings and fixes documented for developers
Design to the federal system
For suppliers building federal government websites.
- Scope and system version confirmed with the entity
- Pages composed from system components
- Accessibility checked as pages are built
- Arabic and English reviewed
- Exceptions recorded and approved
Premium brand experience
For hospitality, retail and property brands.
- Brand and audience studied
- Signature moments defined
- Visual direction explored
- Key pages designed with a performance budget
- Motion and interaction specified
What we design
Research across audiences
Sessions with users of different backgrounds, to find wording and steps that everyone gets through.
English and Arabic interfaces
Both languages designed properly, with the lead language chosen from evidence about your users.
Accessible components
Contrast, focus, target size, labels and error handling specified to WCAG 2.1 AA and tested with assistive technology.
Plain-language content design
Interface text rewritten to be short, literal and translatable.
Design systems
Libraries that carry accessibility and both directions in every component. See our comparison of a design system and a UI kit.
Audit reports and handover
Ranked findings, corrected designs and specifications that developers can act on.
What we need from you
- The product and a description of who uses it
- Any accessibility or design system requirement from a buyer
- Analytics on language, device and where users leave
- Brand guidelines and existing design files
- Reviewers for English and for Arabic content
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for a design project in the UAE
Before design starts
0 of 8 checkedWhat to do next
Tell us about the product, its users and any standard a buyer has asked you to meet. We will reply with the engagement we would suggest and how we would test with a mixed audience. Start a conversation or book a 30-minute call.
For a wider view of what a review covers, see our guide on what a UX audit should deliver.
Common questions
Is accessibility a legal requirement for private companies in the UAE?
We have not found a general rule that names a conformance level for private websites, and you should confirm the position with a legal adviser. The published requirement we know of is in the federal design system, which asks federal government entities for WCAG 2.1 at level AA. Private companies adopt the same level because buyers ask for it and because it serves more customers.
Which language should lead, English or Arabic?
It depends on who uses the product. For services aimed at citizens and for government work, Arabic leads or stands equal. For products serving the general resident population, English often leads, with Arabic fully supported. Your own analytics on language settings is the best evidence. Whichever leads, the other must not be a reduced version.
How do you design for users who are not fluent in either language?
By removing reliance on reading. Short sentences, common words, one action per screen, clear icons paired with labels, examples inside form fields and progress that is visible. We test wording with people from several backgrounds and watch where they hesitate. Simple interfaces also translate better and suit fluent readers in a hurry.
We supply a federal entity. What will they expect from design?
Normally that pages are built from the federal design system's components, meet its accessibility guidance and work in Arabic and English. Ask your contact which version applies and how exceptions are approved. We design inside the system, test accessibility as we go and document every departure, so that approval is straightforward.
Where to go from here
Related serviceUI/UX DesignInterface design that engineers can actually build