Repository navigation
Expand file tree
/
Copy pathindex.html
More file actions
767 lines (714 loc) · 41.9 KB
/
Copy pathindex.html
File metadata and controls
767 lines (714 loc) · 41.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
<!DOCTYPE html>
<html lang="en" dir="rtl" data-mode="broken">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Perfectly Backwards — RTL is a requirement, not a request</title>
<meta name="title" content="Perfectly Backwards — RTL is a requirement, not a request">
<meta name="description" content="This English page is deliberately rendered right-to-left so you can feel what 1.8 billion people put up with every day. Plus a live tracker of which products have shipped RTL support and which have not.">
<meta name="keywords" content="RTL, right-to-left, bidi, Arabic, Hebrew, Persian, Urdu, localization, internationalization, accessibility, digital inclusion">
<meta name="author" content="@asimnet">
<meta property="og:type" content="website">
<meta property="og:url" content="https://perfectly-backwards.com/">
<meta property="og:title" content="Perfectly Backwards — RTL is a requirement, not a request">
<meta property="og:description" content="An English page deliberately rendered right-to-left, so left-to-right readers can feel the defect for themselves. With a live RTL support tracker.">
<meta property="og:image" content="https://perfectly-backwards.com/assets/og_en.png">
<meta property="og:site_name" content="Perfectly Backwards">
<meta property="og:locale" content="en_US">
<meta property="og:locale:alternate" content="ar_AR">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@asimnet">
<meta name="twitter:creator" content="@asimnet">
<meta name="twitter:title" content="Perfectly Backwards — RTL is a requirement, not a request">
<meta name="twitter:description" content="An English page deliberately rendered right-to-left, so left-to-right readers can feel the defect for themselves.">
<meta name="twitter:image" content="https://perfectly-backwards.com/assets/og_en.png">
<link rel="canonical" href="https://perfectly-backwards.com/">
<link rel="alternate" hreflang="en" href="https://perfectly-backwards.com/">
<link rel="alternate" hreflang="ar" href="https://perfectly-backwards.com/arabic.html">
<link rel="alternate" hreflang="x-default" href="https://perfectly-backwards.com/">
<link rel="icon" type="image/svg+xml" href="assets/logo.svg">
<link rel="apple-touch-icon" href="assets/logo.png">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Amiri:ital,wght@0,400;0,700;1,400;1,700&family=Readex+Pro:wght@300;400;500;600&display=swap" rel="stylesheet">
<link rel="stylesheet" href="style.css">
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<p id="dir-announcer" class="visually-hidden" role="status" aria-live="polite"></p>
<header class="site-header">
<div class="shell site-header__inner">
<a class="brand" href="index.html">
<span class="brand__mark" aria-hidden="true">PB</span>
Perfectly Backwards
</a>
<div class="header-actions">
<button type="button"
class="dir-switch"
data-dir-switch
data-broken-dir="rtl"
data-fixed-dir="ltr"
aria-pressed="false"
title="This page is forced right-to-left. Press to read it the way it was designed.">
<span class="dir-switch__track" aria-hidden="true">
<span class="dir-switch__knob" data-dir-knob>RTL</span>
</span>
<span class="dir-switch__label" data-dir-label>Fix the direction</span>
</button>
<a class="lang-link" href="arabic.html" lang="ar" hreflang="ar">اقرأها بالعربية</a>
</div>
</div>
<div class="progress" data-progress aria-hidden="true"></div>
</header>
<main id="main">
<!-- ================================================================ -->
<section class="hero">
<div class="shell hero__inner">
<div>
<h1 class="hero__title">This page is in English. It is also <em>perfectly backwards.</em></h1>
<p class="lede">
Nothing about this design is broken. The type is set, the spacing is
considered, the colour is deliberate. Only the <strong>direction</strong> is
wrong — and that alone is enough to make it a chore to read.
</p>
<p>
That is the entire argument. Roughly 1.8 billion people who read Arabic,
Hebrew, Persian or Urdu open well-built software every day and meet exactly
this: something competent, pointed the wrong way.
</p>
<div class="hero__cta">
<button type="button" class="btn" onclick="document.querySelector('[data-dir-switch]').click()">
Make it readable
<span class="icon-directional" aria-hidden="true">→</span>
</button>
<a class="btn btn--ghost" href="#tracker">See the tracker</a>
</div>
<p class="sabotage-note">
You have a button for this. RTL users do not.
</p>
<div class="hero__meta">
<span><b>1.8B</b> readers of RTL scripts</span>
<span><b>2</b> of 8 everyday tools have shipped it</span>
<span><b>6</b> years on ClickUp's most-voted language request</span>
</div>
</div>
<figure class="specimen specimen--bad js-reveal">
<figcaption class="specimen__bar" role="presentation">
<span>Sent from a real product</span>
<span class="mono">bidi</span>
</figcaption>
<div class="specimen__body">
<p class="sample sample--broken" dir="rtl">
جمال اللغة يكمن في تفاصيلها، والـRTL ليس ترفاً، بل ضرورة والسلام PEACE
</p>
<p style="margin-block-end:0">
One sentence. Two scripts. The comma drifts, the Latin word lands in the
wrong place, and the reader has to reassemble the meaning by hand — every
single time.
</p>
</div>
</figure>
</div>
</section>
<!-- ================================================================ -->
<section class="section section--sunk" id="feel-it">
<div class="shell">
<div class="section__head">
<h2>Type something. Watch it come apart.</h2>
<p class="section__note">
Both panels receive the identical string. The only difference is whether the
directional runs are isolated.
</p>
</div>
<div class="bidi-lab">
<div class="bidi-lab__control">
<label class="label" for="lab-input">Your text — mix English and Arabic, add a price, a date, a ticket number</label>
<textarea id="lab-input"
class="bidi-lab__input"
data-lab-input
dir="auto"
rows="3"
spellcheck="false"></textarea>
<p class="bidi-lab__hint">
Punctuation, digits and brackets are <em>neutral</em> characters. They take
their direction from whatever sits next to them, which is why a full stop
can end up at the start of your sentence.
</p>
</div>
<figure class="specimen specimen--bad">
<figcaption class="specimen__bar" role="presentation">
<span>Naive — one direction, no isolation</span>
<span class="mono">×</span>
</figcaption>
<div class="specimen__body">
<p class="sample sample--broken" data-lab-broken dir="rtl"></p>
<p style="margin-block-end:0">
What most products ship: <code>dir</code> is set on a container and
nobody looks again.
</p>
</div>
</figure>
<figure class="specimen specimen--good">
<figcaption class="specimen__bar" role="presentation">
<span>Correct — runs isolated</span>
<span class="mono">✓</span>
</figcaption>
<div class="specimen__body">
<p class="sample sample--correct" data-lab-correct dir="auto"></p>
<p style="margin-block-end:0">
Each run wrapped with <code>unicode-bidi: isolate</code>. That is the
whole fix. It is a CSS declaration, not a research project.
</p>
</div>
</figure>
</div>
<h3 style="margin-block-start: var(--space-xl)">The same message, in two chat apps</h3>
<div class="figure-pair">
<figure class="specimen specimen--bad">
<figcaption class="specimen__bar" role="presentation">
<span>Microsoft Teams</span>
<span class="mono">×</span>
</figcaption>
<img src="assets/teams.gif"
alt="Screen recording of Microsoft Teams: as Arabic and English are typed into one message, the cursor jumps and the words reorder unpredictably."
loading="lazy" decoding="async" width="640" height="360">
<figcaption>The cursor jumps. Words reorder as you type. You cannot predict where the next character will land.</figcaption>
</figure>
<figure class="specimen specimen--good">
<figcaption class="specimen__bar" role="presentation">
<span>WhatsApp</span>
<span class="mono">✓</span>
</figcaption>
<img src="assets/whatsapp.gif"
alt="Screen recording of WhatsApp: the same mixed Arabic and English message is typed, and every character stays where the writer put it."
loading="lazy" decoding="async" width="640" height="360">
<figcaption>Same sentence, same two scripts, no drama. So it is evidently not difficult.</figcaption>
</figure>
</div>
</div>
</section>
<!-- ================================================================ -->
<section class="section" id="tracker" data-tracker>
<div class="shell">
<div class="section__head">
<h2>Who has shipped it</h2>
<p class="section__note">
Status as of July 2026. Corrections and additions are welcome — open an
issue on GitHub.
</p>
</div>
<div class="tier">
<div class="tier__head">
<h3>The tools people open every day</h3>
<span class="tier__tag">Highest priority</span>
</div>
<div class="tracker__toolbar">
<button type="button" class="chip" data-filter="all" aria-pressed="true">
All <span class="chip__count" data-filter-count>—</span>
</button>
<button type="button" class="chip" data-filter="done" aria-pressed="false">
Shipped <span class="chip__count" data-filter-count>—</span>
</button>
<button type="button" class="chip" data-filter="pending" aria-pressed="false">
Pending <span class="chip__count" data-filter-count>—</span>
</button>
</div>
<div class="table-wrap">
<table class="tracker-table">
<caption class="visually-hidden">RTL support status for widely used everyday software</caption>
<thead>
<tr>
<th scope="col">Product</th>
<th scope="col">Category</th>
<th scope="col">RTL support</th>
<th scope="col">Notes</th>
<th scope="col">Updated</th>
</tr>
</thead>
<tbody>
<tr data-status="done">
<th scope="row" data-col="product">ClickUp</th>
<td>Work management</td>
<td><span class="badge badge--done">Done</span></td>
<td data-col="notes">
Arabic interface available, and native RTL moved to
<strong>Building Now</strong> with a public beta in July 2026
after 866 votes and six years on the request. See the story below.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="done">
<th scope="row" data-col="product">Notion</th>
<td>Docs & knowledge base</td>
<td><span class="badge badge--done">Done</span></td>
<td data-col="notes">
Arabic interface plus RTL text direction in documents. The
difference was immediate and widely noticed — it is the proof
that a large editor can retrofit this.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="pending">
<th scope="row" data-col="product">Slack</th>
<td>Team messaging</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">
No RTL layout and no Arabic interface. Mixed-script messages,
thread replies and canvases all reorder unpredictably.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="pending">
<th scope="row" data-col="product">Claude Desktop</th>
<td>AI assistant</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">
The model answers in fluent Arabic; the interface renders it
left-to-right. Long Arabic replies, code blocks and lists are
the worst affected.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="pending">
<th scope="row" data-col="product">ChatGPT Work</th>
<td>AI assistant</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">
Same pattern: strong Arabic generation, no RTL layout. Business
and enterprise workspaces inherit the problem organisation-wide.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="pending">
<th scope="row" data-col="product">Discord</th>
<td>Community & chat</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">
No RTL layout. Arabic-speaking communities are among the
platform's fastest growing, and they type around the bug daily.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="pending">
<th scope="row" data-col="product">Zed</th>
<td>Code editor</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">
Bidirectional text in the buffer is unreliable: Arabic strings
and comments inside LTR source reorder, and cursor movement
through them does not match what is on screen.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
<tr data-status="pending">
<th scope="row" data-col="product">T3 Chat</th>
<td>AI assistant</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">
A new product, built on a modern web stack, shipping without
RTL. This is the one that stings — the cost of doing it right
was never lower than at the start.
</td>
<td data-col="updated">Jul 2026</td>
</tr>
</tbody>
</table>
</div>
<p data-tracker-empty hidden class="section__note" style="margin-block-start: var(--space-s)"></p>
</div>
<details class="tier tier--archive">
<summary>
Enterprise and ERP systems — the older backlog (4)
</summary>
<div class="tier--archive__body">
<p>
These were the original entries on this page. They still matter, but they
are no longer where the argument is won: the everyday tools above are what
a whole workforce touches hourly, and they are the ones a procurement
clause can actually move.
</p>
<div class="table-wrap">
<table class="tracker-table">
<caption class="visually-hidden">RTL support status for enterprise and ERP systems</caption>
<thead>
<tr>
<th scope="col">Product</th>
<th scope="col">Category</th>
<th scope="col">RTL support</th>
<th scope="col">Notes</th>
<th scope="col">Updated</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row" data-col="product">SAP ERP</th>
<td>Enterprise resource planning</td>
<td><span class="badge badge--partial">Partial</span></td>
<td data-col="notes">Arabic display is broadly fine; mixed-script data entry and BI reports are not.</td>
<td data-col="updated">Apr 2025</td>
</tr>
<tr>
<th scope="row" data-col="product">Oracle ERP Cloud</th>
<td>Cloud ERP</td>
<td><span class="badge badge--partial">Partial</span></td>
<td data-col="notes">Financial report formatting and mixed-text documents break. Several modules have no RTL layout at all.</td>
<td data-col="updated">Apr 2025</td>
</tr>
<tr>
<th scope="row" data-col="product">Microsoft Dynamics 365</th>
<td>CRM and ERP</td>
<td><span class="badge badge--partial">Partial</span></td>
<td data-col="notes">Core screens are reasonable; dashboards and custom reports are not, and mixed data entry is unreliable.</td>
<td data-col="updated">Apr 2025</td>
</tr>
<tr>
<th scope="row" data-col="product">Odoo ERP</th>
<td>Open-source ERP</td>
<td><span class="badge badge--pending">Pending</span></td>
<td data-col="notes">Limited Arabic support throughout. Reports and mixed-script documents are the biggest gap.</td>
<td data-col="updated">Apr 2025</td>
</tr>
</tbody>
</table>
</div>
</div>
</details>
</div>
</section>
<!-- ================================================================ -->
<section class="section section--ink" id="clickup">
<div class="shell">
<div class="section__head">
<h2>What one comment did</h2>
<p class="section__note">
Evidence that this works, and the reason the page you are reading exists.
</p>
</div>
<div class="story">
<div>
<p>
ClickUp's RTL request was opened in <strong>July 2020</strong>. It gathered
866 votes and sat there. Hundreds of Arabic- and Hebrew-speaking teams
explained, over and over, that they could not use Docs, Chat, Comments or
task descriptions. Nothing moved.
</p>
<p>
In February 2026, <strong>Majd Alhakeem</strong> left a comment on that
thread that did something different. Instead of asking again, he handed the
ClickUp team a way to <em>feel</em> the defect — he linked them to this
site, where a left-to-right reader gets put on the wrong side of the
problem for a few minutes.
</p>
<figure class="quote">
<blockquote cite="https://feedback.clickup.com/languages/p/rtl-language-support">
<p>
I want to draw the ClickUp team's attention to an important point:
RTL support (IS NOT) an aesthetic or optional feature. It is a core
functional requirement for us.
</p>
<p>
I believe many people around the world are simply unaware of how
broken and exhausting this experience is for RTL users. To help
demonstrate this, here is a webpage specifically designed to let LTR
users see and feel what we deal with.
</p>
</blockquote>
<figcaption>
<b>Majd Alhakeem</b>
<span>·</span>
<span>23 February 2026</span>
<span>·</span>
<a href="https://feedback.clickup.com/languages/p/rtl-language-support" target="_blank" rel="noopener">
ClickUp feedback thread
<span class="icon-directional" aria-hidden="true">→</span>
</a>
</figcaption>
</figure>
<p>
Five months later the status changed. That is what awareness is for: not
applause, but a status field moving from silence to <em>Building Now</em>.
</p>
</div>
<div>
<h3>The timeline</h3>
<ol class="timeline">
<li>
<time datetime="2020-07-25">Jul 2020</time>
<span>Sella Yoffe opens “RTL Language support”, asking for text direction and paragraph justification.</span>
</li>
<li>
<time datetime="2025-04">Apr 2025</time>
<span>Perfectly Backwards publishes, built to let LTR readers experience the defect first-hand.</span>
</li>
<li>
<time datetime="2026-02-23">Feb 2026</time>
<span>Majd Alhakeem links the site in the ClickUp thread and reframes RTL as a functional requirement, not a preference.</span>
</li>
<li data-mark="now">
<time datetime="2026-07">Jul 2026</time>
<span><strong>Status changed to “Building Now.”</strong> ClickUp opens a public beta; the thread fills with people asking to join.</span>
</li>
</ol>
<div class="callout" style="margin-block-start: var(--space-m); background-color: oklch(0.24 0.05 264); border-color: oklch(0.34 0.05 264);">
<p class="label" style="color: oklch(0.78 0.02 264)">Progress across the tracked everyday tools</p>
<div class="meter" style="--fill: 25%; background-color: oklch(0.32 0.05 264)">
<div class="meter__fill"></div>
</div>
<p style="margin-block: var(--space-2xs) 0; font-size: var(--step--1); color: oklch(0.85 0.015 264)">
2 shipped, 6 pending. Note which edge that bar fills from right now.
</p>
</div>
</div>
</div>
</div>
</section>
<!-- ================================================================ -->
<section class="section" id="failures">
<div class="shell shell--narrow">
<div class="section__head">
<h2>Four ways it breaks</h2>
<p class="section__note">
Each of these is live on this page right now. Toggle the direction and watch
them resolve.
</p>
</div>
<ol class="failures">
<li class="js-reveal">
<div>
<h3>Bidirectional text and input</h3>
<p>
The worst of the four, because it affects <em>writing</em>, not just
reading. Cursors jump mid-word. Selections grab characters you did not
point at. Full stops migrate to the start of the line. Pasted text
scrambles. Every message becomes a small negotiation with the text
field.
</p>
<p class="sabotage-note">
Neutral characters — <code>. , : ( ) 12/03</code> — take direction from
their neighbours. Without isolation, they land wherever the algorithm
leaves them.
</p>
</div>
</li>
<li class="js-reveal">
<div>
<h3>Layout that never mirrors</h3>
<p>
Navigation belongs on the reading-start edge. Primary actions belong
where the eye finishes. When a layout is written with
<code>margin-left</code> instead of <code>margin-inline-start</code>,
none of it moves — the structure stays pinned to a direction the reader
does not have.
</p>
<p class="sabotage-note">
The numbers down the side of this list are padded with a physical
<code>padding-left</code>. That is the entire bug, reproduced faithfully.
</p>
</div>
</li>
<li class="js-reveal">
<div>
<h3>Icons pointing the wrong way</h3>
<p>
Back and forward arrows, undo and redo, progress bars, sliders, chat
bubble tails, send buttons. All of them carry direction. An unmirrored
“next” arrow in an RTL interface is not a cosmetic slip — it is an
instruction to go the wrong way.
</p>
<p>
Forward, as this page currently renders it:
<span class="icon-directional" aria-hidden="true" style="font-size:1.3em">→</span>
<span class="visually-hidden">an arrow pointing towards the end of the line</span>
</p>
</div>
</li>
<li class="js-reveal">
<div>
<h3>Forms that read out of order</h3>
<p>
Labels rendered after their input. Checkbox captions on the wrong side
of the box. Error messages anchored to an edge the reader is not
looking at. Each is small; together they make a five-field form feel
like a puzzle.
</p>
<form class="demo-form" onsubmit="return false" aria-label="Demonstration form">
<div class="demo-form__field">
<label for="demo-name">Full name</label>
<input id="demo-name" type="text" placeholder="Type here" autocomplete="off">
</div>
<div class="demo-form__field">
<label for="demo-org">Organisation</label>
<input id="demo-org" type="text" placeholder="Type here" autocomplete="off">
</div>
</form>
<p class="sabotage-note">
Those labels are underneath their fields, not above them. Nobody chose
that; a <code>flex-direction</code> simply never got reconsidered.
</p>
</div>
</li>
</ol>
</div>
</section>
<!-- ================================================================ -->
<section class="section section--sunk" id="accessibility">
<div class="shell shell--narrow prose">
<h2>The accessibility double standard</h2>
<p>
Companies publish accessibility statements. They fund screen-reader compatibility,
keyboard navigation, focus management, contrast audits. They map their work to WCAG
clause by clause and announce it in release notes. All of that is genuinely good,
and it took years of advocacy to win.
</p>
<p>
The same organisations then treat right-to-left as a localisation ticket. It waits
behind translation. It gets scoped as “language support”, priced as a market-entry
cost, and deferred to a quarter that never arrives. Meanwhile the failure it causes
is the same class of failure accessibility work exists to prevent: a person who
cannot reliably operate the interface.
</p>
<p>
There is no technical distinction worth defending here. Both are about whether a
human being can use the thing. One of them got a standards body, an acronym and a
budget line. The other got a feedback thread and six years of votes.
</p>
<div class="callout callout--alarm">
<p>
<strong>The uncomfortable version:</strong> if RTL had been written into WCAG in
1999, every product in the tracker above would have shipped it a decade ago.
Nothing about the engineering changed. Only the paperwork would have.
</p>
</div>
</div>
</section>
<!-- ================================================================ -->
<section class="section" id="solution">
<div class="shell">
<div class="section__head">
<h2>There is no excuse left, and there is one lever</h2>
</div>
<div class="grid-2">
<div class="prose">
<h3>The platform already solved this</h3>
<ul>
<li><strong>CSS logical properties.</strong> <code>margin-inline-start</code>, <code>padding-inline-end</code>, <code>text-align: start</code>, <code>inset-inline</code>. Universally supported, not experimental.</li>
<li><strong>The <code>dir</code> attribute and <code>unicode-bidi: isolate</code>.</strong> Wrap your directional runs. That is the mixed-text fix, in one declaration.</li>
<li><strong>The Unicode Bidirectional Algorithm.</strong> A published standard since 1996. Every text engine you depend on already implements it; products just have to stop fighting it.</li>
<li><strong>Component libraries.</strong> Most modern frameworks ship RTL-aware primitives. The integration cost is a fraction of what it was five years ago.</li>
<li><strong>AI coding assistants.</strong> Converting physical properties to logical ones across a codebase is now a mechanical task an agent can do in an afternoon — which removes the last honest objection, cost.</li>
</ul>
</div>
<div class="prose">
<h3>The lever: procurement</h3>
<p>
Feature requests are optional. Contracts are not. The single most effective
action available to a government body or a large enterprise in the region
is to write full RTL and Arabic support into every software purchase as a
<strong>non-negotiable acceptance criterion</strong> — tied to sign-off and
payment, not to a roadmap promise.
</p>
<p>
The moment a vendor cannot invoice without it, RTL stops being a
nice-to-have on someone's backlog and becomes a line in a delivery plan.
Do that collectively, across enough buyers, and it becomes a market
requirement — which is the only language a global product roadmap reliably
understands.
</p>
<div class="callout">
<p style="margin-block-end:0">
<strong>Suggested clause.</strong> “The supplier shall deliver complete
right-to-left interface mirroring and correct bidirectional text
handling for reading, input, search, export and printed or generated
reports. Acceptance testing shall include mixed Arabic–Latin content in
every user-facing surface.”
</p>
</div>
</div>
</div>
<p class="lede" style="margin-block-start: var(--space-xl)">
Build products that feel native to everyone. Think RTL — and if you already do,
say so publicly, because the tracker above is short and it should not be.
</p>
</div>
</section>
<!-- ================================================================ -->
<section class="section section--ink" id="share">
<div class="shell">
<div class="section__head">
<h2>Pass it on</h2>
<p class="section__note">
A comment in the right thread moved a six-year-old request. Yours might move
the next one.
</p>
</div>
<div class="share">
<p class="share__text">
My digital life is #PerfectlyBackwards because of poor RTL support. This page
puts LTR readers on the other side of it for a few minutes — worth your time
if you build software.
</p>
<div class="share__buttons">
<a class="btn"
href="https://twitter.com/intent/tweet?text=My%20digital%20life%20often%20feels%20%23PerfectlyBackwards%20due%20to%20poor%20RTL%20support.%20This%20page%20puts%20LTR%20readers%20on%20the%20other%20side%20of%20it%3A%20https%3A%2F%2Fperfectly-backwards.com%2F%20%40AsimNet"
target="_blank" rel="noopener">Share on X</a>
<a class="btn btn--ghost"
href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fperfectly-backwards.com%2F&title=Perfectly%20Backwards%3A%20RTL%20is%20a%20requirement%2C%20not%20a%20request"
target="_blank" rel="noopener">Share on LinkedIn</a>
<a class="btn btn--ghost"
href="https://github.com/AsimNet/Perfectly-Backwards/issues/new"
target="_blank" rel="noopener">Suggest a product</a>
</div>
</div>
</div>
</section>
<!-- ================================================================ -->
<section class="section" id="comments-section">
<div class="shell shell--narrow">
<div class="section__head"><h2>Comments</h2></div>
<div class="comments">
<script src="https://utteranc.es/client.js"
repo="AsimNet/Perfectly-Backwards"
issue-term="pathname"
label="Utterances"
theme="github-light"
crossorigin="anonymous"
async>
</script>
</div>
</div>
</section>
</main>
<footer class="site-footer">
<div class="shell">
<div class="site-footer__inner">
<div>
<h4>Perfectly Backwards</h4>
<p>Raising the cost of shipping software that points the wrong way.</p>
</div>
<div>
<h4>About this page</h4>
<p>
The English edition renders right-to-left on purpose, using the same failure
modes real products ship: physical CSS offsets, unmirrored directional icons,
meters filling from the wrong edge, and labels ordered after their controls.
The Arabic edition is built correctly throughout.
</p>
</div>
<div>
<h4>Contribute</h4>
<p>
<a href="https://github.com/AsimNet/Perfectly-Backwards" target="_blank" rel="noopener">Source on GitHub</a><br>
<a href="https://github.com/AsimNet/Perfectly-Backwards/issues/new" target="_blank" rel="noopener">Suggest or correct a product</a><br>
<a href="arabic.html" lang="ar" hreflang="ar">النسخة العربية</a>
</p>
</div>
</div>
<p class="site-footer__legal">
Built to raise awareness · نحو عالم رقمي شامل · 2026 ·
<a href="https://twitter.com/AsimNet" target="_blank" rel="noopener">@AsimNet</a>
</p>
</div>
</footer>
<script src="app.js" defer></script>
</body>
</html>