Arabic A11y expertise
Arabic A11y is our specialist accessibility support for Arabic and bilingual websites, apps and documents. We evaluate the content, interaction and assistive technology experience in the language people use.
Our wider work spans interfaces in languages from around the world. Arabic A11y brings a dedicated regional specialism to that experience, addressing Arabic content and its interaction with English and other languages.
Standards across languages
We apply WCAG to Arabic and English services, with PDF/UA targets for PDFs. UAE engagements include the UAE A11y Code within the National Digital Accessibility Policy where applicable.
The assessment examines how those requirements work in context: accessible names, reading order, mixed-language content and keyboard behaviour. Each finding identifies the language and environment affected.
What we assess
Language and meaning
Labels, instructions, alternative text and screen reader announcements that convey the intended meaning.
Right-to-left interaction
Reading and focus order, layout, and combinations of Arabic, Latin text, numbers and punctuation.
Bilingual journeys
Language switching and consistency across screens, forms, messages and supporting documents.
Documents and assistive technology
Document structure and language, evaluated with relevant assistive technology.
Regional delivery
For TDRA, we authored the bilingual UAE A11y Code and produced an unofficial Arabic translation of WCAG 2.2. Our ongoing Zain Kuwait engagement applies Arabic and English expertise across services, communications and employee policies.
Language and interaction
An interface can display Arabic while still exposing English labels to a screen reader. A form can look correct while its keyboard focus moves in an unexpected sequence. We investigate these differences in the working service.
Mixed-language information needs particular care. Email addresses, reference numbers, dates and brand names should remain understandable when displayed, navigated or announced within Arabic content.
Testing connects content, code and interaction around a real task. It establishes whether the information people need is available in each affected language and environment.
Planning bilingual testing
- Identify priority journeys in Arabic and English, including supporting documents and messages.
- Use representative names, numbers and mixed-language content.
- Choose relevant devices, browsers and assistive technology.
- Record findings that affect one language, both versions or language switching.
- Verify fixes in each affected context, including shared components.
Arabic A11y questions
Can Arabic A11y be reviewed before launch?
Yes. We can review designs and content before launch, then test the implemented service. The scope reflects your development stage and the decisions still open to change.
Does this apply to documents as well?
Yes. We review document language, structure and reading order. Document accessibility can be included in a wider bilingual engagement.
Build sustainable accessibility
Tell us about your services, your priorities and the people who use them. We will help you define the right support, agree a clear scope and plan your next steps.
Get in touch