Skip to content
This repository was archived by the owner on Sep 15, 2026. It is now read-only.
This repository was archived by the owner on Sep 15, 2026. It is now read-only.

Add a main landmark and an h1 per top-level view (WCAG 1.3.1 / 2.4.1) #56

Open

Description

@gabitoesmiapodo

Priority

Medium — should be addressed soon

User story / Problem statement

Currently, there are no main/nav landmarks and h1 exists only on the home view (WCAG 1.3.1 / 2.4.1): the shell wrapper src/App.tsx:46 is a plain div with no main; the only h1 is in Header (src/components/Header.tsx:17), which renders only on home (src/App.tsx:33); unlock and onboarding views have no h1 (UnlockView's top heading is an h2 at src/views/UnlockView.tsx:50). Screen-reader users cannot skip to main content or orient by heading on non-home views.

Expected outcome

A main landmark wraps the view body and each top-level view exposes an h1.

Acceptance criteria

  • A main landmark wraps the view body.
  • Each top-level view (home, unlock, onboarding) exposes exactly one h1.

Technical notes

Wrap the view body in src/App.tsx:46 in a main element and ensure each top-level view promotes its top heading to h1 (e.g. src/views/UnlockView.tsx:50).

Additional context

Part of epic #28. Severity: Moderate. WCAG 2.2 SC 1.3.1 Info and Relationships / 2.4.1 Bypass Blocks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions