Saudi SASO Launches ICT-2026 AI Review System

Saudi Arabia’s Standards, Metrology and Quality Organization (SASO) launched the ICT-2026 AI-powered review platform on May 17, 2026. The move significantly accelerates UI localization approval timelines for ICT products entering the Saudi market—but introduces a new, non-negotiable compliance requirement: Arabic text-to-speech (TTS) synthesis coupled with dialectal semantic understanding. This dual-layer voice functionality is now mandatory for certification, reshaping technical, operational, and strategic planning across the global ICT supply chain serving the Kingdom.

Event Overview

On May 17, 2026, SASO officially activated the ICT-2026 AI review platform. The system reduces UI localization review cycles for end-user devices—including AI-enabled terminals, interactive flat panels, and self-service kiosks—to 15 calendar days. Concurrently, SASO introduced a new mandatory testing requirement: all submitted products must pass evaluation of Arabic TTS voice output and regional Arabic dialect comprehension (e.g., Najdi, Hijazi, Gulf Arabic). Products that complete UI translation but fail voice module validation will not receive the SASO Certificate of Conformity (CoC), regardless of other compliance status.

Industries Affected

Direct Trade Enterprises: Exporters and distributors targeting the Saudi market face immediate timeline compression in pre-market clearance—but also heightened technical risk. Previously, UI-only localization could support parallel certification and launch planning; now, voice module readiness must be confirmed before submission. Delays in Arabic TTS integration or dialect testing may cascade into missed Q3 2026 product launches or contractual penalties tied to CoC issuance dates.

Raw Material & Component Suppliers: Providers of voice ICs, embedded speech SDKs, and multilingual ASR/TTS chipsets are seeing increased demand—particularly for solutions certified against GCC Arabic dialect profiles. However, suppliers lacking documentation traceable to SASO’s newly published ICT-2026 test protocols (e.g., ISO/IEC 20248 Annex D addendum) may find their components excluded from approved BOMs unless requalified by OEMs.

Manufacturing & ODM/OEM Firms: Contract manufacturers must now embed Arabic voice validation checkpoints earlier in NPI (New Product Introduction) workflows—not just during final QA. Firmware partitioning, audio calibration for regional phoneme sets, and runtime dialect switching logic are no longer optional features but baseline requirements. This increases firmware development lead time and necessitates cross-functional coordination between UI, voice, and regulatory engineering teams.

Supply Chain & Certification Service Providers: Third-party labs and conformity assessment bodies must obtain updated accreditation under SASO’s ICT-2026 framework by August 2026 to issue valid test reports. Firms currently relying on legacy Arabic language verification methods (e.g., static script checks or MSA-only TTS) are at risk of report rejection. Additionally, logistics partners handling pre-certified stock must now verify voice firmware versioning and dialect flagging in shipment manifests—introducing new data reconciliation steps.

Key Considerations & Recommended Actions

Validate Voice Module Against SASO’s Dialect Test Corpus

Do not assume MSA (Modern Standard Arabic) compliance suffices. SASO’s ICT-2026 test suite includes phonetic and syntactic samples drawn from at least three major Gulf dialects. Companies should request access to the official test corpus via SASO’s e-portal or authorized testing partners—and conduct internal dry-runs prior to formal submission.

Reassess Localization Timelines Holistically

The 15-day UI review window applies only after full submission—including verified voice binaries, dialect metadata, and signed TTS vendor attestations. Teams should treat voice integration as a critical path item, not a post-UI task. Buffer at least 4–6 weeks for dialect tuning and regression testing before targeting the 15-day window.

Update Technical Documentation Packages

SASO now requires explicit declaration of TTS engine version, supported Arabic dialects (with ISO 639-3 codes), and phoneme mapping tables in the technical file. Legacy user manuals and firmware release notes lacking this granularity may trigger queries or rejection—even if UI text is fully localized.

Editorial Perspective / Industry Observation

Observably, SASO’s ICT-2026 rollout signals a deliberate shift from linguistic surface compliance toward functional accessibility—aligning with Vision 2030’s emphasis on inclusive digital public services. Analysis shows this is less about ‘adding another checkbox’ and more about enforcing real-world usability for non-MSA speakers, particularly in government-facing kiosks and education terminals. From an industry standpoint, it’s better understood as a de facto standardization lever: firms investing early in dialect-aware voice stacks gain faster time-to-market not just in Saudi Arabia, but across broader GCC markets where similar frameworks are under discussion.

Conclusion

The ICT-2026 AI review system marks a structural inflection point—not merely a procedural update. It redefines what constitutes ‘market-ready’ for ICT hardware in Saudi Arabia: UI fluency alone is insufficient without audible, intelligible, and regionally grounded Arabic interaction. For global vendors, this represents both a compliance hurdle and a strategic opportunity to build differentiated, locally resonant user experiences.

Source Attribution

Official announcement: SASO ICT Division Bulletin No. ICT/2026-05 (published May 17, 2026, on www.saso.gov.sa).
Test protocol reference: SASO ICT-2026 Annex A (Arabic TTS & Dialect Validation Framework), v1.2.
Note: SASO has indicated plans to extend ICT-2026 requirements to IoT gateways and smart home controllers in Q4 2026—details pending formal consultation.