Qatar

Qatar's e-Accessibility and Mada — preparing before you operate.

The MOTC checklist Mueen uses to ready Gulf operators for Qatari procurement. Includes the bilingual flow audit template.

9 min read · Updated 19 May 2026

A Gulf bank operating in three countries discovers, three days before a Qatari tender deadline, that its accessibility statement is English-only, its barrier-report email has no published SLA, and its retail banking app has never been tested against the Mada switch-access protocol. The pre-existing WCAG audit it relies on in Saudi Arabia is necessary but not sufficient. This article is the checklist we wish the bank had been given six months earlier — what Qatar's e-Accessibility regime actually requires, what Mada adds on top, and how to tell when each one applies.

The MOTC e-Accessibility Policy in brief

The Qatar Ministry of Communications and Information Technology (MOTC) administers the e-Accessibility Policy. The policy applies directly to every Qatari government digital service. It is also increasingly cited by the Qatar Central Bank for financial services and by the Communications Regulatory Authority for telecom customer channels. In practice, any operator competing for Qatari public-sector or regulated-private contracts will see MOTC's checklist in the tender document.

The policy assumes WCAG 2.2 Level AA as its technical baseline. On top of that baseline, it adds Qatar-specific provisions that are not in WCAG and that automated tooling alone cannot verify:

What Mada certification adds

Mada — the Qatar Assistive Technology Center — administers a separate certification program that goes beyond the MOTC policy. Mada certification is not the same thing as MOTC compliance; the two are layered. MOTC is the floor; Mada is the badge.

Mada certification adds the following on top of WCAG 2.2 AA:

When to seek Mada certification versus rely on WCAG AA + MOTC

This is the question that comes up first in every Qatari engagement, so it's worth being concrete about the answer.

You need Mada certification when:

WCAG 2.2 AA + MOTC compliance is sufficient when:

The pragmatic sequence for most enterprise operators: get to WCAG 2.2 AA + MOTC compliance first; layer Mada on the specific surfaces where the marketing or procurement case justifies the additional work.

The MOTC evidence pack

For any Qatari government tender citing the e-Accessibility Policy — and many do, by reference — the evidence pack expected at submission is:

The single most common reason MOTC submissions get bounced for shape, in our experience: the accessibility statement exists on the website but is English-only, or links to a 404, or has no date of last review. The fix is small; the cost of missing it at submission is large.

Bilingual gotchas specific to Qatar

Qatari Arabic shares the vast majority of its conventions with Modern Standard Arabic as used across the Gulf, but a handful of patterns recur in Qatari procurement reviews that we don't see flagged as often in Saudi audits.

Qatari numeral conventions in financial flows

Qatar's banking and government services frequently mix Western Arabic numerals (0123456789) and Eastern Arabic numerals (٠١٢٣٤٥٦٧٨٩) depending on the field. The accessibility expectation is that the numerals match the user's stated locale preference, not the document author's preference. A Qatari riyal amount displayed in mixed numerals — Western digits inside Arabic copy without isolation — fails both the WCAG 1.3.1 structure test and the MOTC bilingual provision.

The fix is to wrap embedded Western-numeral content in a <bdi> element or in <span dir="ltr">, so the bidirectional algorithm renders it correctly and the screen reader reads it as digits rather than as RTL-mangled text.

<!-- Currency amount inside Arabic copy -->
<p>
  ﺗﺑﻠﻎ ﺍﻟﻘﯾﻣﺔ ﺍﻹﺟﻣﺎﻟﯾﺔ
  <bdi dir="ltr">1,250.00 QAR</bdi>
</p>

Mixed-direction content in financial confirmations

Confirmation screens in banking flows — "you are about to transfer X to account Y on date Z" — routinely intermix Arabic narrative copy with Western-numeral account numbers, Latin-script SWIFT codes, and Arabic recipient names. The mixed-direction handling decides whether a screen reader can read the confirmation correctly. We see Qatari banking apps fail this regularly because the surrounding Arabic copy is bidirectional but the account number lives inside an unisolated <span>.

The language-switcher behavior

The MOTC policy expects that when a user toggles the language switcher mid-flow, they land on the equivalent page in the other language — not a home page, not a 404. For multi-step flows, the state should travel with the user across the toggle. Single-page apps with hash-routed localization tend to handle this correctly; legacy server-rendered apps with separate /en/ and /ar/ trees often do not.

Form validation in the user's locale

A surprisingly common failure: Arabic-labeled forms emit English validation messages because the validation library was configured English-only. The fix is configuration, not engineering, but the audit catches it every time. Same point applies to error toasts and ARIA-live announcements — they must be in the user's locale.

Common patterns we see across Qatari banking, government, and telecom

The audit findings cluster by sector. The patterns below repeat enough that we consider them sector-level diagnostics.

Banking

Government

Telecom

The pre-launch checklist for operators new to Qatar

If you are a Gulf operator preparing to bid on a Qatari tender or to launch a service in Qatar, this is the sequence we run with our customers:

  1. Baseline audit against WCAG 2.2 AA on every in-scope surface — web, mobile, authenticated flows. Get the score.
  2. Layer the MOTC additions — bilingual parity audit, accessibility-statement publication, barrier-report SLA commitment.
  3. Decide on Mada certification per the rule above. If yes, layer the switch-access, voice-control, magnification, and reading-mode tests.
  4. Assemble the evidence pack in the MOTC-expected shape: signed PDF, accessibility statement, contact route, remediation plan, statement of independence.
  5. Commit to a re-audit cadence — at least every two years for services scoring above threshold; annually for services below. Quarterly internal monitoring between formal audits.

The work is sequenced, not parallel — each step depends on the previous one. Most operators arriving in Qatar from Saudi Arabia find that step 1 is largely done (the DGA work transfers) but steps 2 and 3 are net new.