Best website design examples, and what they get right for Dubai and UAE businesses
What well known sites such as GOV.UK, u.ae, RTA, Apple and Stripe get right, and how to turn those qualities into a brief.
Read the articleWeb Services
A practical guide to white space for Dubai and UAE websites: W3C reading rules, spacing scales, room around forms, Arabic pages, touch targets and the stakeholder who says a page looks empty.

White space web design is the deliberate use of empty space between and around elements so that a page is easier to read, scan and act on. It sells because it controls attention: the fewer things competing in one view, the more clearly the important one stands out. For a Dubai or UAE business site, good spacing is not a style preference but a set of measurable decisions about line length, line height, gaps and touch targets.
This guide stays practical, with every standard quoted as of October 2026.
Key points
Designers talk about two scales of space, and most problems on business websites come from treating them as one.
Macro white space is the large space: margins around the page, the gap between a hero and the section below it, the band of nothing that tells a reader one topic has ended and another has begun. Good web design treats macro white space as structure, not decoration: with it a homepage reads as calm, without it as a noticeboard.
Micro white space is the small space: line height, paragraph spacing, letter spacing, the padding inside a button, the distance between a form label and its field. Readers rarely notice good micro spacing, but they notice its absence quickly, usually by giving up.
The useful habit in white space web design is to decide the two separately. Set the reading rhythm first, because body text appears on every page, then decide how much room each section needs.
Most spacing advice is opinion. Two WCAG success criteria are not.
Success Criterion 1.4.12, Text Spacing, is Level AA. It says there must be no loss of content or functionality when a user sets line height to at least 1.5 times the font size, spacing after paragraphs to at least 2 times the font size, letter spacing to 0.12 times and word spacing to 0.16 times. It does not require those values as your defaults; it requires your layout to survive them. Fixed height boxes, buttons with text clipped at a set height and cards that overlap when text grows all fail it.
Success Criterion 1.4.8, Visual Presentation, is Level AAA, but its spacing parts make excellent design targets. It asks for a width of no more than 80 characters or glyphs (40 for Chinese, Japanese and Korean), line spacing of at least space and a half within paragraphs, paragraph spacing at least 1.5 times larger than the line spacing, text that is not justified, and text that can be resized to 200 percent without horizontal scrolling to read a line.
In practice that means a reading column capped by a maximum width, body line height around 1.5 or a little above it, and clear gaps between paragraphs. Setting the column width in the CSS ch unit keeps the 80 character limit honest when the font changes. These two criteria turn white space in web design from taste into a checklist; our website accessibility guide covers the wider WCAG picture.
Uneven gaps are the most common spacing fault we see on business sites: 13 pixels here, 22 there, 37 under one heading and 40 under the next. Together they make a page feel slightly off. A spacing scale fixes this by allowing only a short list of values.
The Atlassian Design System is a clear public example. It states that its spacing system is built around a base unit of 8 pixels, with named tokens running from 2 pixels up to 80. It groups them by job: small values up to 8 pixels for compact interface details, medium values of 12 to 24 for things like button padding and gaps inside cards, and large values of 32 to 80 for page level layout. It also asks teams to use the tokens instead of raw pixel values, and to place related elements closer together and unrelated ones further apart.
A 4 point system works the same way with a finer step. The GOV.UK Design System shows another approach: a numbered scale whose larger steps grow on wide screens. Its unit 6 is 20 pixels on small screens and 30 on large ones, and unit 9 is 40 and 60, while the smallest units stay the same at every size.
Whichever base you choose, a shared scale lets a designer and a developer talk about “space 400” instead of pixels, and it makes white space web design repeatable across fifty pages rather than hand tuned on five.
| Source | What it covers | The guidance |
|---|---|---|
| WCAG 2.2, 1.4.12 Text Spacing (AA) | Text that users respace | No loss of content at line height 1.5 times font size, paragraph spacing 2 times, letter spacing 0.12 times, word spacing 0.16 times |
| WCAG 2.2, 1.4.8 Visual Presentation (AAA) | Blocks of reading text | No more than 80 characters wide, line spacing at least 1.5, paragraph spacing 1.5 times the line spacing, not justified |
| WCAG 2.2, 2.5.8 Target Size (AA) | Buttons and links on touch and pointer devices | At least 24 by 24 CSS pixels, or enough space that a 24 pixel circle around a small target touches no other target |
| Atlassian Design System | Spacing tokens | 8 pixel base unit; small, medium and large ranges from 2 to 80 pixels |
| GOV.UK Design System | Responsive spacing | Larger steps grow above 640 pixels, for example 20 pixels on phones and 30 on wide screens |
Space is how a page tells a visitor what belongs together. In web design for forms, white space does the grouping that borders and boxes usually do, following Atlassian’s principle of keeping related items close and unrelated items apart.
What the button says and where it sits on the page is a separate question, covered in our call to action examples. The spacing point is narrower: the empty area around an action is part of the action. Pages built around one form get the same treatment in our landing page design service.
Bilingual web design in the UAE needs white space decided per language, not mirrored from English. W3C’s Arabic and Persian Layout Requirements, a Group Draft Note, observes that Arabic ascenders and descenders extend much further than those of Latin script, and that care is needed to align the two scripts when they appear together. In practice that means a line height chosen for English often feels tight in Arabic, especially where diacritics are used.
Justification is the second trap. The same document describes kashida, the stretching of joins between letters, as one of several ways Arabic text is justified, and warns that excessive kashida produces uneven colour. WCAG 1.4.8 already asks for text that is not justified, so ragged alignment on the reading side is the safer default for body copy in both languages.
In practice, Arabic labels often run to a different length from the English, so fixed width buttons and fixed height cards break, and padding should use logical start and end properties so the space flips with the text. Our Arabic and English website build guide goes further into fonts and direction.
On a phone, white space has a second job: it stops thumbs hitting the wrong thing. Success Criterion 2.5.8, Target Size (Minimum), Level AA, says targets for pointer inputs should be at least 24 by 24 CSS pixels. Its spacing exception is the interesting part for designers: a smaller target can pass if a 24 pixel diameter circle centred on it does not intersect another target or another small target’s circle. In other words, space itself can satisfy the rule.
That has direct consequences for white space web design on mobile. Footer link lists, filter chips, social icons in a row and pagination numbers are the usual failures, because they were spaced for a mouse. Adding padding to each link, or more gap between icons, often fixes them without changing the style.
The other mobile habit is to shrink the large gaps while keeping the small ones. The GOV.UK scale does exactly this: its smallest steps stay the same at every size, while larger steps shrink on screens narrower than 640 pixels. A desktop section gap of 120 pixels may become 64 on a phone; line height and form spacing should not shrink at all, because reading and tapping do not get easier on a smaller screen.
This objection comes up on almost every project, and it deserves a better answer than “trust the designer”. Most arguments about white space in web design end once both versions are seen at real size on a phone.
Empty space is not unused space. It is the part of the layout that tells the visitor where to look.
A few faults appear again and again when we review sites for businesses here:
Most of these white space faults are quick to correct in an existing web design with a spacing review and a few CSS variables. If the problems run through every template, a website redesign is often the cleaner route.
Our team designs websites for businesses in Dubai and across the UAE, and in our white space web design work spacing is set as a system at the start rather than patched page by page. Our web design work includes a written spacing scale and reading rules, our UI UX design service handles forms, states and touch targets for products and portals, and Arabic versions get their own checks. You approve the full design before development begins.
If your current site feels crowded and you are not sure whether it needs a spacing pass or a rebuild, send us a few page links. We will reply with a written fixed price proposal, usually within 45 minutes during business hours, with no obligation.
Straight answers
No. The term means any area with no content in it, whatever its colour. A dark navy band, a photo with a calm area beside the headline or a pale beige background all count, as long as the gap is deliberate and gives the eye somewhere to rest.
Some of it, yes, and that is usually fine. Visitors scroll readily when the first screen tells them clearly what the page offers. What hurts is a first screen so crowded that nothing stands out, which makes scrolling feel like more of the same.
There is no single number that suits every font. W3C's Visual Presentation criterion asks for at least one and a half times the font size within paragraphs, and many fonts read well a little above that. Check a full paragraph in the real font and size rather than trusting a default.
Agree a small spacing scale, write it down as named tokens or variables, and use only those values in design files and CSS. Reviews then become a quick check of whether every gap uses a token, rather than a debate about individual pixels.
Not directly. Search engines do not reward empty pixels. Spacing affects how easily visitors read and act, and pages that are hard to read on a phone tend to lose visitors, so the effect is indirect and depends on the content being worth reading in the first place.
Sources
Fixed price, in writing
Got it. Your quote is being written now.
In business hours you will have it within 45 minutes. Check your inbox for the confirmation.
Keep reading

What well known sites such as GOV.UK, u.ae, RTA, Apple and Stripe get right, and how to turn those qualities into a brief.
Read the article
Registrar, DNS and hosting are three separate things. Here is which ones a UAE business should hold, and what the .ae rules say.
Read the article
When a breadcrumb trail earns its place on a UAE website, and how to design, mark up and translate it properly.
Read the article