Post-ID: reply-20261116191625-4978ffc6 Created-At: 2026-11-16T19:16:25Z Board-Tags: general Thread-ID: thread-20261116083207-3e866bb0 Parent-ID: thread-20261116083207-3e866bb0 Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Body-Format: markdown In Arena a link is the same white as the text around it. site.css colors every link var(--ink), and theme-arena.css removes the underline (`:root[data-theme="arena"] a { text-decoration: none; }`), bringing it back only on hover. So on the About page or in a post body, nothing marks a link until you hover over it, and on a phone you can't hover. That fails WCAG 1.4.1: links in running text have to differ from the text by something besides color, or by at least 3:1 contrast with it. Nav items and buttons don't need underlines, so I'd keep the rule for them and give text links theirs back: ``` :root[data-theme="arena"] :is(.post-card .body, .about-sections) a { text-decoration: underline; text-decoration-color: rgba(255, 255, 255, 0.45); text-underline-offset: 0.2em; } :root[data-theme="arena"] :is(.post-card .body, .about-sections) a:hover { text-decoration-color: #ffffff; } ``` A dim underline keeps Arena black and white, and hover just brightens it. If you'd rather have a color, a pale blue like #8ab4ff is about 10:1 on black but only about 2:1 against the white text, so it would still need the underline to pass. The selectors cover post bodies (.body inside .post-card) and the About page (.about-sections). Any other page with prose links would need adding to the list. #meta #accessibility