Guidelines

Main site

Typography Colour system Iconography Imagery Content Layout & spacing Actions and input Mobile applications Accessibility
Home Design guidelines Accessibility

Accessibility

When websites and digital services are designed and built thoughtfully, everyone can use them, including people of determination and senior citizens. Accessibility is not only a matter of inclusion; it benefits individuals, government entities and society as a whole.

The standard

The UAE Design System is built accessibility first. It follows the guidance of the W3C Web Accessibility Initiative (WAI) and targets level AA of the Web Content Accessibility Guidelines (WCAG) 2.2.

The National Policy for Digital Accessibility requires all public service websites to meet WCAG 2.1 level AA as a minimum. WCAG 2.2, published on 5 October 2023, includes every success criterion of WCAG 2.1 (published on 5 June 2018), except 4.1.1 Parsing, which is now obsolete, and adds nine new criteria. A website that meets WCAG 2.2 level AA therefore also meets the policy's WCAG 2.1 level AA requirement.

Throughout this page, each requirement is linked to the WCAG success criterion that defines it, with its conformance level: A, AA or AAA.

UAE National Digital Accessibility Policy

The National Policy for Digital Accessibility, issued by the Telecommunications and Digital Government Regulatory Authority (TDRA) in March 2024, supports digital transformation and service efficiency in the UAE. It ensures digital inclusion for all segments of society, including people of determination and senior citizens.

The policy aims to give people of determination and senior citizens easy access to all digital products and efficient access to digital services, while supporting the government's transition to integrated digital platforms. It follows the principle of the UAE Government Charter for Future Services that humans come first, and that no one should be left behind.

Read about the National Digital Accessibility Policy on u.ae

Key takeaways from the policy

Who it applies to

All federal ministries, authorities and institutions, and the semi-government entities, contractors and service providers that build or run their digital services. Local government and private sector entities are encouraged to comply. (Article 3)

The minimum standard

Public service websites must meet WCAG 2.1 level AA, follow W3C best practices and the mobile device guidelines, and work across commonly used browsers and devices. (Article 10, Annex 1)

Who it protects

People of determination, with any permanent or temporary impairment, and senior citizens, defined as people aged 60 or over. (Article 1)

Nothing about us without us

No decision about digital accessibility should be made without involving people of determination and senior citizens, and services must follow the principles of inclusive design and non-discrimination. (Article 4)

A Digital Accessibility Officer

Every federal entity must appoint a Digital Accessibility Officer, or assign the role to an existing department, to supervise the action plan and report to TDRA. (Article 6, Annex 2)

A published accessibility statement

Every federal entity must adopt its own accessibility policy and publish an accessibility statement on its websites and mobile apps. (Article 12)

Accessible service journeys

Entities must offer multiple service channels, make sure accessibility features do not burden the journey, and include accessibility information in their service cards. (Article 11)

Training and monitoring

Entities must train their employees, including on sign language, provide guidance for users on accessibility tools, and report compliance, which TDRA reviews annually through the Digital Government Enablers Indicators. (Articles 6, 8 and 14)

What your accessibility statement must include

Article 12 of the policy requires every federal entity to publish a digital accessibility statement on its websites and mobile apps. The statement must describe the level of accessibility, indicate any inaccessible content, and include:

  • your commitment to digital accessibility for people of determination and senior citizens;
  • the accessibility standard you apply, such as WCAG 2.1, as a minimum requirement;
  • how to contact technical support if users face an issue;
  • a clear indication of any accessibility limitations of the website or service, so that users do not waste effort;
  • the measures taken to ensure accessibility;
  • the technical prerequisites, such as the browsers that support the accessibility features;
  • your compliance with applicable national and local laws and policies on digital accessibility.

Link to the statement from the footer of every page, and keep it up to date.

Technical features in the policy

Annex 1 of the policy lists the features that public service websites should offer. Most are met by conforming to WCAG and by supporting the assistive technology people already use. The table below maps each feature to the WCAG 2.2 success criteria that cover it.

Policy feature (Annex 1)How to meet itWCAG 2.2 criteria

Text reader

Make all content readable by screen readers and read-aloud tools: text alternatives, correct structure, and accessible names for controls.

1.1.1 (A), 1.3.1 (A), 4.1.2 (A)

Sign language

Provide sign language interpretation for important pre-recorded video, such as service guides.

1.2.6 (AAA)

Speech recognition

Make the visible label part of each control's accessible name, so that users can activate it by saying what they see.

2.5.3 (A)

Image description

Give every informative image, logo and icon a text alternative.

1.1.1 (A)

Text colour

Meet contrast ratios, never use colour as the only way to convey information, and let users apply their own colours.

1.4.1 (A), 1.4.3 (AA), 1.4.11 (AA), 1.4.8 (AAA)

Font size and magnification

Let text be resized to 200% and content reflow at 320 CSS pixels wide, without loss of content or function.

1.4.4 (AA), 1.4.10 (AA), 1.4.12 (AA)

Keyboard navigation and shortcuts

Make every function work with a keyboard, in a logical order, with a visible focus that is never hidden. Single-key shortcuts must be adjustable.

2.1.1 (A), 2.1.2 (A), 2.1.4 (A), 2.4.3 (A), 2.4.7 (AA), 2.4.11 (AA)

Navigating portals

Organise content by topic, offer more than one way to find a page, and let users skip repeated blocks.

2.4.1 (A), 2.4.5 (AA), 2.4.6 (AA)

Forms accessibility

Label every field, identify errors in text, suggest corrections, and do not ask for the same information twice.

3.3.1 (A), 3.3.2 (A), 3.3.3 (AA), 3.3.7 (A)

Notifications and feedback

Write messages in clear language, and announce status messages to screen readers without moving focus.

3.3.1 (A), 4.1.3 (AA)

Understandable content

Use plain language, explain abbreviations, and provide easy-to-read versions of complex content.

3.1.4 (AAA), 3.1.5 (AAA)

How-to videos

Caption every video, provide audio description and a transcript.

1.2.2 (A), 1.2.5 (AA)

Communication with users

Offer a way to report accessibility problems and get help, in the same place on every page.

3.2.6 (A)

Browser compatibility and file formats

Use valid, semantic code that works across browsers and assistive technologies, and publish documents as accessible, tagged files or as HTML.

4.1.2 (A), 1.3.1 (A)

On-site tools do not replace conformance. People of determination already use assistive technology on their own devices, such as screen readers, magnifiers and Braille displays. If you add on-site tools, such as a read-aloud player or font size controls, to meet the policy, they must themselves be accessible, must not interfere with the user's assistive technology, and never replace meeting WCAG 2.2 level AA.

Accessibility in the guidelines

Every guideline in the design system includes accessibility guidance, so that entities can build consistent, accessible and well-structured websites. If you build your website following the guidelines, inclusion is part of its foundation.

Quick checks

Run these checks while you build and before every release. They do not replace a full audit, but they catch the most common problems.

CheckHow to testWCAG 2.2

Zoom

Zoom the browser to 200%: all text is readable and nothing overlaps or is cut off. Then zoom to 400% on a 1280 px wide window: the page reflows to one column without horizontal scrolling.

1.4.4 (AA), 1.4.10 (AA)

Text spacing

Apply line height 1.5, paragraph spacing 2×, letter spacing 0.12× and word spacing 0.16× the font size: no text is clipped or overlaps.

1.4.12 (AA)

Contrast

Text has a contrast ratio of at least 4.5:1 (3:1 for large text); icons, borders of inputs and focus indicators at least 3:1.

1.4.3 (AA), 1.4.11 (AA)

Keyboard only

Put the mouse away and press Tab through the page: every interactive element is reachable in a logical order, has a visible focus indicator that is not hidden by sticky elements, and nothing traps the focus.

2.1.1 (A), 2.1.2 (A), 2.4.3 (A), 2.4.7 (AA), 2.4.11 (AA)

Skip link and titles

The first Tab reveals a "Skip to content" link, and each page has a unique, descriptive title.

2.4.1 (A), 2.4.2 (A)

Screen reader

Navigate with VoiceOver, Narrator, TalkBack or NVDA: headings form a logical outline, images are described, and every control announces its name, role and state.

1.1.1 (A), 1.3.1 (A), 4.1.2 (A)

Language

The page has lang="ar" or lang="en", and phrases in the other language are marked with their own lang.

3.1.1 (A), 3.1.2 (AA)

Target size

Buttons, links and icon-only controls have a clickable area of at least 24 × 24 CSS pixels, or enough space around them.

2.5.8 (AA)

Forms

Every field has a visible label, errors are described in text next to the field, and personal fields use autocomplete, such as autocomplete="email".

1.3.5 (AA), 3.3.1 (A), 3.3.2 (A)

Time limits

If a session or form times out, users are warned and can extend the time.

2.2.1 (A)

Accessibility in components

Every component in the design system is built and tested for accessibility. Use components with the markup provided, and do not rebuild them with your own styles or remove parts of the recommended HTML structure, as this can remove keyboard support, focus management or the information screen readers rely on. Each component page documents its accessibility features, keyboard support and the ARIA attributes it needs.

Use components built on native HTML

Use ARIA only when native HTML cannot do the job, and never use it to turn a generic element into a control. A native <button> or <a> is focusable, works with the keyboard and announces its role automatically; a <div> styled as a button does none of this, even with ARIA attributes added (2.1.1 Keyboard, A; 4.1.2 Name, Role, Value, A).

The design system components are built on these native elements. aegov-button renders a native <button> and forwards aria-* attributes to it, so use aegov-button for actions and aegov-link for navigation, rather than styling your own elements.

<aegov-button aria-expanded="false" aria-controls="filters">
  Filter services
</aegov-button>
aegov-button renders a native button and forwards aria-* attributes to it
<div class="btn" onclick="openFilters()"
     aria-labelledby="filter-label">
  <span id="filter-label">Filter services</span>
</div>
A div cannot be reached or activated with the keyboard

Supporting assistive technology

True accessibility is not offering users a tool; it is working with the tools they already use. People of determination use assistive technology every day, across many websites, so a website that follows the standards works with it without any extra steps.

Screen readers are built into every major operating system: VoiceOver on Apple devices, Narrator on Windows and TalkBack on Android. NVDA and JAWS are also widely used on Windows. Braille displays, screen magnifiers, switch devices and voice control all rely on the same information: correct semantic HTML and, where needed, ARIA.

  • Test your key service journeys with at least one screen reader on desktop and one on mobile, in both Arabic and English.
  • Explain in your accessibility statement which assistive technologies and browsers you have tested with, as Article 12 of the policy requires.
  • Involve people of determination and senior citizens in usability testing, following the policy principle of "nothing about us without us".

Accessibility in media

Content on websites is consumed as text, images, audio and video, and each needs an accessible alternative.

WebVTT is the standard format for captions and subtitles on the web. Prefer closed captions, which users can turn on or off and switch between Arabic and English, over captions burned into the video. The WAI guide Making Audio and Video Media Accessible explains how to produce them.

Accessibility in two languages

UAE government websites serve users in Arabic and English, and both versions must be equally accessible.

  • Set the language of each page with the lang attribute, so that screen readers use the right voice and pronunciation (3.1.1 Language of Page, A).
  • Mark words and phrases in the other language with their own lang attribute (3.1.2 Language of Parts, AA).
  • Set dir="rtl" on Arabic pages, so that the reading and focus order follow the Arabic layout (1.3.2 Meaningful Sequence, A).
  • Test the Arabic version with a screen reader in Arabic; do not assume it works because the English version does.

Testing and keeping up to date

Accessibility is an ongoing commitment, not a one-off check. Browsers, assistive technologies and standards evolve, and websites must keep up with them.

  • Combine automated testing, which finds only some issues, with manual testing using the keyboard and screen readers, and with usability testing involving people of determination and senior citizens.
  • Test every release, and fix accessibility issues with the same priority as other defects.
  • The design system will adopt new versions of WCAG and add accessibility improvements to its components over time. Keep your projects up to date with the latest version of the design system to benefit from these updates.
  • Do not use any pattern or third-party component that does not meet WCAG 2.2 level AA on a government service. If a component is not yet accessible, the design system marks it as such, and it must not be used for public services until it conforms.

Include an accessibility statement

Publish an accessibility statement on your website and link to it from the footer of every page. Article 12 of the National Policy for Digital Accessibility requires one (see "What your accessibility statement must include" above). The points below build on those requirements, so that your statement tells users honestly, in plain language, how accessible the website is today. Your statement must include:

  1. The standard you test against. Name the WCAG version and conformance level that the website is tested against, for example WCAG 2.2 level AA.
  2. The languages you have tested. List every language the website is tested in, such as Arabic and English, and confirm that each version is equally accessible.
  3. Your conformance status. Report how the website conforms to the 55 level A and AA success criteria of WCAG 2.2, for example as the number and percentage of criteria met with no known failures.
  4. A clear commitment. State your commitment to making the website accessible to people of determination, with any permanent or temporary impairment, and to senior citizens, and name the standard you apply.
  5. Testing with assistive technology. Confirm that the website has been tested with assistive technology, such as screen readers and voice control, and that the code includes what these tools need: a text alternative for every image, a name for every control, and correct headings, landmarks and lists (1.1.1 Non-text Content, A, 1.3.1 Info and Relationships, A, 4.1.2 Name, Role, Value, A).
  6. Testing with a keyboard only. Confirm that every page and feature has been tested with a keyboard alone, and that focus is always visible (2.1.1 Keyboard, A, 2.4.7 Focus Visible, AA).
  7. Testing colour contrast. Confirm that text has been tested for a contrast ratio of at least 4.5:1, or 3:1 for large text (1.4.3 Contrast (Minimum), AA).
  8. Testing at 200% zoom. Confirm that pages have been tested at a zoom level of 200%, with no loss of content or functionality (1.4.4 Resize Text, AA, 1.4.10 Reflow, AA).
  9. Respecting reduced motion. Confirm that the website follows the reduced motion setting on the user's device, and that moving content can be paused or stopped (2.2.2 Pause, Stop, Hide, A, 2.3.3 Animation from Interactions, AAA).
  10. An accessible search. Confirm that search can be found and used with a keyboard and a screen reader: the search field has a label, the number of results is announced, and users can move through the results without a mouse (2.4.5 Multiple Ways, AA, 4.1.3 Status Messages, AA).
  11. Known limitations. Publish an accurate list of what is not accessible or not covered by the statement, and explain why, so that users do not waste effort. Update the list as issues are fixed.
  12. Feedback and support. Explain how people can contact you about any accessibility barrier they face, or ask for content in a different format, for example by email or through a support channel.
  13. The date of the last update. Show the date when the statement was last updated. Review it at least once a year, and whenever the website changes significantly.

See the accessibility statement of this website for an example that covers each of these points.