From 4280383c9befd86d8d4e34219d2a21c1043f1f7a Mon Sep 17 00:00:00 2001
From: Ole-Morten Duesund <olemd@glemt.net>
Date: Mon, 25 May 2026 14:25:52 +0200
Subject: [PATCH] fix(a11y): use h2 in PublicList to avoid duplicate h1
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

App.svelte already renders <h1>Vinterliste</h1> in the nav, so the
PublicList page's <h1>{displayName || username}</h1> produced a
two-h1 document — screen-reader users navigating by headings would
see two top-level entries that aren't actually peers.

Switched to <h2>, kept the larger font size inline so the visual
hierarchy is unchanged. Every other view (Home/Profile/Admin/Feedback)
already follows the "nav h1, view h2" pattern; this brings PublicList
in line.

Surfaced by /audit a11y (semantic structure lens).
---
 frontend/src/components/PublicList.svelte | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/frontend/src/components/PublicList.svelte b/frontend/src/components/PublicList.svelte
index 0a63528..2d79382 100644
--- a/frontend/src/components/PublicList.svelte
+++ b/frontend/src/components/PublicList.svelte
@@ -49,7 +49,7 @@
   {:else if error}
     <p class="error">{error}</p>
   {:else}
-    <h1>{displayName?.trim() || username}</h1>
+    <h2 style="font-size: 1.75rem; margin-top: 0.5rem;">{displayName?.trim() || username}</h2>
     <p class="muted">Offentlige vinteraktiviteter</p>
     {#if !activities.length}
       <p class="muted">Ingen offentlige aktiviteter ennå.</p>