Fast. Simple. No meetings. No delays.
Home / Blog / Tel Aviv / Common RTL Mistakes in Hebrew Web Application Interfaces

Common RTL Mistakes in Hebrew Web Application Interfaces

The interface bugs that appear when a web app gains Hebrew: mirrored icons, broken tables, mixed-direction numbers and misaligned forms.

Cover graphic for the article: Common RTL Mistakes in Hebrew Web Application Interfaces

A broken RTL web application UI usually comes from a handful of repeatable mistakes: icons mirrored (or not) incorrectly, tables and progress bars running the wrong way, mixed-direction text, hard-coded left and right CSS, and unlocalised dates and numbers. This guide lists each one, why it happens and how to fix it.

Start with the RTL web application UI foundations

Most problems trace back to a missing basis. Set lang='he' and dir='rtl' on the root element when the interface is Hebrew, and drive both from the user's language so one codebase serves Hebrew and English. Then replace physical CSS properties with logical ones: margin-inline-start instead of margin-left, padding-inline-end instead of padding-right, inset-inline-start instead of left, and text-align: start instead of text-align: left. Flexbox and grid already follow the document direction, so avoid reversing rows by hand. For a broader overview of bilingual websites, see our guide to building a bilingual Hebrew-English website; this article concentrates on application-interface bugs.

Icons and arrows that should (and should not) mirror

The rule of thumb: mirror icons that express direction or progression through the interface, and leave alone icons that depict real-world objects or universal symbols.

Usually mirrorUsually do not mirror
Back and forward arrows, chevrons in lists and breadcrumbsPlay and pause media controls (these follow media convention)
Sidebar and navigation toggles, list indentsCheckmarks, close (X), plus and minus
Reply, undo and redo arrowsClocks, as clock hands turn the same way everywhere
Progress or step indicators that imply directionLogos, photos, brand marks and most pictograms of objects such as phones or cameras

A search magnifier handle, a speech bubble tail or a document with a text-like glyph sometimes need individual review. Build an icon component that accepts a flag for mirroring in RTL, and apply it with [dir='rtl'] .icon-directional { transform: scaleX(-1); } or the equivalent in your framework. Do not mirror every SVG globally.

Tables, charts and progress bars

  • Tables: the first column should sit on the right in RTL, and column order should follow reading order. Numeric columns usually stay right-aligned for readability, but check how they sit beside Hebrew labels. Sticky first columns and horizontal scroll shadows must use logical properties or they pin to the wrong edge.
  • Progress bars and steppers: a bar that fills from the right and a stepper that progresses right to left feel natural in Hebrew. A fixed width animation anchored left will look wrong.
  • Charts: decide deliberately. Many products keep time axes and numeric scales left-to-right even in Hebrew interfaces, while mirroring legends, titles and tooltips. Whatever you choose, apply it consistently and ask a native-speaking user if it reads naturally.
  • Sliders and carousels: check that the next control and swipe direction agree with the layout.

Mixed-direction strings and punctuation

Hebrew text with embedded English names, product codes, numbers or URLs is where the bidirectional algorithm surprises people. Why does punctuation jump to the wrong side? Neutral characters such as full stops, parentheses and hyphens take their direction from the surrounding text, so a sentence that ends with an English word followed by a full stop may display the dot at the wrong end.

  • Wrap user-generated or dynamic fragments in an isolating element: <bdi> or an element with unicode-bidi: isolate, so they do not disturb surrounding text.
  • Use dir='auto' on inputs and elements that show user-provided content of unknown language.
  • Force left-to-right for content that is always LTR, such as email addresses, URLs, phone numbers, order codes and code snippets: dir='ltr' plus text-align: start or an explicit alignment where needed.
  • Do not build strings by concatenating translated fragments and variables. Use full message templates with placeholders so translators can order the words naturally.

Form layout and validation messages

  • Labels, helper text and error messages should align to the start edge, with inputs matching.
  • Icons inside inputs, such as a search icon or a show-password toggle, belong on the logical start or end side, so use logical properties.
  • Give email, phone, URL and numeric inputs dir='ltr', so typed characters do not scramble, while keeping the placeholder readable.
  • Make error messages translatable with the field name as a variable, and check how they wrap beside icons.
  • Check that validation focus order and tab order follow the visual order.
  • Test select menus, date pickers and autocomplete widgets from third-party libraries separately; many have their own RTL support gaps.

Date, number and currency formats

Do not format by hand. Use the platform's internationalisation APIs, such as Intl.DateTimeFormat and Intl.NumberFormat with a Hebrew locale such as he-IL, and let them handle separators and the placement of the currency symbol, such as the shekel sign. Digits in Hebrew text are written left to right as a block, so a long number inside a sentence can look reordered if it is not isolated. Check amounts with a negative sign, percentages and ranges (for example a date range with a dash) because those are the usual offenders. Confirm with your users whether they expect the Gregorian calendar, which most business software uses, or a Hebrew calendar in specific contexts.

Testing RTL automatically

How do you test a bilingual UI without checking every screen by hand? Combine several approaches:

  1. Run end-to-end tests in a browser with the Hebrew locale and dir='rtl', and take visual snapshots of key screens in both directions. Tools such as Playwright support locale settings and screenshot comparison.
  2. Add a lint rule or search in code review for left, right, margin-left and similar physical properties.
  3. Use long pseudo-text or deliberately long Hebrew strings to check wrapping and truncation.
  4. Seed test data that mixes Hebrew, English, digits and punctuation, such as a customer named in English with a Hebrew address.
  5. Have a native Hebrew speaker review the real screens before release. Automated tests catch layout breaks, not unnatural wording.

A bug checklist

  • Root lang and dir are set from the user's language.
  • No hard-coded left and right in CSS or JavaScript layout code.
  • Directional icons mirrored; symbols and logos untouched.
  • Tables, steppers and sliders follow reading order.
  • Dynamic and user-generated text isolated; LTR-only fields forced to LTR.
  • Messages are full templates, not concatenated fragments.
  • Dates, numbers and currencies come from locale-aware formatting.
  • Third-party widgets checked, scrollbars and drawers open from the correct side.
  • Visual regression tests run for both directions.

Putting it together

Fix the foundations first, because logical properties remove most bugs in one pass. Then work through icons, tables, mixed text and forms, and lock the result in with automated visual tests. If you are planning a larger product, our guide to building a SaaS product for Israeli startups covers where localisation fits in the roadmap, and you can read about our approach to software development for Tel Aviv teams.

Frequently asked questions

Which icons should be mirrored in RTL?

Mirror icons that express direction or progression, such as back and forward arrows, chevrons, list indents, sidebar toggles and undo or redo. Leave checkmarks, close buttons, clocks, logos, media play controls and most pictograms of real objects alone. Review borderline icons individually instead of flipping every SVG globally.

How do I test a bilingual UI?

Run end-to-end tests in a Hebrew locale with dir set to rtl and compare screenshots against the English layout. Search code for hard-coded left and right values, seed data mixing Hebrew, English and digits, and use long strings to test wrapping. Finish with a review by a native Hebrew speaker.

Why does punctuation jump to the wrong side?

Punctuation is a neutral character, so the bidirectional algorithm gives it the direction of the surrounding text. When Hebrew text ends with an English word or number, a final full stop or bracket can appear at the wrong end. Isolating the embedded fragment with bdi or unicode-bidi isolate usually fixes it.

Related articles

Web Development Tel Aviv

Startup Landing Page Launch Checklist

Everything a startup landing page needs before launch: message, speed, forms, analytics, metadata, privacy text and tracking.

6 min read

🚀 Start Now