Estimated reading time : 4 min · Published
Declare language and direction separately
lang identifies language; dir identifies text direction. Check both at document level on an Arabic page. Do not reverse characters in stored data: the browser handles bidirectional presentation using text and markup.
Inventory affected components: menu, breadcrumbs, buttons, cards, tables, fields and errors. Logical CSS properties such as margin-inline and padding-inline help adaptation. Applying right alignment globally does not solve reading order or mixed scripts.
Isolate names, URLs and numbers
A Latin name in Arabic text can displace surrounding parentheses or punctuation when its directional context is ambiguous. Set an appropriate dir on a fragment with known direction; consider bdi or dir=auto for dynamic content of unknown direction. Check the result across browsers.
Create demonstration data combining an Arabic name, a French company, a URL, an email and an international number. Copy values from the interface and compare them with the original text. Directional handling must not reverse a phone number or change the address actually used by a link.
Prepare exact test references such as DEMO-00120 and https://example.com/ref/00120, using a domain reserved for examples. Within an Arabic sentence, isolate each complete Latin reference with its known left-to-right direction; do not split the URL at every dot or slash. Punctuation belonging to the sentence stays outside the fragment, while punctuation belonging to the reference stays inside.
Distinguish rendering, stored value and link destination. Correct appearance does not prove that href retains the intended URL or that copying reproduces the exact reference. Where HTML markup is available, prefer explicit isolation to invisible directional characters added to data. Plain text or attribute values may need a different solution: a bdi element cannot be inserted as markup inside an attribute.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Layer checked | Expected result | Failure to identify |
|---|---|---|
| Reading within the Arabic sentence | Reference and punctuation retain a clear association. | A parenthesis or separator appears to belong to the wrong fragment. |
| Stored value | Logical character order remains that of the reference. | Characters were reversed merely to repair appearance. |
| Copied text | The copied reference exactly matches the intended value. | Copying reveals a different order or unexpected invisible controls. |
| Link destination | The target address matches the reference independently of the label. | A correct label conceals a different destination. |
- W3C Internationalization : Inline bidi markup
Consulted on 22 October 2026; isolate fragments according to their direction and structure.
- W3C Internationalization : Unicode controls or markup
Consulted on 22 October 2026; using markup where available and its limits in attributes or plain text.
Test actions and reading order
Navigate the form by keyboard, trigger an error and correct it. Check labels, error announcements and retained input. An email field may need left-to-right direction inside an RTL form; validate the choice with a person who uses the language.
Visual mirroring must not change logical document order. Check tables, lists and navigation with a screen reader. Logos, photographs and symbols without directional meaning do not automatically need mirroring. Check previous and next arrows against the localised journey.
Have the entire journey reviewed
Ask an Arabic-speaking reviewer to test main pages, search, filters, no-result states and confirmations. Check the font, diacritics, wrapping, zoom and long strings. A homepage screenshot cannot validate every component.
Retain a component–data–action–result grid and connect each defect with its correction. Repeat it after resource names, forms or shared components change. Editorial translation, bidirectional presentation and accessibility require complementary review.
Keep identifier order in Arabic

Proposed case: an Arabic sentence contains a number, URL and Latin name. Visual order can make the reference ambiguous without changing characters.
Compare display, selection, copying and reading. Isolate differently directed segments for the context and test real values; do not manually reorder their content.
- Choose a realistic mixed string
- Compare display and copied text
- Check references and punctuation
- Review translated conditions
Quality-check website translations beyond words
Reference documents
- W3C: structural direction in HTML · Source consulted
- W3C: inline bidirectional text · Source consulted
- MDN : Bidirectional isolation element · Source consulted
Content updated on
Documented reference points for this topic
| Reference | Value or syntax | Scope |
|---|---|---|
| W3C · HTML language | <html lang="fr"> | The default language is declared on html; local language changes are marked. |
| WCAG 2.2 · 1.4.10 | 320 CSS px | Vertical content without two-dimensional scrolling; exceptions cover inherently two-dimensional content. |
| W3C Internationalization · HTML direction | lang="ar" dir="rtl" | Language and reading direction are separate information. Declaring ar alone does not establish the base direction; dir="rtl" does. Logical CSS properties adapt spacing without hard-coding left and right throughout the layout. |
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
