XFix reads publicly published pages only. It requests no credentials and retains no entity data. Traffic is encrypted over HTTPS.
Criterion 12 · ComponentsMachine-measured

Ensure Buttons follow the Platforms Code Design System

Buttons must be called from the library with their approved height, radius, fill and padding, and must carry all six interactive states. The state most often lost is the focus indicator, removed because it “spoils the look” — which puts the primary action of a page out of reach of anyone not using a mouse.

It is one of the primary criteria in the components 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 site

All 2 checkpoints, in Arabic

This criterion’s 2 checkpoints are not written in English yet. The Arabic page carries all of them in full, each with its own answer, what passes and fails, how it is measured, and how it is repaired.

Criterion 12 in Arabic, with every checkpoint

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.

Criterion 12 · Buttons · Saudi Platforms Code | XFix