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.

Replace window.confirm vault reset with the in-app DangerConfirm/Sheet (WCAG 4.1.2) #57

Open

Description

@gabitoesmiapodo

Priority

Medium — should be addressed soon

User story / Problem statement

Currently, vault reset uses a native window.confirm (WCAG 4.1.2 / internal consistency): src/views/UnlockView.tsx:35 triggers a destructive action via window.confirm, whereas elsewhere the app uses the accessible DangerConfirm/Sheet pattern. The native dialog is inconsistent and less accessible than the in-app pattern.

Expected outcome

Vault reset uses the in-app DangerConfirm/Sheet pattern instead of window.confirm.

Acceptance criteria

  • Vault reset routes through the existing Sheet + DangerConfirm pattern rather than window.confirm.

Technical notes

Replace the window.confirm call in src/views/UnlockView.tsx:35 with the existing Sheet + DangerConfirm components used elsewhere in the app.

Additional context

Part of epic #28. Severity: Moderate. WCAG 2.2 SC 4.1.2 Name, Role, Value; consistency with the app's accessible confirm pattern.

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