Accessibility improvements based on the WCAG 2.1 AA quick-scan (April 2026, v4.2.0). 15 criteria not met, 3 partially met. Most issues are systemic in the sense that shared components (`form-row`, sidebar, `reset.scss`, `app.component`) propagate across all pages. Full report: (incoming) ## Phases I suggest working on these issues in the following order: low-hanging fruit first, high effort low gain issues last. low-effort changes that resolve multiple criteria first, then structural changes that require more work but unlock the remaining criteria. ### Phase 1: quick wins Low effort, resolves ~6 criteria. Single-file or single-variable changes that fix issues across all pages at once (because the root cause is in shared components/config). Landmarks, contrast, lang code, logo alt, button focus, autocomplete attributes. ### Phase 2: structural improvements Medium effort, resolves ~5 criteria. Changes to the canon component architecture that require changes in multiple files, but then it pays off everywhere those components are used. Form label coupling, error message coupling, icon-only buttons, heading hierarchy, dialog/input labeling. ### Phase 3: Refinement Higher effort, resolves ~4 criteria. More complex patterns (in particular ARIA tree view) and scattered smaller fixes. ARIA tree view, aria-live regions, fieldsets, table headers, link underlines, focusable tooltips. ### Process We think about how to bring WCAG compliance into our continuous development process: ESLint a11y rules, axe-core component tests, MR template checklist.