A municipal permit portal in Riyadh fails a contrast check on its primary call-to-action. The finding can be reported three different ways: as a WCAG 1.4.3 violation in an engineering ticket, as a Citizen Experience indicator drop in the Digital Government VRP quarterly, and as a Reduced Inequalities data point in the parent ministry's ESG submission. Same finding, three audiences, three rolled-up numbers. This article is about why that mapping matters and how to do it without translating the same audit three times.
How Vision 2030 treats digital inclusion
Saudi Vision 2030 organizes the kingdom's transformation through Vision Realization Programs (VRPs). Three of them have direct digital-accessibility consequences, and they are read upward into different parts of the program governance:
- Digital Government VRP — accessibility is a published indicator of citizen-facing digital service maturity. Ministries report against it quarterly. The DGA accessibility index (the 0–100 composite covered in our DGA guide) is the underlying measurement instrument here. Indicators roll up into the Digital Government Authority's annual digital maturity assessment.
- Quality of Life VRP — digital inclusion sits under the social welfare cluster, alongside healthcare and education access. Annual cadence. The KPI is qualitative-quantitative: a narrative on inclusion outcomes paired with measurable indicators (service reach, citizen satisfaction by demographic, barrier-report SLA performance).
- Privatization VRP — when a government service migrates to a private operator, the accessibility commitment migrates with it. The contracting authority writes the floor into the concession agreement. Many private Gulf operators discovered this clause only after winning a tender.
Two consequences fall out of that structure. First, accessibility is no longer the developer's good-citizen task — it is a number a program manager carries to a quarterly review. Second, the same finding can be read by three different governance bodies depending on how it's tagged. The audit that produces the finding has to do that tagging.
Mapping to UN SDG 10
UN Sustainable Development Goal 10 — Reduced Inequalities — has two indicator clusters that digital accessibility addresses directly:
- Indicator 10.2 — "by 2030, empower and promote the social, economic and political inclusion of all, irrespective of age, sex, disability, race, ethnicity, origin, religion or economic or other status." Digital service access is one of the operational interpretations of this indicator at the country level.
- Indicator 10.3 — "ensure equal opportunity and reduce inequalities of outcome, including by eliminating discriminatory laws, policies and practices and promoting appropriate legislation, policies and action in this regard." Digital accessibility regulation — the very existence of frameworks like the DGA standards and the Qatar e-Accessibility Policy — is reportable evidence here.
For listed Gulf enterprises filing integrated annual reports — under SAMA reporting frameworks for banks, CMA for listed companies in KSA, or QFMA for Qatari listed entities — the digital-inclusion section of the ESG portion is now a regular feature. Auditors and analysts ask for it. The one-page form is the same shape across most filings: a headline number, a year-over-year trend line, a short narrative on barrier-report cadence, and a forward-looking commitment.
How to report upward
There are three audiences for accessibility findings inside any large operator, and each wants a different shape of the same number.
The engineering audience
Engineers want findings in raw WCAG vocabulary. Success criterion, severity, file reference, code snippet. They want the issue queue sorted by severity and filtered by component owner. They want a CI signal that fails the build when a regression lands. The Mueen issue queue is the artifact for this audience.
The program management audience
Program managers do not read WCAG vocabulary. They read VRP indicators. They want each finding tagged with the KPI it affects — Citizen Experience, Service Reach, Digital Inclusion — and they want the per-KPI delta from last quarter. A program manager files a single quarterly report; the audit needs to feed the relevant indicator boxes directly.
The board and ESG audience
The board wants a one-page summary: composite score, trend, top three risks, one-sentence forward commitment. The ESG submission wants a paragraph mapping work done to SDG 10.2 and 10.3 with quantitative evidence. Both audiences want the audit data already abstracted into narrative.
A worked example
The clearest way to show the multi-audience roll-up is with one finding moved through all three views.
A Mueen audit runs against a municipal e-service that handles construction permit applications. The audit produces a finding:
- Issue: The "submit application" call-to-action button uses a brand-green background with white text. Contrast ratio measures 2.9:1. WCAG 1.4.3 requires ≥ 4.5:1 for normal text.
- Severity: Serious. Affects every applicant attempting to complete a submission.
- Scope: Appears on the final step of the application flow, before payment. Estimated 12,000 monthly submissions touch this surface.
Same finding, three roll-ups:
Roll-up 1 — Engineering ticket
Filed in the team's project tool with the WCAG citation, the file reference (the brand button component in the design system), and a suggested fix (move to --mueen-green-deep which measures 9.1:1 against cream — already AAA). Severity tag drives priority. Owner is the design system team. Remediation window: 90 days (Serious).
Roll-up 2 — Digital Government VRP quarterly indicator
Tagged to the Citizen Experience sub-indicator of the Digital Government VRP. The program manager's quarterly report shows a one-point dip in the Citizen Experience sub-indicator for that service, attributable to this finding (alongside others). The remediation plan with named owner and date goes into the report's "open actions" section.
Roll-up 3 — Annual ESG report against SDG 10
The finding contributes to a paragraph in the parent ministry's integrated annual report: "We identified and remediated 14 accessibility barriers affecting an estimated 144,000 service interactions across the year. Our composite accessibility index moved from 71 to 83. Findings related to visual contrast accounted for the largest single category, fully remediated within the regulator's expected 90-day Serious-finding window." SDG 10.2 cited explicitly; quantitative evidence baked in.
One audit, three numbers move, no one re-translates the finding. The Mueen Vision 2030 overlay applies the tags automatically at audit time; the SDG 10 one-page summary is generated from the same audit data.
What this changes about the budget conversation
The pre-2024 framing of accessibility as compliance overhead — a cost line that protected the organization from regulatory exposure — does not survive contact with this reporting structure. Three reframings happen at once:
- Accessibility becomes a KPI line. Program managers carry it like they carry uptime or transaction volume. It has to move in the right direction.
- Accessibility becomes an ESG line. Analysts and investors ask about it. It appears on the same dashboard as carbon intensity and board diversity.
- Accessibility becomes a procurement gate. Tenders ask for the evidence pack. Operators without one lose the contract.
The budget conversation is no longer "should we spend on accessibility?" It is "which of the three KPI lines is this remediation budget moving?" That's a question the CFO can answer.