Video transcript
A UAE annual report works in two reading directions at once. Arabic runs right-to-left, English left-to-right, in one book. Almost every decision gets executed twice, and must match. Here is how to design a 2026 bilingual report that holds. The strongest UAE reports share four habits. One visual system, bilingual structure from page one, designed charts, tagged PDFs. The catch: almost every habit is executed twice.
The same content sets to a different length in each language. Short strings can swing 200 to 300%, long passages near 130%. So size the grid for the longer language, not the shorter. Two layout patterns recur across bilingual UAE reports. Parallel puts both languages on one spread, for the chairman's statement. Sequential runs one language then the other, for notes and ESG tables.
Arabic script has two digit families: Western Arabic and Eastern Arabic-Indic. Many UAE reports set Western Arabic numerals, 1 2 3, in both versions. A figure inside right-to-left prose still reads left-to-right. The clearest sign a report was designed bilingual, not translated: the two scripts read as one system, not two unrelated fonts. Give the Arabic the leading it needs to carry equal weight.
A strong cover signals the theme and sets the visual system. The Arabic and English titles share one composition, at matched weight. The cover motif must survive mirroring into the right-to-left dividers. Use one chart language across financial and ESG sections alike. Lead each section with the headline figure, then give the detail. DFM, ADX and the GRI Standards set what to disclose; design makes it readable.
A bilingual data table leaves nowhere for an inconsistency to hide. Three things get planned first: column order, precision, one source figure. Order columns where an Arabic reader starts, not flipped from English. Well-designed UAE reports follow a predictable 7-section flow. Overview, chairman, CEO, financials, governance, ESG, audited statements. The Arabic contents and bookmarks point into the Arabic sequence.
A tagged PDF serves analysts and assistive tech alike. Bookmarks, alt text for charts, and a logical reading order. Set direction in the structure once, and the Arabic order follows. The most useful work happens before design begins. Settle the numeral rules, the type pairing, the bilingual structure first. One visual system, sized for the longer language, read as one. Plan yours with Walk Production.
A reader judges an annual report before they read a single number. The cover sets the register; the first spread confirms it or breaks it. The best annual report examples we have worked with across Malaysia and Singapore share one discipline: every design decision serves the content it carries.
This post gathers the visual and layout principles that strong UAE annual reports share in 2026. The thread that runs through all of them is bilingual production. The ESG disclosure context set by the Dubai Financial Market and Abu Dhabi Securities Exchange decides what a report has to present; the Arabic-English requirement decides how much of the design work has to be done twice, in two reading directions, and held in step.
A note on scope. Walk Production designs and writes annual reports, sustainability reports, and integrated reports for listed companies across Malaysia and Singapore, and now serves the UAE market. Our own team does the writing and the design. Sustainability consulting is available beside that, with the consultant on the project appointed by you or drawn from our partner panel. We are not an audit, assurance, or legal firm, and independent assurance stays with your appointed providers. The observations here are about design craft and clear presentation. Confirm your reporting obligations with those providers and the official sources cited.
What do the best UAE annual reports have in common in 2026?
The strongest UAE annual reports in 2026 share four habits: a single visual system across financial and ESG content, a bilingual structure planned from page one, designed (not auto-generated) charts, and accessible tagged PDFs. The disclosure leads and the design follows it.
The visual system runs from the cover through to the back-of-book data appendices: same palette, same chart style, same heading hierarchy across financial and ESG sections. The bilingual structure is settled before layout begins, so neither the Arabic nor the English version has to be retrofitted later. Charts are designed rather than exported at spreadsheet defaults. The digital PDF is tagged so an analyst or an assistive-technology user can navigate without friction.
What separates a UAE example from its Singapore or Malaysian equivalent is that almost every one of those habits has to survive being executed twice, once in each reading direction, and stay identical where it matters. That is the real subject of this post. The shared principles of good report design are well understood; the bilingual mechanics are where most of the craft, and most of the failure, actually sits.
For the regulatory context that sets what UAE companies must present, see our guide to annual and sustainability reports for UAE companies.
How is bilingual Arabic-English layout shaping UAE report design?
Bilingual Arabic-English layout is the single biggest design driver for UAE reports. Arabic reads right-to-left and runs to a different length from the same English content, so the grid, column widths and page breaks must be planned for both directions from the start, never retrofitted after the English version is locked.
The Arabic and Persian layout requirements from the W3C Internationalization Working Group set out why the page behaves the way it does. Arabic letters flow right-to-left, while numbers and embedded Latin text inside that flow still run left-to-right, which makes a bilingual page inherently bidirectional. Direction has to be a structural property of the document, decided in the layout, rather than a visual flip applied to a finished English file. The W3C’s separate note that text direction should be set in the document structure, not as a presentational override, is the same idea expressed for markup, and it carries straight into a bilingual PDF: get the direction right in the structure and the reading order follows; bolt it on at the end and it fights you.
The length difference is the part teams most often underestimate. There is no published figure for how much Arabic specifically expands against English, so treat the numbers carefully, but the W3C’s guidance on text size in translation gives a useful order-of-magnitude planning guide: text translated out of English is typically longer, and the shorter the source string, the larger the swing. The rates it cites run from around 200 to 300 percent for very short strings (up to ten characters) down to roughly 130 percent for long passages over seventy characters. The expansion is not uniform across the document either, so a heading, a chart label and a body paragraph each grow by a different amount. The practical rule that falls out of this is simple: size the grid for the longer-setting language. A column built to fit English copy will overset when the Arabic is poured in; a column built to hold the longer setting accommodates both.
Two layout patterns appear most often across bilingual UAE reports.
Parallel layout places both languages on the same spread. It suits shorter, high-visibility sections: the chairman’s statement, the CEO review, governance summaries. Seeing both languages together carries weight in these sections, and the length difference is manageable across a short passage. Arabic often benefits from a slightly larger point size here to hold equivalent visual weight against the Latin setting.
Sequential layout presents one language fully, then the other. It suits long technical material where parallel columns would compress the type past comfort: financial notes, ESG data tables, back-of-book appendices. Running two languages across a dense data spread crowds the page; giving each its own run keeps both legible. Many reports mix the two, parallel for the front narrative and sequential for the back data, and deciding which sections use which pattern belongs in the structural plan, before layout starts.
Our team produces bilingual Bahasa Malaysia-English reports across Malaysia and Singapore. That planning discipline carries directly to Arabic-English work: treat both languages as primary from day one, and size the document for the language that takes more room.
How do numerals and figures work across Arabic and English?
Numerals are a pure typesetting decision, and in a financial report they are the decision a careless team gets wrong most often. Pick one numeral system and hold it across both language versions, set the Arabic separators deliberately, and make sure every figure inside right-to-left prose still reads left-to-right. A reader comparing the two versions should see the same number.
Arabic script is written with more than one family of digits. The W3C’s Arabic and Persian layout requirements document the two that matter for a UAE report: Western Arabic numerals, which are the European 1 2 3 most readers recognize, and Eastern Arabic-Indic numerals, the distinct glyphs used across much of the Arabic-speaking region. They are not interchangeable on the page. Many UAE financial reports set Western Arabic numerals in both the Arabic and English copy, precisely because an analyst reading the two versions side by side wants the digits to match without translation. Whichever family you choose, the choice is made once and held everywhere, because switching numeral systems between the narrative and the tables splits one report into two documents.
The direction of a figure is the second trap. Because Arabic runs right-to-left while the digits inside it run left-to-right, a number embedded in Arabic prose, a year, a percentage, a line in a sentence, has to be handled so it stays in left-to-right order. Set the direction structurally rather than nudging glyphs by hand, and the bidirectional behavior resolves the way a reader expects. Fix it visually at the end and you get transposed digits, which in a financial figure is not a cosmetic problem.
Separators are the third detail, and they are specific to the script. Arabic-Indic setting uses its own decimal separator and its own thousands separator, distinct from the Latin point and comma. A bilingual table that carries 1,234.5 in the English column and the same value with the wrong separators in the Arabic column has, in effect, printed two different-looking numbers for one figure. The rule that keeps this clean is to decide, for the whole document, which numeral family and which separators each language version uses, and then make every financial and ESG figure obey it. In data that a reader may set side by side, a number is only trustworthy if it is presented the same way every time it appears.
Pairing an Arabic and a Latin typeface
The clearest single signal that a report was designed bilingually, rather than translated, is that its Arabic and Latin type work together as one system. Arabic and Latin scripts have different vertical proportions, different baseline behavior, and different needs for line spacing, so a size and leading that sit well in English will rarely sit well in Arabic at the same values.
A heading set at a size that feels confident in Latin can read cramped or oversized once the Arabic is set to match. Arabic letterforms carry more of their weight along a horizontal spine and rely on generous line spacing to stay legible, where a Latin face of the same nominal size occupies the line differently. The fix is to pair an Arabic typeface with the Latin one deliberately, choosing faces whose weight, apparent size and rhythm match, so the spread carries one voice instead of two unrelated fonts. Where the Arabic needs a slightly larger optical size or more leading to carry equal weight, the design gives it that, rather than forcing both scripts to the same numeric size and letting one look weaker.
This is the kind of decision that does not show up in a brief and is obvious on the page. A bilingual report where the two scripts are tuned to each other holds its composure; one where a single Latin-first type scale was imposed on the Arabic exposes the English design underneath. The discipline transfers from any serious bilingual work, including the Bahasa Malaysia-English reports our team produces, even though the scripts differ: treat each language’s typesetting as a craft problem in its own right, then make the two agree.
What bilingual cover and theme ideas work for UAE companies?
A strong UAE cover does one job: it signals the year’s theme in seconds and sets the visual system the rest of the report inherits. Pick a single idea, carry it through the section dividers and the data styling, and make it read with equal weight in both Arabic and English.
A motif that recurs (an architectural element, a data graphic, a photographic treatment) ties the document together when it reappears on dividers and in chart styling. Finish choices such as foil, emboss and spot UV earn their place on the title or the motif; spread across body content or decorative borders they clutter the page, and institutional readers take restraint as a sign of confidence.
What makes the UAE cover its own problem is the bilingual lockup. The Arabic and English titles share one composition, and the relationship between them is decided deliberately. They can stack or sit side by side, but they carry matched visual weight: an Arabic title set noticeably smaller or pushed to a secondary position tells every reader that the document was designed in English and adapted afterward. The Arabic title is drawn as a piece of typography in its own right. The recurring motif then has to survive mirroring, because the section dividers in the Arabic run flip to right-to-left, and a graphic device that only works facing one way breaks the moment the page turns the other. A motif designed to read in both directions is what lets one visual system carry across both halves of the book.
How should ESG and financial data be visualized in a UAE report?
Use one consistent chart language across the whole document, lead each section with a headline figure, then give the detail. A multi-year revenue trend or an emissions chart is read in seconds, so the design of those few elements decides whether the section gets read at all. In a bilingual report, the visual system also has to hold across two scripts, and the data tables have to agree figure for figure in both.
The Dubai Financial Market’s ESG and sustainability resources include the DFM ESG Reporting Guide, which shapes what listed DFM companies disclose. The Abu Dhabi Securities Exchange publishes parallel ESG disclosure guidance for ADX-listed companies, and the GRI Standards are among the most widely used global sustainability frameworks, referenced by both exchanges’ guidance. Together these set the reporting context. The design task is to present that content clearly, not to advise on compliance, so confirm your framework obligations with your advisers.
Exchange guidance sets what to disclose. Design makes it readable.
DFM, ADX, and GRI Standards are cited here as context for what UAE companies present in their reports, not as compliance advice. Confirm the current requirements on the official sources before you finalize any disclosure.
A comparison of layout patterns across the two data types:
| Content type | Layout pattern | Design watch-points |
|---|---|---|
| Multi-year financial highlights | Full-width dashboard at the front of the financial section | One metric per panel; units stated once; same numerals in both versions |
| ESG performance summary | Dashboard spread before the full ESG data tables | Consistent icon set; baseline year clearly marked |
| Revenue or profit trend chart | Designed bar or line chart with year labels | Set in brand colors; not spreadsheet defaults; y-axis labeled |
| Emissions or water data | Year-on-year comparison chart with target line | Units consistent with GRI or DFM metrics; source noted |
| Governance data | Clear table with board composition, attendance, committee membership | Headers aligned; no merged cells in complex rows |
The bilingual data table is where this section earns its keep, because a table leaves nowhere for an inconsistency to hide. Three things have to be planned before the figures arrive.
Order the columns for the reader. Because Arabic reads right-to-left, the point where the eye enters a table shifts to the opposite side, so the Arabic version needs its leading column and row labels placed where an Arabic reader starts, not the English table flipped pixel for pixel. Headers, subtotals and footnote markers all have to sit where each language expects them; a table reversed wholesale tends to strand the totals where they are hardest to find.
Hold the precision identical, figure for figure. A value shown to one decimal place in English must not surface to two in Arabic. In a financial or emissions table a reader may set side by side, a precision mismatch reads as an error even when the underlying number is the same.
Feed both versions from one governed source value. Where every metric draws on a single source figure, the Arabic and English tables are filled from that one entry rather than keyed in twice, so the two agree by construction instead of by luck. This is why the index structure is fixed before bilingual production begins, rather than reconciling two separately typed tables at the deadline. Then proof the table as its own pass: a reader fluent in each language confirming that every figure matches across versions, in the same unit and precision, under the same label, catches what general proofreading misses, because a transposed digit is invisible unless someone is checking the numbers on purpose.
Scannable tables carry clear headers, aligned figures, and units stated once. A table where units change between rows, or where the Arabic and English columns drift apart, costs the reader time and signals the data was assembled rather than designed.
What page structure and section flow do well-designed reports follow?
Well-designed UAE reports follow a predictable flow so different readers can navigate fast. Designers vary the order, but every mandatory item stays findable and the narrative reads front-to-back.
A reference flow most well-designed UAE annual reports share:
- Corporate overview: business model, key metrics, highlights spread.
- Chairman’s statement: strategic direction from the board.
- CEO or managing director’s review: operational performance and priorities.
- Financial review: analysis of revenue, margins, capital allocation.
- Corporate governance report: board composition, committees, CMA (formerly SCA) requirements.
- ESG content: integrated through the narrative or as a clearly signposted section.
- Audited financial statements: with notes and the independent auditor’s report.
A hyperlinked contents page and section openers that name their content serve the narrative reader, the analyst, and the regulator equally. In a bilingual report this flow has to hold in both runs, with the Arabic contents page and bookmarks pointing into the Arabic sequence rather than the English one.
ESG content integrated through the narrative reads differently from ESG content parked as a back-of-book appendix. Integration signals that sustainability is part of the business story; an appendix signals it was added after the financial sections were done. That is a design and editorial choice.
Caveat: the mandatory contents of a UAE annual report are governed by DFM, ADX, and CMA requirements. Confirm the mandatory items against the current official guidance before you finalize the structure.
How do you design a report PDF that works on screen and for accessibility?
Design the report for screen first, then derive print from the same master. A tagged PDF with a hyperlinked contents page, bookmarks, and alternative text for charts serves analysts and assistive technology equally well.
The tagged, accessible PDF techniques from the W3C Web Accessibility Initiative define the requirements: tagged headings and table structure, a logical reading order, and alternative text for figures. A chart without alternative text leaves a screen-reader user with a gap in the data. A table without tag structure becomes unnavigable even if it prints correctly.
The sequence here is what saves a project from late rework. On the annual report design we have produced across Malaysia and Singapore, the reports that hold together are the ones designed for the screen and then derived for print, rather than laid out for the printer and flattened into a PDF afterward. A print-first file looks fine on paper and arrives in an analyst’s inbox stripped of bookmarks, links and tags. Set the master up for screen reading first, and the print version follows from it without a second design pass.
Practical features that distinguish a well-designed digital report PDF:
- Bookmarks for every major section, matching the hyperlinked contents page.
- Internal cross-links between the strategy section and the financial statements.
- Alternative text for all charts and infographics, describing the finding the chart illustrates rather than just “bar chart”.
- Tagged headings and table structure, so the reading order survives independent of the visual layout.
For a bilingual report the accessibility work has to hold in both versions, not just the English one. The Arabic version’s reading order needs to follow the right-to-left document structure, so a screen reader moves through it in the order an Arabic reader would, rather than tracking the English layout repurposed with a visual override. This is the same structural-direction point that governs the visual layout, surfacing again in the accessibility layer: set direction in the structure once, and both the sighted reading order and the assistive-technology reading order come out right.
What design mistakes weaken a UAE annual report?
The common faults are visible at a glance, and most of them trace back to bilingual production being treated as a translation step rather than a design discipline.
- ESG section in a different palette or voice. Both sections must share the same visual system from the first draft, or the reader ends up with two documents stapled together.
- Arabic and English versions that diverge. Different figures, different numerals, different tone, or different layouts between languages undercut the whole document. Plan both together; proof both together.
- Bilingual added at the end. When Arabic is commissioned after the English layout is locked, the text overflows a grid built for English copy fit, and the page count stops matching across versions. The result is a bilingual document in name only.
- Inconsistent numerals or separators. Switching numeral systems between sections, or carrying mismatched decimal and thousands separators between the Arabic and English tables, prints one figure two different ways.
- Auto-generated charts and dense tables. Spreadsheet exports produce charts calibrated for a data analyst, not an annual report reader. Undifferentiated tables with no clear hierarchy signal the data was not edited.
- A cover theme that could belong to any company. Generic concepts such as “growth” or “resilience” without specific visual expression miss the chance to signal character, and a motif that cannot survive mirroring into the right-to-left dividers breaks the system.
- Accessibility left as an afterthought. An untagged PDF, missing alternative text, and a broken right-to-left reading order are each a gap that a meaningful share of your readers will notice.
How Walk Production can help
Walk Production designs and writes annual, sustainability, and integrated reports for listed companies and organizations, with a track record across Malaysia and Singapore and now serving the UAE market. Our in-house team covers concept development, layout design, data visualization, bilingual production, and print and digital delivery under one account.
For UAE companies preparing an annual report, the most useful work happens before design begins: aligning the financial and ESG narratives, settling the numeral and typographic rules, and planning the bilingual structure so both language versions start from the same brief. A single visual system agreed at the outset, sized for the language that takes more room, avoids the most common rework cycles.
To see how the approach lands in practice, look through the reports and publications we have designed, including our annual report for MSIG Insurance (Malaysia) Berhad, an insurance group, produced as part of our Malaysia and Singapore reporting work. Our in-house report design and production service covers the full track from concept to filed document. To discuss the production calendar and scope for your next cycle, talk to our editorial team.
