Smashing Magazine recently published "Accordion Icons: Which Work Best?", a useful look at which disclosure icons users understand. Its recommendation is the caret as the safest choice, with a warning against arrows that can mean several different things. It's good advice. What it doesn't cover is what happens in a right-to-left interface, where many of those same icons have to point the other way, and some of them must never flip.
In my RTL app design checklist, icon mirroring got one line. It deserves much more, because wrongly flipped icons are among the most common bugs I see in Arabic products. Here are the rules we use in client design systems at Breem.
Key takeaways
- Direction matters more in RTL because the same icon can mean "next" in one language and "back" in the other.
- Sort every icon into three groups: always mirror, never mirror, and depends on meaning.
- Collapsed carets point toward the content's leading edge in LTR; in RTL, a collapsed caret pointing sideways should point left.
- Encode direction in the design system with a "mirrorable" property, so developers and AI agents don't have to guess.
- Add icon direction to QA, with screenshots in both languages side by side.
Why direction matters more in RTL
An accordion caret, a back arrow and a "next" chevron all carry meaning through direction. In English, a chevron pointing right means "forward" or "go deeper". In Arabic, forward is to the left, so the same chevron pointing right means "back". If an icon doesn't flip when it should, users get the opposite meaning.
The reverse problem is just as bad. Some icons represent things in the physical world that don't change with language: a play button, a clock, a checkmark. Flipping those makes the interface look broken. The DEV guide on RTL design for UAE teams and Cloudtopia's RTL layout practices both make this point. The hard part is applying it consistently across hundreds of icons.
Three groups: always, never, depends
Always mirror
Icons whose direction expresses movement through the interface or through reading order:
- Back and forward arrows
- Chevrons used for navigation (list items, breadcrumbs, "see all")
- Progress and step indicators
- Undo and redo, when drawn as curved arrows
- Text alignment and indent icons
- Icons of a list with bullets or a document with lines of text
- Send icons in chat, which should point in the direction text flows
Never mirror
Icons that represent physical objects, universal symbols or time:
- Media controls: play, pause, fast-forward, rewind. These follow the direction of tape and timelines, which doesn't change with language.
- Clocks, timers and refresh icons that represent clockwise rotation
- Checkmarks
- Logos and brand marks
- Icons containing Latin text or numbers, such as a "1" or an "A"
- Objects held in the right hand in the real world, like a pen or a magnifying glass, unless your icon set specifically adapts them
Depends on meaning
The tricky ones, where the same shape is used for different purposes:
- A right-pointing arrow as "next" should mirror. The same arrow as "external link" usually shouldn't.
- A volume slider icon may mirror if your sliders do, but the speaker itself doesn't need to.
- Charts and trend arrows: an upward trend still goes up. Whether the x-axis flips depends on how your charts handle time, which I discussed in my dashboard design rules.
The fix for this group is simple: don't reuse one icon for two meanings. Create separate named icons, one for "next" and one for "external link", so each can carry its own rule.
Disclosure states in RTL
This is where the accordion research connects directly to RTL. Carets used for expand and collapse usually follow one of two patterns:
- Down when expanded, up when collapsed (or the reverse). Vertical carets don't need mirroring. This is the easiest pattern for bilingual systems.
- Sideways when collapsed, down when expanded, common in tree views and nested lists. In LTR, the collapsed caret points right, toward the content. In RTL, it should point left.
Two more details:
- Caret position. If the caret sits at the trailing end of the row in English, it should sit at the trailing end in Arabic too, which means the left side.
- Nested accordions. Indentation increases from the leading edge, so in Arabic, nested items move to the left. The caret should stay aligned with the indented content.
If you're starting a new system, I'd recommend vertical carets for accordions. They work identically in both directions and remove a whole class of bugs.
Encoding direction in the design system
Rules in a document are easy to forget. Rules in the component are hard to break. Here's how we encode direction:
- A mirrorable property on every icon. Each icon in the library carries a flag, such as
mirror: autoormirror: never. In code, the icon component reads this flag and flips itself automatically in RTL. - Naming by meaning, not shape.
icon/navigation/nextinstead oficon/arrow-right. "Next" knows it should flip; "arrow-right" doesn't. My post on naming components for bilingual teams goes into this approach in more detail. - RTL previews in Figma. Each icon page shows the LTR and RTL versions side by side, so designers see the rule at a glance.
- Written rules for AI agents. If agents generate screens from your system, put the mirroring rules in the files they read. I covered this in DESIGN.md Has No Sense of Direction.
[Waleed: add a screenshot of an icon library page showing LTR and RTL versions with the mirror property.]
QA: catching wrongly flipped icons
Even with good rules, icons slip through, usually when someone adds a new one under deadline. A few habits help:
- Side-by-side screenshots. For every release, capture key screens in Arabic and English and review them next to each other. Wrong icons jump out.
- A short icon checklist in the release QA: back arrows, chevrons, media controls, send icons, accordions.
- Test with native Arabic readers. They notice wrong direction instantly, even when designers who mostly work in English don't.
- Audit new icons. Any icon added since the last release gets its mirror property checked before it ships.
Closing thoughts
Icons are small, but in a bilingual product they carry a lot of meaning. The accordion research gives us a good starting point for which icons work. For Arabic products, the next step is deciding which way they point, and building that decision into the system so nobody has to make it again under deadline. Sort your icons into always, never and depends, name them by meaning, and let the components do the flipping.
Sources: Accordion Icons: Which Work Best? (Smashing Magazine), RTL UI design for Arabic apps: a guide for UAE teams (DEV), Best website design practices for RTL Arabic layouts in 2026 (Cloudtopia).
FAQs
Which icons should be mirrored in RTL?
Icons that show direction through the interface or reading order, such as back and forward arrows, navigation chevrons, progress indicators and send icons.
Should media play buttons flip in Arabic interfaces?
No. Play, pause, fast-forward and rewind follow the direction of media timelines, which doesn't change with language.
Which way should an accordion caret point in RTL?
Vertical carets don't change. If you use a sideways caret for collapsed items, it should point left in RTL, toward the content.