Adhere to Typography guidelines by using approved fonts, appropriate font weights for headings, and responsive typography measures
The approved typeface is IBM Plex Sans Arabic, actually loaded rather than merely declared, and the type variables split into two distinct sets: Display for headings and Text for body copy. Mixing the two collapses the visual hierarchy even when the family is right.
It is one of the primary criteria in the foundations group of the Saudi Platforms Code, issued by the Digital Government Authority.
How XFix measures this criterion
The applied value is read from the page and compared with the value approved in the Platforms Code, so the verdict comes from a measurement rather than an estimate, and the observed and expected values are attached together.
The official text and its checkpoints
This criterion rests on 2 checkpoints published in the Platforms Code, and they are the reference when judging it.
This criterion on the official Platforms Code siteThe checkpoints, one by one
Each checkpoint below has its own answer: what it requires, what passes and what fails, how it is measured or verified, and how it is repaired. Each has a direct link.
The approved typeface, IBM Plex Sans Arabic
Machine-measuredDGA-003-aThis checkpoint requires the approved typeface IBM Plex Sans Arabic as specified in the Platforms Code, actually loaded rather than merely named in the stylesheet. What counts is what renders on screen, not what the font stack declares.
XFix measures this checkpoint automatically, and attaches the observed value and the expected value together.
What passes: IBM Plex Sans Arabic is first in the font stack, its file is loaded, and rendering actually resolves to it.
What fails: A custom face leading the stack with the approved font behind it as a fallback: the text renders in the custom face while the declaration still looks correct.
How it is measured or verified: The tool reads the applied font stack and verifies the file actually loaded, separating a font declared in CSS from a font that draws the text. Family names are normalised, because self-hosted fonts name each weight as its own family.
How it is repaired: Move the approved font to the head of the stack and self-host it as woff2 for every weight in use; relying on a system font opens the door to different rendering per device.
Type variables: Display and Text
Machine-measuredDGA-003-bThis checkpoint requires the correct type variables from the Platforms Code, which come in two distinct sets: Display for large headings and Text for body copy. Mixing them collapses the visual hierarchy even when the typeface itself is right.
XFix measures this checkpoint automatically, and attaches the observed value and the expected value together.
What passes: Every size, weight and line height on the page traces to a declared variable in one of the two sets, headings from Display and body from Text.
What fails: A page heading at a body size, or body copy at a heavy display weight, so heading and text read as visually equal and the order is lost.
How it is measured or verified: Applied sizes, weights and line heights are read and compared with the two sets. The tool’s typography rule currently governs family alone, so this checkpoint is verified by your own team.
How it is repaired: Bind each heading level to one Display variable and body copy to one Text variable, then delete the hand-written sizes from the stylesheet.
Related criteria
The limits of this tool
XFix is an independent commercial tool. It is not part of the Digital Government Authority, is not endorsed by it, and does not act on its behalf. What it produces is an indicative estimate expressed as a range. It is not the Platforms Code Application Certificate and not a declaration of conformity. The certificate is issued by the Authority alone, and the Authority’s assessment remains the reference.
Its usefulness is in showing the gap early and with evidence. It does not stand in for the body that decides.