Most Arabic interfaces lose readability for an unglamorous reason: the palette was chosen on a bright designer monitor, in a cool office, at full zoom. The real user opens the app in Kuwaiti daylight, on a cheap phone, reading a script built from thin connectors and small dots. That is where the design gets judged, not in the portfolio shot.
WCAG asks for a contrast ratio of 4.5:1 for normal body text and 3:1 for large text, meaning 18pt or 14pt bold. Treat those as a floor, not a target. For Arabic interfaces, start at 4.5:1 and stay away from the edge, because real reading conditions are worse than test conditions: low brightness, an older screen, glare. Free contrast checkers take a minute per colour pair, so there is no excuse for skipping them.
Arabic type relies on thin connectors, small dots and diacritics that vanish when scaled down. An elegant light grey that works in English can make tashkeel invisible in Arabic. The practical fix: keep the font size, deepen the colour one or two steps, avoid thin weights below 16px, and test the smallest size you actually ship. Light grey body text on white is the single most common fault we see in Arabic UI reviews.
Gold is a strong brand colour in the Gulf, but pure gold on pure white produces a very low contrast ratio, and the text turns into decoration. The answer is not to drop gold; it is to change its job. Use it as a background, a border or an icon, with dark text on top, or move to a darker gold with a brown undertone. The same logic applies to yellow, light green and pink accents, all common in Gulf brand systems.
In dark mode, do not simply invert. Lower the saturation of the background and lift the text slightly instead of using pure white, which creates a halo around Arabic letterforms. On meaning: green reads as good and as identity, red as warning, blue as trust and formality. Never carry meaning with colour alone. Add an icon or a word, because some users cannot separate red from green, and colour is read differently from one market to the next.
Before handover, review every interactive state, one at a time:
Then open the interface on the cheapest phone in the team, at midday, with brightness turned down. That one minute reveals more than an hour of debate on a high-density display, and it usually settles the argument about that elegant grey.
At Q8DM we treat this as part of software development, web and mobile design and corporate training, from the first palette to the last button state. If your project needs a real readability review on the devices people actually use, start at https://q8dm.com and talk to us.