Skip to main content
Guide

Hebrew and RTL website accessibility, direction, language, and mixed content

Israeli sites are mostly RTL. Wrong `lang` and `dir`, mirrored icons, and mixed LTR snippets create real barriers beyond generic WCAG checklists.

07/17/20261 min read

Accessibility guidance written only for English LTR sites misses daily Israeli reality: Hebrew copy, English product names, phone numbers, and forms that jump direction mid-field.

Document basics

  • lang="he" on Hebrew pages
  • dir="rtl" when the primary reading direction is right-to-left
  • Local overrides for English paragraphs or code samples when needed

UI details that break in RTL

Chevrons that point the wrong way, progress steppers that reverse unexpectedly, and toast messages anchored to the wrong edge.

Forms and numbers

Phone, ID, and card fields often stay LTR internally. Users still need clear labels in Hebrew and error text that does not scramble digits.

Content authoring

Avoid images of Hebrew text as the only source of copy. Prefer real text that can resize and be read by assistive tech.

Test ritual for Israeli sites

  1. Check lang and dir on home and one inner page
  2. Tab through the header in RTL
  3. Fill a form in Hebrew and with a mixed email address
  4. Zoom to 200% and confirm no clipped Hebrew letters

Frequently asked questions

Should the html element be lang he and dir rtl?
For a Hebrew-first site, yes in most cases. English pages should switch language appropriately, and mixed snippets may need local dir overrides.
Do screen readers care about lang?
Yes. Correct language tagging improves pronunciation and is an explicit WCAG requirement for page language.
Is mirroring every icon enough?
No. Some icons should not flip, and focus order must still follow reading order, not a broken visual mirror.

Sources

Related articles