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.
- Websites and web appsPublic websites, portals, e-services, online forms and web applications.Main standard: WCAG 2.2Latest version: WCAG 2.2 (2023, updated 2024) · ISO/IEC 40500:2025Usual legal target: Level AA
- Mobile appsNative and hybrid apps on iPhone, iPad and Android phones and tablets.Main standard: WCAG 2.2 (applied to apps)Latest version: WCAG 2.2 + WCAG2ICT (2025)Usual legal target: Level AA
- PDF documentsReports, forms, guides, policies and any document shared as PDF.Main standard: PDF/UA (ISO 14289)Latest version: PDF/UA-2 (ISO 14289-2:2024)Usual legal target: PDF/UA + WCAG 2.2 AA
- Word, Excel and PowerPointLetters, reports, spreadsheets, templates and presentations made in Microsoft Office or similar tools.Main standard: WCAG 2.2 for documentsLatest version: WCAG 2.2 + WCAG2ICT (2025)Usual legal target: Level AA
- Video and audioVideos, webinars, podcasts, live streams and social media clips.Main standard: WCAG 2.2 (guideline 1.2)Latest version: WCAG 2.2Usual legal target: Level AA
- E-books and digital publicationsE-books, digital textbooks, manuals and other long publications.Main standard: EPUB AccessibilityLatest version: EPUB Accessibility 1.1 (2023)Usual legal target: WCAG 2.2 AA
- Buying and managing technologyRules for organisations that buy, build or manage digital products and services.Main standard: EN 301 549Latest version: EN 301 549 v4.1.1 (2026)Usual legal target: WCAG 2.2 AA + extra ICT needs
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
- 1999WCAG 1.0The first guidelines
- 2008WCAG 2.0Became ISO/IEC 40500:2012
- 2018WCAG 2.1Added mobile and low vision
- 2023WCAG 2.29 new success criteria
- 2025ISO/IEC 40500:2025WCAG 2.2 becomes an ISO standard
- 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
WCAG 2.2 (Web Content Accessibility Guidelines)
Main standardCurrentThe main international standard for web accessibility. It has testable success criteria at three levels (A, AA, AAA). Version 2.2 added 9 new criteria, for example larger touch targets, visible focus, help that is easy to find and simpler log-in.
Read the standard WCAG 2.2 (Web Content Accessibility Guidelines) (opens in a new tab)ISO/IEC 40500:2025
CurrentWCAG 2.2 published as an official ISO international standard. It replaces ISO/IEC 40500:2012 (WCAG 2.0), so governments can refer to it in laws and contracts.
Read the standard ISO/IEC 40500:2025 (opens in a new tab)WAI-ARIA 1.2
SupportingTechnical rules that help developers make custom controls (menus, tabs, dialogs) understandable to screen readers.
Read the standard WAI-ARIA 1.2 (opens in a new tab)
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.
Mobile apps
Native and hybrid apps on iPhone, iPad and Android phones and tablets.
- iOS
- Android
WCAG 2.2 applied to apps (WCAG2ICT)
Main standardCurrentThere is no separate 'app WCAG'. W3C's WCAG2ICT guidance explains how to apply each WCAG 2.2 criterion to apps and other software. Most laws require Level AA for apps too.
Read the standard WCAG 2.2 applied to apps (WCAG2ICT) (opens in a new tab)EN 301 549 v4.1.1 (clause 11: software)
CurrentThe European standard for accessible ICT. Clause 11 sets the rules for software and mobile apps, based on WCAG 2.2 AA plus extra needs, such as working with the phone's accessibility settings.
Read the standard EN 301 549 v4.1.1 (clause 11: software) (opens in a new tab)Apple Human Interface Guidelines and Android accessibility guidelines
SupportingPlatform guidance on VoiceOver, TalkBack, Dynamic Type and touch target sizes. Useful for designers and developers, but not a legal standard.
Read the standard Apple Human Interface Guidelines and Android accessibility guidelines (opens in a new tab)
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.
PDF documents
Reports, forms, guides, policies and any document shared as PDF.
PDF/UA-1 (ISO 14289-1:2014)
Main standardCurrentThe international standard for accessible PDF ('UA' means Universal Accessibility). It is the version most tools and laws use today, for PDF 1.7 files.
Read the standard PDF/UA-1 (ISO 14289-1:2014) (opens in a new tab)PDF/UA-2 (ISO 14289-2:2024)
CurrentThe newest version, for PDF 2.0 files. It improves support for maths, links and modern structure, and is built to work well with WCAG.
Read the standard PDF/UA-2 (ISO 14289-2:2024) (opens in a new tab)Matterhorn Protocol and Well-Tagged PDF (WTPDF)
SupportingMatterhorn is the official checklist for testing PDF/UA-1 files. Well-Tagged PDF sets out how to tag PDF 2.0 files for accessibility and reuse.
Read the standard Matterhorn Protocol and Well-Tagged PDF (WTPDF) (opens in a new tab)WCAG 2.2 for documents
SupportingLaws that require WCAG usually apply it to PDFs on a website too. A PDF should meet PDF/UA and WCAG 2.2 AA together.
Read the standard WCAG 2.2 for documents (opens in a new tab)
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.
Word, Excel and PowerPoint
Letters, reports, spreadsheets, templates and presentations made in Microsoft Office or similar tools.
- DOCX
- XLSX
- PPTX
WCAG 2.2 applied to documents (WCAG2ICT)
Main standardCurrentOffice files are 'non-web documents'. WCAG2ICT explains how WCAG 2.2 applies to them, for example headings, alternative text, contrast and reading order. Level AA is the usual target.
Read the standard WCAG 2.2 applied to documents (WCAG2ICT) (opens in a new tab)EN 301 549 v4.1.1 (clause 10: non-web documents)
CurrentClause 10 of the European ICT standard lists the accessibility rules for documents such as Word, Excel, PowerPoint and PDF, aligned with WCAG 2.2 AA.
Read the standard EN 301 549 v4.1.1 (clause 10: non-web documents) (opens in a new tab)Section 508 (US federal)
SupportingUS federal agencies must make electronic documents accessible. Section508.gov publishes free, practical checklists for Word, Excel, PowerPoint and PDF.
Read the standard Section 508 (US federal) (opens in a new tab)
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.
Video and audio
Videos, webinars, podcasts, live streams and social media clips.
- MP4
- Audio
- Live
WCAG 2.2: Guideline 1.2 Time-based media
Main standardCurrentSets the rules for captions, audio description and transcripts. At Level AA, pre-recorded and live videos need captions, and pre-recorded videos need audio description.
Read the standard WCAG 2.2: Guideline 1.2 Time-based media (opens in a new tab)WebVTT (Web Video Text Tracks)
SupportingThe common file format for captions and subtitles on the web. It supports right-to-left Arabic text.
Read the standard WebVTT (Web Video Text Tracks) (opens in a new tab)
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.
E-books and digital publications
E-books, digital textbooks, manuals and other long publications.
- EPUB
EPUB Accessibility 1.1
Main standardCurrentSets 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.
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 standardCurrentThe 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
SupportingA 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.
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.
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.
