“A typography field guide for property websites, brochures and Arabic–English brand systems, covering scale, contrast and practical QA.
Choose type for the job, not the moodboard
A development brand needs to communicate at very different distances: an outdoor sign, a website headline, a pricing table, a dense contract and an Arabic brochure. Begin with the most demanding content, not the largest hero headline. Test the typeface with numerals, symbols, long project names and real addresses. A beautiful display font that cannot handle form labels or bilingual paragraphs should not be the only font in the system.
Define a hierarchy with a small number of roles
Assign clear jobs: display heading, section heading, body, label, caption and data. Build a responsive type scale around those roles rather than adding a new arbitrary font size to every section. The distinction between heading and body should come from a combination of size, weight, spacing and layout. In a property card, the project name, location, price and availability should never compete at the same visual intensity.
Treat Arabic as a first-class design language
Arabic is not a mirrored Latin paragraph. Test line length, connected letterforms, punctuation, diacritics, baseline alignment and numerals in the actual font. Allow sufficient line height, and do not compensate for poor contrast by lowering opacity on Arabic display type. Verify mixed-direction fragments such as phone numbers, square metres and invoice identifiers. The English and Arabic layouts may need different line breaks while preserving one brand rhythm.
Check contrast and resizing
For WCAG 2.2 Level AA, normal text generally needs a contrast ratio of at least 4.5:1, with 3:1 for qualifying large text. Test actual rendered colors, including text over photography and gradients; logo marks have different treatment from body copy. People should be able to enlarge text without breaking a form or hiding information. Test long labels, browser zoom and narrow screens. A minimal interface is not good if people cannot read it.
Write usage rules the team can actually follow
A compact typography sheet should specify font families and licenses, permitted weights, responsive sizes, line heights, letter spacing where appropriate, maximum line widths and examples of correct and incorrect use. Include real website cards and brochure spreads, not only a specimen poster. Export font assets only within their license terms and verify web performance to avoid layout shifts as fonts load.
Run the final bilingual QA pass
Review one landing page, one listing card, one data table, one form and one downloadable PDF in both languages. Check that the title does not wrap onto a single isolated word, the price stays readable, punctuation remains in the right place and fonts embed correctly in print files. Fix the system tokens if you see the same problem twice. Typography is a usability and trust decision, not a decorative finishing touch.
References and further reading
Platform specifications, policies and production requirements can change. Verify the current requirements before publishing or printing.