Compliance · Standards guide

Accessibility standards, made simple

Every type of digital content has an international accessibility standard. This page shows which standard applies to websites, apps, PDFs, Word, Excel and PowerPoint files, video and e-books, what each one checks, and which version is the latest.

Last reviewed:

Choose a type of content

Pick the kind of digital content you publish to see the standards that apply, what gets checked and the latest versions.

WCAG: the standard behind everything

The Web Content Accessibility Guidelines (WCAG) from the W3C are the base for almost every accessibility law and policy in the world, including the UAE National Digital Accessibility Policy. They are built on four simple principles.

  • PPerceivable

    People can see or hear the content: text alternatives for images, captions for video, enough colour contrast.

  • OOperable

    People can use it with a keyboard, voice or switch, with enough time and nothing that flashes dangerously.

  • UUnderstandable

    Text is clear, pages behave in a predictable way, and forms help people avoid and fix mistakes.

  • RRobust

    Content works with assistive technology such as screen readers, today and in the future.

Three levels of conformance

  • Level A

    The minimum. Without it, some people cannot use the content at all.

  • Level AA Target

    The level that laws and policies ask for, including in the UAE, USA, UK, Canada and the EU.

  • Level AAA

    The highest level. Good to reach where possible, but not required for whole websites.

How WCAG has grown

  1. 1999WCAG 1.0The first guidelines
  2. 2008WCAG 2.0Became ISO/IEC 40500:2012
  3. 2018WCAG 2.1Added mobile and low vision
  4. 2023WCAG 2.29 new success criteria
  5. 2025ISO/IEC 40500:2025WCAG 2.2 becomes an ISO standard
  6. DraftWCAG 3.0Working draft, not yet for use

Websites and web apps

Public websites, portals, e-services, online forms and web applications.

  • HTML
  • Web apps
  • Portals

What gets checked

  • Text alternatives for images and icons
  • Colour contrast of at least 4.5:1 for normal text
  • Everything works with the keyboard only, with a visible focus
  • Clear headings, labels and page titles
  • Forms with labels, help and clear error messages
  • Captions and transcripts for video and audio
  • Content still works when zoomed to 200% and on small screens
  • Works with screen readers such as NVDA, JAWS and VoiceOver

Arabic content tip

Set the page language to Arabic (lang="ar") and direction right-to-left (dir="rtl"), and mark English words inside Arabic text with lang="en" so screen readers pronounce them correctly.

Back to all content types

Mobile apps

Native and hybrid apps on iPhone, iPad and Android phones and tablets.

  • iOS
  • Android

What gets checked

  • Every button and icon has a spoken label
  • Touch targets are big enough to tap easily
  • Works with VoiceOver (iPhone) and TalkBack (Android)
  • Supports larger text and bold text settings
  • Works in portrait and landscape
  • No gestures that cannot be done another way
  • Good colour contrast in light and dark mode

Arabic content tip

Test with VoiceOver and TalkBack set to Arabic. Make sure layouts mirror correctly in right-to-left, and that every button has a clear Arabic label.

Back to all content types

PDF documents

Reports, forms, guides, policies and any document shared as PDF.

  • PDF

What gets checked

  • The PDF is tagged (headings, lists, tables, figures)
  • Correct reading order
  • Alternative text for images and charts
  • Tables have header cells
  • Document title and language are set
  • Bookmarks for long documents
  • Forms have labels and work with the keyboard
  • Real text, not a scanned picture of text

Arabic content tip

Set the document language to Arabic, check that the reading order goes right to left, and use real Arabic text, not scanned images of text. Scanned Arabic PDFs need OCR before they can be made accessible.

Back to all content types

Word, Excel and PowerPoint

Letters, reports, spreadsheets, templates and presentations made in Microsoft Office or similar tools.

  • DOCX
  • XLSX
  • PPTX

What gets checked

  • Word: real headings (Heading 1, 2, 3) and lists
  • Alternative text for pictures, charts and SmartArt
  • Simple tables with a header row; no merged cells
  • Excel: each sheet named, no blank sheets, clear headers
  • PowerPoint: every slide has a unique title, correct reading order
  • Meaningful link text, not 'click here'
  • Good colour contrast; colour is not the only way to show meaning
  • Run the built-in Office Accessibility Checker

Arabic content tip

Set the proofing language to Arabic, use the built-in right-to-left paragraph direction, and use Office heading styles rather than bold text. Choose clear Arabic fonts and avoid very thin or decorative ones for body text.

Back to all content types

Video and audio

Videos, webinars, podcasts, live streams and social media clips.

  • MP4
  • Audio
  • Live

What gets checked

  • Captions for all pre-recorded video
  • Captions for live video
  • Audio description of important visual information
  • Transcripts for audio and podcasts
  • Media players that work with the keyboard and screen readers
  • No auto-playing sound that cannot be stopped

Arabic content tip

Provide Arabic captions written by people, not only automatic ones, and check that they are timed correctly. For important public messages, add Emirati or Arabic sign language interpretation.

Back to all content types

E-books and digital publications

E-books, digital textbooks, manuals and other long publications.

  • EPUB
  • EPUB Accessibility 1.1

    Main standardCurrent

    W3C · W3C Recommendation, 2023 (updated October 2024)

    Sets the accessibility rules for EPUB e-books, including accessibility metadata and meeting WCAG. Version 1.0 is also published as ISO/IEC 23761:2021.

    Read the standard EPUB Accessibility 1.1 (opens in a new tab)

What gets checked

  • Logical reading order and navigation (table of contents)
  • Alternative text for images
  • Accessibility metadata that describes the book's features
  • Content meets WCAG 2.2 AA
  • Page numbers that match the printed book, if there is one

Arabic content tip

Set the publication language and page direction to Arabic so e-book readers turn pages right to left, and include accessibility information (metadata) so readers know what features the book supports.

Back to all content types

Buying and managing technology

Rules for organisations that buy, build or manage digital products and services.

  • Procurement
  • Policy
  • EN 301 549 v4.1.1

    Main standardCurrent

    ETSI / CEN / CENELEC · Published 2 September 2026; replaces v3.2.1 once cited by the EU (expected late 2026)

    The European standard for accessible ICT, used in public procurement and for the European Accessibility Act. It covers websites, documents, software, hardware and communication, and is aligned with WCAG 2.2 AA.

    Read the standard EN 301 549 v4.1.1 (opens in a new tab)
  • ISO/IEC 30071-1:2019

    Supporting

    ISO / IEC · International standard, 2019

    A code of practice that shows organisations how to build accessibility into the way they plan, design, buy and test ICT products.

    Read the standard ISO/IEC 30071-1:2019 (opens in a new tab)

What gets checked

  • Accessibility written into tenders and contracts
  • Suppliers give an accessibility conformance report (VPAT/ACR)
  • Accessibility testing before launch and after updates
  • A published accessibility statement
  • Staff training and a named accessibility lead

Arabic content tip

When you buy software or websites, ask suppliers for an accessibility conformance report (VPAT/ACR) that includes Arabic and right-to-left support, not only English.

Back to all content types

What is coming next

Standards keep improving. These are the changes to plan for.

  • Coming soonEN 301 549 v4.1.1 becomes the EU harmonised standard

    Expected to be cited in the EU Official Journal in late 2026. Until then, v3.2.1 (based on WCAG 2.1) stays in force.

  • DraftWCAG 3.0

    A new, broader model is being written by W3C (latest working draft: March 2026). It is not ready to use yet; W3C expects it to take several more years.

  • Coming soonMove to PDF 2.0 and PDF/UA-2

    Tools are adding support for PDF/UA-2. PDF/UA-1 stays valid, but new projects can start planning for the newer version.

Not sure which standards apply to you?

We audit websites, apps and documents against these standards and help your team fix what we find, in Arabic and English.

Talk to us

This guide is for general information and is not legal advice. Which standard and level you must meet depends on your country, sector and contracts. Always check the official standard and your local regulator.