[drmowinckels]

Why this is separate

Cut from main, not from the landing-page work, so it can merge on its own. These defects are live today and none of the fixes depend on any redesign decision. PRs #23, #24 and #25 can rebase onto this and inherit them.

What was found

axe-core 4.14 (WCAG 2.0/2.1/2.2 A + AA, plus best-practice) over every route in the sitemap, both languages, desktop and mobile, including the open mobile menu — 222 violations across 7 types. Now zero, plus 44/44 manual checks.

	Fix
Contrast 1.4.3	--color-primary as a text colour is 3.10:1 on dark, 2.68:1 on grey — below AA everywhere it appeared. Text uses now --color-primary-text (5.29/4.58); background and border uses unchanged. --color-light is 4.09:1 on grey, so small text moved to --color-muted. Chroma's monokai code comments were 3.03:1 → github-dark at 6.15:1.
Links in prose 1.4.1	Body links were colour-only at 1.36:1 against surrounding text. Now underlined.
Headings	List pages had no h1 at all. Their section title is now the page heading, with cards moving h3 → h2 so levels never skip. Team profiles made the generic "About Member" the only heading and the person's name an h3 — the name is now the h1. A news post started at h3. A titleless section rendered an empty h2.
Landmarks / bypass 1.3.1, 2.4.1	The banner sat outside <main>. There was no skip link at all.
Reflow 1.4.10	Long code lines widened the entire page at 320px instead of scrolling inside their own block.
Empty page	/funfacts/ published a page with no content and no heading. It is data for the home-page counters, so it no longer renders as a page — counters and background image unaffected.

The one worth reading about

.reveal starts at opacity: 0 and is only revealed by scroll-reveal.js. All page content was gated on JavaScript running and on the IntersectionObserver firing. It now renders immediately under prefers-reduced-motion, with a <noscript> fallback. This bit me twice while testing — screenshots caught blank sections mid-fade, which is the same failure a crawler, a print stylesheet or a headless renderer would hit.

Test plan

CI builds both languages. What it does not check, and what I ran manually:

• axe-core over all sitemap routes × 2 languages × 2 viewports + interactive states
• Skip link is the first tab stop and visible on focus; no keyboard trap; focus indicators on every interactive element
• prefers-reduced-motion honoured and content still visible without the observer
• No horizontal scroll at 320px (400% zoom) or 640px (200% zoom)
• alt text, lang and title on every page

Two honest caveats:

1. Automated tooling catches roughly a third of real accessibility problems. Zero violations is a floor, not a ceiling — it cannot tell you whether alt text is meaningful or how the site sounds in VoiceOver. A pass with a real screen reader is still worth doing.
2. I initially recorded a reflow failure on the nav that was an artifact of how I emulated zoom (body { zoom } does not shrink the CSS viewport, so media queries never switch to mobile). Corrected to resize the viewport, which is what browser zoom actually does. The nav is fine; the code blocks genuinely were not.

🤖 Generated with Claude Code

[github-actions]

✅ Preview deployed at https://26--capro-uio.netlify.app
Please check it looks ok before merging.

[github-actions]

✅ Accessibility: no issues

axe-core over 31 routes × 2 viewports (one page per layout), plus 67 manual checks.

All 67 manual checks passed.

_{Automated tooling catches roughly a third of accessibility problems. A clean run is a floor, not a ceiling.}