Back and forward icons in RTL interfaces
Learn how to orient back and forward icons in Arabic, preserve navigation behavior, and fix misleading labels, links, and nested controls.
By Omran Khleifat, Founder of Ritla
Guide14 min read
In an Arabic navigation flow, a back arrow points right and a forward arrow points left. Moving an English back button to the right side of a header does not change its left-pointing artwork. Reversing that artwork does not fix a handler that opens the wrong page, either.
Material Design's bidirectionality guidance mirrors back and forward navigation icons. Apply that convention to the action the component actually represents. Browser history, a parent-page link, and the previous item in a collection can share a back-shaped icon while having different destinations.
The reliable implementation keeps four things in agreement: the action, its translated name, the icon's orientation, and its placement. This guide uses a fictional calligraphy lesson reader to show where those pieces diverge, including instructions that tell readers to click a physical arrow direction.
Define what back and forward do in this component#
Before changing an asset, name the navigation relationship. In the lesson reader, returning to the lesson catalogue is different from opening the preceding lesson. Neither necessarily means returning to the last page in browser history.
| Control | Destination or operation | Arabic navigation icon |
|---|---|---|
| Back in session history | The preceding history entry | Right-pointing back counterpart |
| Forward in session history | The next available history entry | Left-pointing forward counterpart |
| Return to lessons | The known lesson catalogue route | Right-pointing return counterpart |
| Previous lesson | The predecessor in the curriculum | Right-pointing previous counterpart |
| Next lesson | The successor in the curriculum | Left-pointing next counterpart |
| Move the canvas right | A physical movement within the workspace | Keep the right-pointing geometry |
The last row is the boundary of this rule. A right-pointing arrow is not automatically a forward-navigation icon. A horizontal pan control in a calligraphy practice canvas describes a physical movement, not progress through lessons.
The same caution applies to arrows inside instructional illustrations. An arrow showing a pen stroke must preserve the intended stroke direction. Its geometry is part of the lesson content. Mirroring every arrow because the surrounding interface is Arabic would change what the lesson teaches.
Write the relationship into the component contract. A name such as previousLesson communicates more than leftButton; a name such as returnToCatalogue avoids implying history traversal. Keep physical direction names inside the asset layer, where they describe drawings rather than application behavior.
This also gives QA a usable expected result. “The back arrow should work” is underspecified. “Return to lessons opens the Arabic catalogue from any lesson entry point” can be tested.
Do not substitute browser history for a known destination#
Suppose the lesson page labels its return control العودة إلى دروس الخط, meaning return to the calligraphy lessons. The intended destination is the catalogue, including when someone opens a lesson from a shared link.
Problem: implementing that destination as history traversal:
<button type="button" onclick="history.back()"> العودة إلى دروس الخط</button>history.back() moves back one entry in session history. It does nothing when there is no preceding entry. If the preceding entry belongs to another site or another part of the application, it does not become the lesson catalogue because the button's label promises one.
Better: give a known destination a real link:
<a href="/ar/calligraphy">العودة إلى دروس الخط</a>The route is an example application route; use the actual localized catalogue URL. This changes the control to match its intended job. It does not attempt to recreate the browser's Back button.
An anchor with href also retains link behavior such as opening its destination in another tab. MDN's anchor reference describes those semantics. If a router intercepts ordinary link activation, retain the destination URL and verify modified clicks instead of reducing the control to a click-only element.
If the product really intends session-history navigation, use a button and label it accordingly. The HTML direction must not change which history API it calls. A right-pointing Arabic back icon still calls Back, not Forward. history.forward() traverses an available forward entry; it is not an implementation of “next lesson.”
Do not use history.length > 1 as proof of a suitable in-app return destination. History length counts session entries, including the current entry. It does not identify the previous route or establish that it belongs to this curriculum.
Mirror the icon without reflecting the link text#
This catalogue link uses a left-pointing source chevron for its English back convention. Its Arabic label and surrounding section are declared in markup.
<header lang="ar" dir="rtl"> <a class="lesson-return" href="/ar/calligraphy"> <svg class="lesson-return__glyph" viewBox="0 0 24 24" width="22" height="22" aria-hidden="true" focusable="false"> <path d="M15 6L9 12L15 18" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" /> </svg> <span>العودة إلى دروس الخط</span> </a></header>Problem: this places the glyph before the label but leaves its geometry unchanged:
.lesson-return { display: inline-flex; align-items: center; gap: 0.875rem;} .lesson-return__glyph { flex: none;}On the Arabic header, the first flex item sits on the right. The glyph therefore moves to the leading side, but its path still points left. Layout order and path orientation are independent.
Better: retain those rules and reflect just this link's glyph in RTL:
.lesson-return__glyph { transform-origin: center;} .lesson-return:dir(rtl) > .lesson-return__glyph { transform: scaleX(-1);}The label remains readable. The English source chevron and spacing remain unchanged. With a corresponding English label and LTR container, the reflection rule does not apply. MDN's scaleX() reference documents the horizontal transformation.
Do not apply the reflection to .lesson-return itself. That would reflect all its painted contents, including the text. Do not use row-reverse to repair the arrowhead: changing row order does not redraw a path.
The layout and SVG distinction is covered by the brief's Chromium 151 measurements: SVG drawings do not mirror with page direction, while a normal flex row follows it. Check the supported browsers for the actual component, especially if an icon package adds its own rendering rules. See RTL flexbox for row-order problems that extend beyond this link.
Keep previous and next attached to the curriculum#
A lesson reader needs ordered content, not language-dependent array mutations. This fixture records curriculum order once:
const calligraphyLessons = [ { key: 'pen-angle', title: 'زاوية القلم' }, { key: 'letter-joins', title: 'وصل الحروف' }, { key: 'line-balance', title: 'اتزان السطر' }]; function adjacentLessons(currentKey) { const index = calligraphyLessons.findIndex( lesson => lesson.key === currentKey ); if (index < 0) throw new Error('Lesson is outside this curriculum'); return { previous: calligraphyLessons[index - 1] ?? null, next: calligraphyLessons[index + 1] ?? null };}For the middle lesson, previous is the pen-angle lesson and next is the line-balance lesson in either interface language. Changing direction changes the arrows and visual placement; it does not exchange those destinations.
Use the returned keys to resolve localized lesson URLs and translated titles. The example's Arabic titles are fixture content, not a replacement for the application's translation resources. Keep stable keys when labels change or lessons are renamed.
Do not reverse the curriculum array to obtain an RTL appearance and then continue using index minus one as previous. That changes which lesson the operation selects. Similarly, do not sort by translated title unless alphabetical browsing is the specified sequence. A curriculum and a search result list may use different ordering.
When the reader starts on the first lesson, previous is absent. At the final lesson, next is absent. Choose a boundary treatment explicitly: omit the unavailable navigation link or render a noninteractive explanation. Do not leave a clickable arrow with a dummy destination. If the final action becomes “Finish lesson series,” update the label and behavior rather than silently reusing next navigation.
This adjacency model is separate from browser history. A reader may jump directly from the catalogue to the final lesson and still have a previous lesson in the curriculum. Browser Back might return to the catalogue instead.
Agree on placement as well as arrow direction#
In a horizontal pair that follows this reader's sequence convention, previous belongs at inline start and next at inline end. That places previous on the right and next on the left in Arabic, with the opposite arrangement in English. Keep the source order previous then next when laying out that pair.
An isolated return link does not need a second control or a full-width footer to establish its meaning. Its location in a header can follow the product's navigation pattern. Avoid a rule that moves every back icon to the viewport's right edge: a back action inside a nested panel belongs to that panel's layout.
List chevrons need the same semantic review. A trailing chevron that means “open this lesson” can follow forward navigation. A down chevron that means “expand lesson details here” represents disclosure, not forward travel. Changing every chevron to the Arabic forward orientation would obscure that difference.
For responsive layouts, decide what happens when previous and next stack. Preserve their labels and destinations even when a horizontal spatial comparison disappears. Do not let an icon-only breakpoint remove the only explanation distinguishing return-to-catalogue from previous-lesson navigation.
Spacing needs its own inspection. A reflected chevron can still sit too close to Arabic text if physical margins were written for the English position. Use logical spacing or gap for the relationship the layout actually needs. CSS logical properties for RTL covers those substitutions.
The useful review has three separate questions: is the correct control at the intended location, does its arrow point the intended way, and does it open the intended destination? A screenshot answers only part of that review.
Use the navigation surface's direction#
Orient the control from the interface that owns it. Do not infer its direction from whichever content title it displays. An Arabic lesson catalogue can contain an English reference title without making its surrounding back action LTR.
In the CSS example, :dir(rtl) is applied to the HTML link. MDN's :dir() documentation distinguishes semantic direction from CSS direction: the selector follows direction established by the document, including inherited values. A CSS-only override is not the same contract.
A broad [dir="rtl"] .back-icon selector continues to match icons under that ancestor even inside a nested dir="ltr" section. Decide whether that section is actually an LTR navigation surface or merely LTR content inside an Arabic surface. Put the direction boundary around the correct owner.
For a foreign title within an Arabic link, isolate the title's text when needed instead of setting dir="auto" on the entire navigation component. Otherwise the content can determine the control's direction even though its place in the interface has not changed. Nested LTR content explains that boundary in more detail.
Language switching can also leave a stale asset behind. Verify that an in-page switch updates the icon together with labels and destinations. An icon selected once from an initial locale will not become correct merely because a parent attribute changes later.
Choose one owner for directional artwork#
There are two workable asset strategies: reflect a canonical back or forward glyph, or select the corresponding finished LTR/RTL asset. Select one strategy for the control and document whether the icon package already implements it.
If the package selects a right-pointing Arabic back asset, adding the earlier CSS reflection makes it point left again. This double mirroring can be difficult to spot in source code because each individual layer appears to support RTL.
Inspect the actual artwork, not just a component name. A component called BackIcon may already account for direction; one called ChevronLeft may promise physical geometry. Those are useful naming conventions, not facts you can assume about every package.
Keep arrow transforms away from unrelated state styling. A hover rule that replaces transform can remove the RTL reflection. An animated transition can likewise show the correct resting arrow but move it opposite to the destination's visual direction. Test the rendered states rather than approving only the default icon.
If the design uses an asymmetric arrow with a badge, text, or another detail that should not reflect, use an authored counterpart. Do not reflect the entire asset just because its arrowhead needs to change. Keep those artwork decisions inside the asset layer rather than attaching per-page exceptions to every usage.
Review shared wrappers, CSS pseudo-elements, and mobile-only replacements during an icon-library migration. A correct desktop inline SVG does not establish the orientation of a different asset rendered by the compact header.
Make screen transitions agree with the navigation action#
An RTL back arrow can be correct at rest while the screen transition still suggests forward navigation. Write down the expected visual transition separately from the asset rule. The icon's CSS reflection does not change a router's transition configuration.
For the lesson reader, decide whether moving to the next lesson uses a directional transition at all. An immediate content replacement does not need an invented leftward slide. If the design uses spatial motion to convey progression, test forward and return transitions as a pair under both interface directions.
Keep transforms for the arrow, the control, and the page transition separate. Reflecting a page wrapper to reuse an English animation also reflects its content. Changing a translation distance without checking the transition's entering and leaving elements can make the incoming page move correctly while the outgoing page leaves through the wrong edge.
Include interrupted transitions in the review. Activate next, then use the application's return action before the transition finishes. Verify the resulting lesson key and controls rather than judging only the motion. A pending transition should not restore an old arrow or label after the newer navigation has completed.
When the product reduces or removes motion, retain the same destinations and names. Animation can reinforce navigation, but it must not be the only indication that the lesson changed.
Distinguish returning from dismissing an overlay#
A compact lesson reader may open an explanation over the current lesson. Closing that explanation and returning from the lesson are separate actions, even if both restore something that was visible earlier.
If the explanation has no internal navigation stack, a close control can be clearer than a back-shaped arrow. Name its actual action and preserve the underlying lesson. Do not make a close control traverse session history merely because a designer placed it where the header's back arrow normally appears.
If the overlay contains several nested views, its own back action can return to the preceding view while a separate close action dismisses the overlay. Orient that back icon from the overlay's navigation surface and test the two destinations independently. A single generic goBack handler shared by both controls conceals the distinction.
Record focus expectations as part of that contract. Dismissing the explanation should return the reader to a useful place in the lesson, while returning to the catalogue changes the reading context. These are interaction decisions to implement and test, not consequences of reflecting a chevron.
Replace physical-arrow instructions with action names#
Instructions can preserve the English mistake after the icons are fixed. This text tells Arabic readers to use a left arrow for a return action whose icon should point right:
Problem
<p>اضغط على السهم الأيسر للعودة إلى دروس الخط.</p>Changing “left” to “right” would repair that one layout, but the instruction would remain dependent on physical placement. It could become wrong in a nested reader, a stacked layout, or a design using text links without arrowheads.
Better
<p>اختر «العودة إلى دروس الخط» لفتح قائمة الدروس.</p>The wording now names the control and its result. Keep that name consistent with the visible link text and any localized tooltip. Search onboarding copy, empty states, help text, and error recovery instructions as well as translation keys attached to buttons.
This is the scope of : UI text referencing physical arrow directions. It is separate from , Directional icon pointing against the sequence its control advances. Correcting one does not establish that the other has been corrected.
A physical-direction instruction can be appropriate when the task really is physical movement, such as panning the practice canvas right. In that case, retain the actual direction and make the context clear. Do not replace every occurrence of “left” and “right” across the product with “previous” and “next.”
Likewise, distinguish a named keyboard key from an icon's visual orientation. If help documents an implemented keyboard command, verify that command and its context. Mirroring an icon does not authorize remapping a browser shortcut or intercepting text-editing arrow keys.
Preserve names, focus, and ordinary navigation behavior#
With visible text, let the label name the link and hide its decorative chevron from assistive technology, as in the catalogue example. For an icon-only version, provide a localized name describing its action, such as aria-label="العودة إلى دروس الخط".
The WAI link pattern recommends native links for resource navigation. A painted arrow with an event handler does not automatically provide link semantics or its expected keyboard behavior. Do not make an SVG a separate focus stop inside its owning link.
When visible text remains, avoid an unrelated aria-label that overrides it with a different action. A control that displays return-to-lessons but announces previous-lesson has two competing contracts. W3C's Label in Name guidance explains why visible and accessible naming need to agree.
For client-side lesson changes, test where focus goes after activation. The arrow orientation does not tell a keyboard reader that the main lesson has changed. Choose and implement a focus strategy suited to the reader, then verify the updated heading and content are reachable without traversing the entire shell again.
Loading and failure states need review too. If a next-lesson request fails, do not leave the heading on one lesson while the navigation controls advance from another. Keep the displayed lesson key, adjacent destinations, and active loading state synchronized. Prevent repeated activation from skipping content if the interaction is defined as one lesson per action.
Test destinations under different entry paths#
Start with the middle fixture lesson and record the current key, expected previous key, expected next key, and catalogue URL. Use the same records for English and Arabic. This separates direction changes from changes to the content sequence.
Test the catalogue return from a direct URL, a new tab, and an in-app catalogue visit. It should open the named catalogue in each case. Separately test a genuine session-history control after visiting a known sequence of pages. Do not judge both controls against the same expected destination.
Activate previous and next, then repeat at the curriculum boundaries. Inspect the resulting title and URL, not just an animation. If a router restores state after browser Back, verify that the icon, localized label, and content all reflect the restored screen.
At a narrow width, inspect wrapped labels and any icon-only replacements. Repeat with keyboard activation, modified link clicks, and the supported touch interactions. A pointer-only test can miss a replacement control that lacks the original link behavior.
Finally, inspect each arrow in its rendered context: desktop header, compact header, lesson footer, catalogue row, and any overlay. For a failure report, include the control's intended action, actual destination, local direction, source asset, and observed orientation. Those details distinguish a route bug from a wrongly selected asset or an extra CSS reflection.
Keep media forward separate from navigation forward#
A calligraphy lesson may contain a demonstration player next to the next-lesson link. Both can use triangular or arrow-like artwork, but they are different controls. Preserve the player's established playback orientation while adapting the surrounding lesson navigation. Microsoft's mirroring guidance explicitly preserves fast-forward and rewind symbols.
Review helper text where these controls appear together. Name the lesson action and playback action explicitly so “forward” does not ambiguously refer to both. Test each destination or playback operation independently, including after the interface language changes.
A free Ritla scan can report Directional icon pointing against the sequence its control advances and UI text referencing physical arrow directions ; verify the destination by activating the control as well. For the next related issue, use what to mirror in RTL or nested LTR content inside an RTL page.