What government procurement commonly asks for is not a list of lines to answer but build decisions you can test. This article covers accessibility, privacy, Nafath, Arabic, continuity, content and handover, with the evidence to prepare for each.
A government website is not a marketing surface. It is a service channel, a trusted entry point, an official source of information, and a document that can be requested in an audit. It is not enough for the site to work in a demo. Government procurement asks for evidence: how access is tested, where data is stored, who approves content, and what happens when the service goes down.
Many teams treat the requirements document as a form to answer line by line, then discover after award that the lines do not translate into a build. This checklist turns what government procurement commonly asks for into engineering decisions you can test. It is not a legal opinion and not a substitute for reading the contract. It is a build map for what the team is actually asked to deliver.
The service first, the website second
People do not visit a government website to browse. They visit to complete a transaction: obtain a certificate, submit an application, pay a fee, follow a status, or verify a piece of information. Each journey needs a definition: who the user is, what proves eligibility, what the next step is, and what happens if they stop halfway. A site that cannot answer those questions becomes a well-designed archive.
Arabic comes first, and English is a complete version rather than machine translation. Official content is written in Arabic and then reviewed, because it carries obligation and meaning that literal translation does not move. Assign a content owner to every service page: who writes, who reviews, who approves, and how long the information stays valid before review. Public-sector content ages faster than design, and an outdated page can become an official error.
Accessibility is a build requirement
WCAG 2.2 was published as a W3C Recommendation on 5 October 2023 and adds nine success criteria to 2.1. Some of them change components rather than copy: 2.5.8 requires a pointer target of at least 24 × 24 CSS pixels, 2.5.7 requires a single-pointer alternative to dragging, 3.3.7 forbids asking for the same information twice in one process, 3.3.8 regulates authentication without a cognitive function test, and 2.4.11 stops a sticky element from entirely hiding the focused component.
These are not cosmetic improvements added at the end. They change form design, step order, and the behaviour of a sticky bar on mobile. Test with the keyboard alone, with an Arabic screen reader, with screen magnification, and on a small phone. Document every test and its result, because procurement will ask for evidence rather than a promise. Test error messages too: an error a screen reader cannot announce is not an understandable error.
| Requirement | What procurement commonly asks for | Evidence you prepare |
|---|---|---|
| Accessibility | A commitment to WCAG 2.2 and real testing | A criteria-based test report, a defect log, and a remediation plan |
| Privacy | A data map, a lawful basis, and a breach procedure | A processing record, a processor list, and a retention policy |
| Identity | A clear Nafath journey, roles, and a fallback | A journey map, a role matrix, and a failure scenario |
| Hosting | Where data and backups sit, and who the subprocessors are | A region diagram, the hosting contract, and the processor list |
| Continuity | A service-level agreement and a recovery plan | Service hours, reporting channels, and a recovery test result |
| Security | A risk assessment and a penetration test | The test report, the remediation record, and the fix plan |
| Content | A content owner, language review, and approval | An approval log, a content guide, and an archive policy |
| Handover | Code, documentation, training, and access transfer | A handover pack, an account list, and an exit plan |
Privacy, residency and retention
The Personal Data Protection Law has been fully enforceable since September 2024. On 6 October 2026 SDAIA published draft amendments to the Implementing Regulation, and the consultation closed on 5 November 2026. The draft proposes localisation of personal data inside the Kingdom with limited exceptions, and a breach notification within 72 hours of awareness without a harm threshold. These are proposals, not rules in force, but they set a direction the build should be ready for.
In practice, start with a data map: which personal data is collected, why, where it is stored, who can access it, how long it is kept, and who processes it on your behalf. Cover backups, logs and analytics as well, because they are often forgotten. Write a breach procedure: who detects, who notifies, who decides, and how it is recorded. Privacy is not a policy page in the footer. It is a set of decisions in the data model and the permission model.
Identity, integration and continuity
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
Nafath is not a button on a login page. It is a journey that defines how the user proves identity, what role they receive afterwards, what data is stored, and how it is reviewed. Separate identity proofing from authentication, and decide what happens if the service fails or the user cannot complete the step. Test negative cases before positive ones, and write a fallback that does not leave the user without an exit.
Integration with internal systems needs clear contracts: who owns the master data, who updates it, what happens on conflict, and how failed attempts are recorded. Continuity belongs in the contract: service hours, reporting channels, response time, the recovery plan, and who speaks to the public during an outage. Do not promise an availability figure in an article; write it into the service-level agreement after you know how you will measure it.
Content and handover
Content on a government site is not marketing. It is instructions, conditions and deadlines. It therefore needs a lifecycle: draft, language review, authority approval, publication, archive. The English version needs independent review, images need alternative text, and tables need clear headers. These details make a page usable and auditable, not merely displayable.
A good handover includes the code and repository, infrastructure as documentation, a deployment and rollback plan, runbooks, team training, and transfer of the domain and service accounts. Agree acceptance tests before you start: a screen reader, a keyboard, a complete application form, an invoice, and an outage scenario. If those tests are not defined, delivery will be measured by the date alone, and a date does not prove the site works.
The build checklist before award
Use this list when reading the requirements document and when writing the proposal. Every line should appear in the method, the schedule and the handover, not only in the compliance section. Also review integration services, and the earlier post on a website RFP in Saudi Arabia, which separates requirements from scope.
Service journeys: turn every service into written steps, states and outputs.
Content ownership: name a writer, a language reviewer and an approver for every page.
Accessibility: tie every component to the WCAG 2.2 criterion that applies, and test it.
The data map: cover logs, backups and analytics, not only forms.
The Nafath journey: define roles, data, and the fallback when the service fails.
Continuity: write service hours, response and recovery before award.
Acceptance tests: run scenarios in front of a committee, rather than describing them.
The handover pack: agree code, documentation, training and access before closure.
Frequently asked questions
Is every line in the requirements document binding law? The document is a contract between you and the authority, not a public law. Read it as a contractual obligation, and ask about ambiguous lines before signing. This article describes what procurement commonly asks for; it does not interpret the law.
Is WCAG 2.2 required on every government site? Many authorities ask for it in contracts, and the standard was published on 5 October 2023. Treat it as a build target and document the testing, and do not claim conformance without evidence.
Do we need Nafath? If the service requires verifying a user's identity, Nafath is the common national route. Define the journey, roles and data before integration.
Where should data be stored? That is a contractual and technical decision together. Review the requirements, choose the region, and document subprocessors. The draft amendments propose localisation inside the Kingdom with limited exceptions, but they remain a draft.
What do we hand over at closure? The code and repository, documentation, the deployment and rollback plan, training, and transfer of accounts. Ask for a written list in the contract.
Sources
- W3C WAI: What's New in WCAG 2.2 — a Recommendation on 5 October 2023, with nine new success criteria.
- SDAIA: Personal Data Protection Law — fully enforceable since September 2024.
- Rasad integrations — how systems, identity and data are connected.
- A website RFP in Saudi Arabia — from requirement to scope and proposal.
- Rasad's published price bands — the figures this article works from.
Cover image: David Kernan, CC BY-SA 4.0, via Wikimedia Commons.

