Skip to content
Web design 13 min read

Website accessibility in the UAE: what the rules require, what WCAG 2.2 AA means, and how to get an Arabic site there

By Manager & CEO, SmartTech Studio

Sooner or later someone asks. A tender mentions WCAG. A customer who uses a screen reader writes to say your booking form cannot be completed. Website accessibility in the UAE is a real topic, but most of what you find about it is written for the United States or Europe, quotes laws that do not apply here, and says nothing about Arabic.

This guide is for UAE business owners, marketing and IT managers, including those who sell to government. It covers what the official UAE texts say and whom they bind, what WCAG 2.2 and its levels mean in practice, the Arabic and right-to-left checks generic guides skip, an audit and fix workflow, mobile apps, and cost.

We build bilingual Arabic and English websites and apps, including a university platform in seven languages, three of them right-to-left. Everything below about laws and standards comes from the official pages in the sources. Where an official text is silent, we say so.

Does your website legally have to be accessible in the UAE?

It depends on who you are and whom you work for. The main official text is the National Policy for Digital Accessibility, issued by the Telecommunications and Digital Government Regulatory Authority (TDRA) in March 2024 and published on u.ae. It defines digital accessibility as the usability of digital products and services by people of determination and senior citizens “to the same degree, effectiveness and safety of use as by other groups”.

Article 3 sets the scope: all federal ministries, authorities and institutions; semi-government entities, consultants and private companies engaged in electronic transactions with a government entity; partners and contractors; and service providers, “particularly in the development of websites, electronic/digital services, service delivery channels, apps and systems for federal entities”. If you build, host or run a digital service for a federal entity, the policy reaches you through that contract.

For everyone else the wording is softer. Local government entities, semi-government entities and the private sector “should take this document into account, and exert the best efforts in compliance”. The policy also asks each federal sector regulator to check adherence with the private entities it licenses, and its objectives mention private companies providing public services in health, education and e-commerce.

Put plainly: a federal entity, or a company delivering a website or app to one, has a written requirement. A private company with no government work is encouraged, not ordered, and we have not found an official page that imposes WCAG on every private website in the UAE. Emirate-level government entities can set their own requirements, so read the tender rather than assume.

There is also the general law. The u.ae page on the rights of people of determination says Federal Law No. 29 of 2006 “protects the rights of people of determination and guarantees them the right to live with dignity”, and that special needs shall not be a reason to deprive anyone of rights and services. It sets no technical web standard, and we will not stretch it into one.

Which standard: WCAG 2.1 AA in the policy, WCAG 2.2 AA in practice

Annex 1 of the policy is blunt: “All public service sites must comply with Level AA of the WCAG 2.1”, plus W3C best practices and the mobile device guidelines. Article 12 requires every federal entity to publish an accessibility statement on its websites and apps that names the standard applied, “such as WCAG 2.1, as a minimum requirement”, lists inaccessible content and offers a technical support contact.

The UAE Design System at designsystem.gov.ae, built by TDRA for federal entities, targets WCAG 2.2 level AA. It explains why that is safe: WCAG 2.2 includes every WCAG 2.1 criterion except 4.1.1 Parsing, now obsolete, and adds nine new ones, so a site meeting 2.2 AA also meets the policy’s 2.1 AA requirement.

The W3C agrees. WCAG 2.2 became a W3C Recommendation on 5 October 2023, “content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0”, and it is now an approved ISO standard, ISO/IEC 40500:2025. Our advice for any new website or app, government or private: write “WCAG 2.2 level AA, in Arabic and English” into the specification.

A, AA and AAA: what the levels mean on a real page

WCAG rests on four principles: content must be perceivable, operable, understandable and robust. Under them sit testable success criteria, each at level A, AA or AAA. A page conforms at AA when it “satisfies all the Level A and Level AA success criteria”. In WCAG 2.2 that is 55 criteria, the figure the UAE Design System asks government sites to report against.

Level A is the floor: text alternatives for images (1.1.1), captions for prerecorded video (1.2.2), structure software can read (1.3.1), full keyboard operation (2.1.1), page language set in the code (3.1.1), labels on form fields (3.3.2) and errors described in text (3.3.1).

Level AA is where the measurable numbers appear. Normal text needs a contrast ratio of at least 4.5:1, large text at least 3:1 (1.4.3). Icons, input borders and focus indicators need 3:1 against adjacent colours (1.4.11). Text must resize to 200 percent without loss (1.4.4), and content must reflow at 320 CSS pixels wide without two-way scrolling (1.4.10). If a user sets line height to 1.5 times the font size, paragraph spacing to 2 times, letter spacing to 0.12 and word spacing to 0.16, nothing may be cut off (1.4.12). Keyboard focus must be visible (2.4.7), live video needs captions (1.2.4), and known corrections for form errors are suggested (3.3.3).

Level AAA is not a sensible whole-site target. The W3C says it “is not recommended that Level AAA conformance be required as a general policy for entire sites”. Pick individual AAA items instead. One UAE example: the policy asks for sign language for people with hearing impairments, and the UAE Design System maps that to 1.2.6 Sign Language (Prerecorded), a AAA criterion, for key service videos.

What WCAG 2.2 added, and why UAE sites trip over it

WCAG 2.2 added nine success criteria and removed 4.1.1 Parsing. Six of the nine are at level A or AA:

Focus Not Obscured (Minimum), 2.4.11, AA: a focused element must not be entirely hidden by content the site added, such as a sticky header, a cookie banner or a floating WhatsApp button.

Dragging Movements, 2.5.7, AA: sliders, maps and reorderable lists must also work with a single tap or click, unless dragging is essential.

Target Size (Minimum), 2.5.8, AA: targets are at least 24 by 24 CSS pixels, or spaced so a 24-pixel circle around each touches no other target, with exceptions such as links inside a sentence.

Consistent Help, 3.2.6, A: help that repeats across pages, such as a phone number, contact form or chat, stays in the same relative place.

Redundant Entry, 3.3.7, A: information already entered in the same process is filled in or offered for selection, not demanded twice.

Accessible Authentication (Minimum), 3.3.8, AA: no login step may rely on a cognitive function test, a task that requires the user to “remember, manipulate, or transcribe information”, unless there is an alternative, a helping mechanism, or the test is recognising objects or the user’s own content.

The other three, 2.4.12, 2.4.13 and 3.3.9, are AAA. The new criteria hit patterns common on UAE business sites: sticky headers with chat and WhatsApp buttons, image sliders, tiny footer icons, and multi-step forms that ask for the same Emirates ID or phone number twice.

The Arabic and right-to-left checks generic WCAG guides skip

The UAE Design System is direct about this: “UAE government websites serve users in Arabic and English, and both versions must be equally accessible”. It tells teams to test the Arabic version with a screen reader in Arabic and not to “assume it works because the English version does”. The Arabic half is often built last and tested least. These are the checks we run on it.

Arabic and bilingual accessibility checks, with the WCAG 2.2 criteria behind them
AreaWhat to checkWCAG 2.2
Language and directionlang="ar" and dir="rtl" on Arabic pages; English phrases inside Arabic text (and the reverse) carry their own lang, so the screen reader switches voice3.1.1 (A), 3.1.2 (AA), 1.3.2 (A)
Mirrored layout and focus orderTab order follows the right-to-left visual order; directional icons flip; focused elements are not hidden by sticky bars on either side1.3.2 (A), 2.4.11 (AA)
Arabic type size and line heightArabic body text legible at its real size; diacritics and tall letters not clipped at 200 percent zoom or with text spacing overrides1.4.4 (AA), 1.4.12 (AA)
Arabic alt textWritten in Arabic by someone who knows what the image shows, not machine-translated; decorative images have empty alt1.1.1 (A)
Captions for Arabic videoClosed captions in WebVTT, with Arabic and English tracks the viewer can switch, not text burned into the video1.2.2 (A), 1.2.4 (AA) for live
Bilingual forms and errorsVisible labels in the page language; errors in the form’s language, in text, next to the field, with a suggestion where known3.3.1 (A), 3.3.2 (A), 3.3.3 (AA)
CAPTCHA and loginNo distorted-text puzzle as the only way in; password managers and paste work; a one-time link or code is offered3.3.8 (AA), 1.1.1 (A)
Brand coloursEvery brand colour used for text, buttons, icons or focus rings measured against its real background, in both versions1.4.3 (AA), 1.4.11 (AA)
Screen reader in ArabicKey journeys completed with VoiceOver, TalkBack and NVDA set to Arabic; every control has an Arabic name; headings make sense read aloud4.1.2 (A), 1.3.1 (A)

On type size: WCAG defines large text as at least 18 point, or 14 point bold, and allows an “equivalent size” for fonts such as Chinese, Japanese and Korean, but gives no figure for Arabic. Many Arabic typefaces look smaller than Latin ones at the same nominal size, so do not assume an 18-point Arabic heading counts as large for contrast. When in doubt, hold Arabic text to 4.5:1.

On mixed text: Arabic pages are full of Latin brand names, emails, prices and phone numbers, and users may type Arabic-Indic or Western digits. Mark foreign phrases, let fields accept both digit sets, and listen to how the screen reader reads a +971 number. For the layout side, see our guide to bilingual RTL web design. We met all of this on the Al-Azhar University platform, where three of seven languages run right-to-left.

Why accessibility pays even when no rule requires it

The policy’s definition of people of determination is broader than many owners expect: any “permanent or temporary, total or partial” impairment in physical, sensory, mental, communicative, educational or psychological capabilities. That includes a customer with a broken wrist using only a keyboard, a visitor who zooms every page to 200 percent, and someone who cannot hear your hero video. The policy gives senior citizens, defined as people aged sixty or over, the same right of access.

Government work is the clearest commercial reason. Because Article 3 reaches contractors building websites and apps for federal entities, accessibility is part of what you sell the moment you bid, and a supplier with a WCAG 2.2 AA test report in Arabic and English is easier to choose. The same goes for an Arabic version of your site: government buyers expect both languages to work equally well.

There is an overlap with search, without any promise of rankings. Google’s image documentation calls alt text the most important attribute for image metadata, says it “also improves accessibility for people who can’t see images”, and uses it to understand what an image shows. Headings, descriptive links, captions and transcripts give people and search engines the same thing: content as text. It also fits the work in our guide to website speed and Core Web Vitals.

One warning about overlay widgets, the toolbars that promise compliance with one line of script. The UAE Design System says on-site tools such as a read-aloud player or font size controls “never replace meeting WCAG 2.2 level AA”, must be accessible themselves, and must not interfere with the assistive technology people already use. A widget is not an accessibility plan.

How to audit and fix an existing website

Start with the journeys that matter, not a tool: finding a service, reading a price, the contact or booking form, payment, login. Test those in both languages first.

Step 1, automated scan. Run Lighthouse or axe across your main templates to catch missing alt text, missing labels, low contrast and missing page language. The UAE Design System notes that automated testing “finds only some issues”, so a clean score starts the audit; it does not end it.

Step 2, keyboard only. Use Tab, Shift+Tab, Enter, Space and the arrow keys. Can you reach every link, menu, slider and field? Is focus always visible, never hidden behind the header or chat button? Can you close every pop-up? Repeat in Arabic, because the focus order differs.

Step 3, screen readers. The UAE Design System recommends testing key journeys with at least one screen reader on desktop and one on mobile, in both languages: in practice NVDA on Windows, VoiceOver on Mac or iPhone, and TalkBack on Android, with the device set to Arabic for the Arabic pass. Listen for unlabelled buttons, images read by file name, English read in an Arabic voice, and errors that appear but are never announced.

Step 4, zoom, spacing and colour. Zoom to 200 and 400 percent, apply the WCAG text spacing values, and measure every colour pair. Arabic text and RTL layouts often break first here.

Step 5, fix at the source. Group findings by criterion, fix level A before AA, and fix shared components rather than single pages. The UAE Design System says the same: use components built on native HTML, and do not strip the markup that carries keyboard support and screen reader information.

Step 6, re-test and publish. Re-test the fixed journeys, publish an accessibility statement naming the standard, languages tested, known limitations and review date, and add automated checks to your release process. Where you can, test with people of determination and senior citizens, as the UAE Design System asks.

Mobile apps: what Apple and Google ask for

The policy covers apps too, and both platform owners publish concrete guidance.

Apple’s Human Interface Guidelines give a default control size of 44 by 44 points on iPhone and iPad, with 28 by 28 as the minimum, and treat spacing as being as important as size. Apps should let people enlarge text by at least 200 percent, through Dynamic Type or custom controls. Apple’s contrast table follows WCAG AA: 4.5:1 for text up to 17 points, 3:1 for larger or bold text. It also asks you to describe the interface for VoiceOver and to cut automatic, repetitive animation when Reduce Motion is on.

Android’s guide recommends touch targets of at least 48 by 48 dp, contrast of at least 4.5:1 for text smaller than 18sp (or bold below 14sp) and 3:1 otherwise, and a content description for each element so TalkBack can announce it. Descriptions state purpose, “Submit” rather than “Submit button”, and decorative elements are hidden from accessibility services. Google points to the Accessibility Scanner app for common problems.

For a bilingual Gulf app, add the Arabic pass: set the phone to Arabic, run every key flow with VoiceOver and TalkBack, and check Arabic labels, a logical reading order on mirrored screens, and that large system text does not truncate Arabic buttons. Do this before submission; see our guide to publishing an app on the App Store and Google Play.

What accessibility adds to a project, and how we work

We will not quote a percentage, because honest numbers depend on the site. Built in from the start, accessibility is mostly decisions: a palette checked for contrast before the brand is applied, components on native HTML, visible labels, captions planned with the video, and Arabic and English test passes in the schedule. Retrofitted, the same work means touching every template, re-testing, and sometimes redesigning brand colours that fail contrast. It is cheapest built in from the start.

If you need it, for a government contract or for your customers, we recommend writing WCAG 2.2 level AA in Arabic and English into the specification and test plan from the first sprint, and testing with keyboards and screen readers as well as automated tools, rather than relying on an overlay widget. As in every build, the domain and code stay in your name, and fixes are checked on a separate staging environment.

Our website builds start from AED 3,000, from AED 5,000 with business email and hosting, and from AED 8,000 for e-commerce. Mobile apps start from AED 10,000 cross-platform and from AED 20,000 for a full app product. All prices exclude VAT. If you are comparing suppliers, add accessibility to the questions in our guide to choosing a web design company in the UAE: which WCAG version and level, which languages, which screen readers, and can you see a report.

Sources

FAQ

Is there a fine if my private company website is not accessible?

The National Policy for Digital Accessibility does not set fines. It binds federal entities and the contractors and service providers that build their digital services, and encourages the private sector to make its best efforts to comply. Check your sector regulator and any contract you sign, which may add requirements of their own.

Is WCAG 2.1 AA enough for a UAE government tender?

It is the minimum the federal policy names for public service websites. The UAE Design System targets WCAG 2.2 AA, which includes every 2.1 criterion except the obsolete 4.1.1 and adds nine more, so building to 2.2 AA satisfies both. Always follow the version written in the tender itself.

Will an accessibility widget or overlay make my website compliant?

No. A widget does not fix missing labels, broken keyboard access or poor structure in the code underneath. The UAE Design System says on-site tools never replace meeting WCAG 2.2 level AA, must be accessible themselves and must not interfere with the screen readers and magnifiers people already use.

Do I need to publish an accessibility statement?

Federal entities must, on their websites and apps, under Article 12 of the policy. For a private company it is good practice rather than a written duty: state the WCAG version and level you test against, the languages tested, known limitations, a contact for problems and the date of the last review.

العربية