A Persian dashboard can have translated labels, right-aligned headings, and a navigation panel on the right while still being difficult to use.

An invoice number may sit awkwardly beside punctuation. A customer name may mix Persian and English. An email address may become hard to select inside a form. A directional icon may point somewhere the interface no longer suggests.

RTL interface design means deciding how layout, text, and interaction behave when the page reads from right to left. Translation is one part of that work.

The useful starting point is a real screen with real content: names, dates, identifiers, error messages, and actions. That is where direction rules become visible.

Separate language, direction, and alignment

These are three different decisions.

Language identifies the language of the content. Direction establishes its base reading direction. Alignment positions text within its available space.

For a Persian page, the document can begin with:

<html lang="fa" dir="rtl">

For an Arabic page, use the appropriate language declaration, such as lang="ar".

Setting lang does not automatically set direction. W3C recommends declaring the document’s RTL direction in HTML, where it remains available independently of the stylesheet. Right-aligning text with CSS does not replace that declaration.

In a design review, keep these decisions separate. A right-aligned invoice identifier may still need left-to-right text direction. An English product name may appear inside a Persian sentence without changing the direction of the entire paragraph.

A screenshot alone cannot document all of this. Add direction rules to the component specification.

Start with a content inventory

Before adapting the layout, list the kinds of content each screen contains.

For an account dashboard, that might include:

Content Question to resolve
Navigation labels Where does the navigation sequence begin?
Customer names Can names arrive in either writing direction?
Invoice identifiers Does the identifier have a fixed Latin format?
Email addresses How will users read, edit, and copy them?
Status messages Can translated sentences contain dynamic values?
Charts What do axis direction and progression mean?
Code samples Which parts must retain their original formatting?

This is a recommended planning exercise, not a web standard. Its purpose is to expose decisions that a generic “RTL version” checkbox hides.

For a client project, use the inventory to define scope. A marketing page with translated paragraphs needs different work from an administration tool containing editable tables, charts, and user-generated content.

Express spacing in terms of start and end

A component often needs spacing on its leading edge, regardless of which physical side that becomes.

CSS logical properties express those relationships through the inline and block axes. In horizontal writing, inline-start corresponds to the left in LTR and the right in RTL.

For example:

.notice {
  border-inline-start: 3px solid var(--color-border-accent);
  padding-inline: 1rem;
  padding-block: 0.75rem;
  text-align: start;
}

.notice__action {
  margin-inline-start: 0.5rem;
}

This describes a leading border, horizontal padding, and spacing before an action without hard-coding left or right. MDN documents how logical properties map to writing mode and direction.

During review, ask what each physical value means. Does margin-left mean “space before this label,” or does it represent an intentionally fixed physical position?

Prefer logical properties for relationships that follow reading direction. Keep physical coordinates where the design actually requires them.

Avoid maintaining a second stylesheet full of unexplained overrides. Each exception should have a reason someone can understand later.

Give mixed-direction content a clear boundary

RTL paragraphs regularly contain left-to-right material, including Latin names and identifiers. Punctuation and adjacent values can make the intended grouping unclear.

W3C recommends tightly wrapping opposite-direction phrases and declaring their direction when known. For inserted content whose direction is unknown, use an appropriate wrapper with dir="auto", or a bdi element.

A known Latin invoice identifier can be represented as:

<bdi dir="ltr">INV-2026-104</bdi>

A customer name whose direction varies can use:

<bdi dir="auto">{{ customerName }}</bdi>

The braces represent an escaped text value supplied by the application’s template system.

Place the boundary around the value, rather than around the whole surrounding message. The translated sentence and its inserted identifier have different responsibilities.

For review, prepare a sentence containing an identifier, parentheses, and a second number. Check whether readers can tell which punctuation belongs to which value. Then copy the identifier and compare it with the original.

The acceptance criterion should describe the content: “The complete invoice identifier remains readable and copies exactly.” That is more useful than “The text looks aligned.”

Choose field direction according to its content

An RTL page does not imply that every field accepts RTL text.

A practical field specification should distinguish between:

  • Free-text content that may arrive in multiple languages.
  • Content expected in the page’s language.
  • Structured values with a defined format.

For runtime text, HTML supports dir="auto" so direction can be determined from the content. A field with a known LTR format can declare dir="ltr" explicitly. These are content-direction decisions, separate from the direction of the surrounding label and help text. W3C explains these direction attributes.

For example, a product might specify an LTR field for Latin-format invoice codes while allowing automatic direction for a customer display name.

Test editing as well as the initial appearance. Place the cursor in the middle, select a substring, paste a value, and correct a mistake. A field can look acceptable when populated but feel confusing during actual use.

Treat digit style, date formatting, and accepted input formats as explicit localization decisions. Record them separately from the layout direction.

Review mirroring by meaning

My recommendation is to classify visual elements before mirroring them.

A navigation arrow communicates movement through an interface. A logo identifies a brand. A chart axis represents a data relationship. Their shapes may all be asymmetric, but they do not share the same meaning.

Use a review table:

Element Recommended review
Back and forward controls Check the localized navigation convention and destination.
Logo or wordmark Preserve the approved brand artwork.
Search or settings icon Check whether there is any directional meaning to change.
Screenshot Use an appropriate localized screenshot where needed.
Chart or timeline Define progression from the meaning of the data.
Code block Preserve the code’s intended presentation.

Do not approve an entire icon set based on one mirrored example. Review the directional controls in context, including their labels and resulting actions.

For charts, ask a more precise question than “Should this flip?” Ask which end represents the beginning, how the axis labels explain that relationship, and what readers expect in this product.

Review typography with actual Persian and Arabic text

A layout approved using short English labels has not yet been reviewed for its translated content.

Use the intended font and representative text before fixing component dimensions. Include long headings, multi-line buttons where permitted, validation messages, and dense table rows.

A practical typography review should check:

  • Whether letters and marks remain clear at the intended sizes.
  • Whether line spacing is comfortable in paragraphs and controls.
  • Whether translated labels wrap without hiding nearby actions.
  • Whether truncation removes information needed to distinguish items.
  • Whether mixed-script text remains visually coherent.

Avoid prescribing one universal line-height or font-size adjustment for every RTL language and font. Review the actual combination.

Ask a fluent reader to complete a task using the interface. Their review should include wording, reading order, and ambiguous abbreviations, alongside appearance.

Build a small direction test set

A reusable test set is more useful than repeatedly checking the same clean screenshot.

For a customer account screen, include:

Test content What to inspect
A Persian or Arabic name Reading direction and available space
A Latin name Isolation within surrounding RTL content
A mixed-script display name Grouping and punctuation
An identifier such as INV-2026-104 Character order and copying
A long email address Editing, wrapping, and overflow
A sentence containing parentheses and numbers Association between values and punctuation
A long translated error message Layout growth and action visibility

Run the screen at a narrow viewport and with enlarged text. Repeat the main task using the keyboard.

Keep keyboard review focused on whether the adapted layout still presents a coherent path. Detailed focus behavior deserves its own specification, especially for dialogs and complex controls.

For repeatable components, preserve representative test cases in the component preview or test environment. Include the troublesome combinations, not only the shortest labels.

Make direction part of the component contract

“Supports RTL” is too vague to be a useful handoff requirement.

For an invoice row, a concrete specification could say:

  • The row follows the page direction.
  • The invoice identifier uses LTR direction within an isolated boundary.
  • The customer name accepts either direction.
  • Spacing follows logical start and end.
  • The full identifier remains available when other content is truncated.
  • The copy action returns the original identifier.
  • Narrow layouts preserve the relationship between each label and value.

This gives designers, developers, and reviewers something observable to agree on.

For a new bilingual product, start with one demanding flow, such as finding an invoice, opening its details, and copying its identifier. Resolve the direction rules there, then apply the reviewed patterns across the product.

A successful RTL interface lets people read, edit, compare, and act without having to work around its direction choices. That quality comes from explicit content rules carried through design, implementation, and testing.