Ensure usage of approved icons as per the Unified Design System (Code of Platforms)
Icons come from the Platforms Code library without substitution and without changes to size or colour, and the alert palette is reserved for alerts. An icon coloured like a warning because it suits a section teaches users to ignore the colour when it means one.
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
This criterion admits automated measurement and no rule has been built for it in the tool yet, so the scan counts it neither for nor against and the report shows it by name and status. The rule is in preparation.
The official text and its checkpoints
This criterion rests on 4 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 icon library, without substitution or resizing and recolouring
No rule built yetDGA-006-aThis checkpoint requires icons from the Platforms Code library without replacing them with another set and without changing their size or colour. A set imported from an external source is a violation even when it resembles the original in style.
This criterion admits automated measurement and no rule has been built for this checkpoint yet, so the scan counts it neither for nor against.
What passes: Every icon on the page comes from the Platforms Code library at its approved size and colour.
What fails: A popular third-party icon set covering the page, or an official icon recoloured to suit one section.
How it is measured or verified: Observed icons are compared with the Platforms Code library by fingerprint, size and colour. No rule has been built for this criterion yet, and the verification step below covers it.
How it is repaired: Replace the external set with library icons, and return modified sizes and colours to their approved variables.
Icon colour: the alert palette for alerts only
Verified by your teamDGA-006-bThis checkpoint separates two uses of an icon: an alert use that takes the approved success, error, warning and information colours exclusively, and a general use for categorising content that takes neutral or primary colours. Using an alert colour for anything but an alert is forbidden.
This checkpoint is not measured automatically: judging it needs interaction with the page, and crawl ethics forbid interacting with an entity’s platform.
What passes: The error icon is red inside an error message and nowhere else, and category icons are grey or green.
What fails: A section icon in the warning colour because it suits the section visually, which teaches users to ignore the colour when it means a real warning.
How it is measured or verified: The icon’s colour and the context of the element containing it are read, separating alert context from categorising context. No rule has been built for this criterion yet.
How it is repaired: Confine alert colours to notifications and status messages, and move category icons to the neutral or primary colour.
The Featured icon above 24 pixels
No rule built yetDGA-006-cThis checkpoint requires the Featured icon component whenever an icon larger than 24 pixels is needed, rather than enlarging the ordinary icon. Changing the Featured icon’s own variant colours and sizes is likewise forbidden.
This criterion admits automated measurement and no rule has been built for this checkpoint yet, so the scan counts it neither for nor against.
What passes: Every icon above 24 pixels is called as a Featured icon with its approved variants.
What fails: An ordinary icon scaled to 48 pixels in a features section, where its edges coarsen and it falls out of the Featured icon’s visual system.
How it is measured or verified: Observed icon sizes are measured and the component used above the threshold is checked. No rule has been built for this criterion yet.
How it is repaired: Replace enlarged icons with the Featured icon component from the library, without modifying its variants.
Requesting approval for an icon the library lacks
No rule built yetDGA-006-dThis checkpoint requires an icon the library does not carry to be designed to the Platforms Code icon guidance and submitted for approval through the channel the official reference points to. A gap in the library does not license importing an external set.
This criterion admits automated measurement and no rule has been built for this checkpoint yet, so the scan counts it neither for nor against.
What passes: One or two icons designed to the library’s guidance for a need it does not cover, with an approval request submitted.
What fails: Importing a whole external set on the strength of one missing icon.
How it is measured or verified: Whether a request exists and its status are outside what can be measured from a public page, so this checkpoint is verified by the entity’s own team. The tool only reports icons falling outside the library.
How it is repaired: Design what is missing to the library’s guidance and submit the approval request; return everything else to library icons.
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.