/* Directional arrow on the T2 related-guides links ("Read Guide", "View all").
 *
 * The glyph used to be a literal → inside the PHP string. That forced the
 * Arabic value to carry either a wrong-facing → or a mirrored ←, so the two
 * translations would have differed by DIRECTION as well as by language, and the
 * mirrored form would have to be re-decided every time the copy was
 * re-translated. The arrow is presentation, so it lives here: one rule, flipped
 * on [dir="rtl"] — the convention the other ~115 RTL rules in this theme use.
 * Batch 1, Greg 2026-09-08.
 *
 * .rp-related-guide-link itself is styled in migration.css, which is FROZEN and
 * served minified; this file only adds the pseudo-element, and is enqueued on
 * compliance (T2) pages after rp-migration. If the arrow is missing on a T2
 * page, check that this stylesheet reached the page before touching the copy —
 * the values in rp_cp5_label()'s map must not get a glyph put back into them
 * (Greg, 09-08: that is a question for him, not a value to patch).
 *
 * Accessibility, stated rather than assumed: generated content IS exposed to
 * the accessibility tree, so some screen readers will announce this as "right
 * arrow" after the link text. That is the same behaviour the literal glyph in
 * the string had — it was inside the link text — so this is not a regression,
 * and it is now fixable in one place. `speak` is not implemented by any engine,
 * so it is deliberately not used here to pretend otherwise.
 */
.rp-related-guide-link::after {
  content: "\2192"; /* → */
  display: inline-block;
  margin-inline-start: 4px;
}

[dir="rtl"] .rp-related-guide-link::after {
  content: "\2190"; /* ← */
}