UI issues on multiple screen:

[cakesoft-swati]

[antuz123]

OpenSpec instruction for this issue:

Please inspect every static screenshot attached to this GitHub issue and fix the UI problems visible in those screenshots.

Scope:

• Static screenshot UI fixes only.
• Ignore video-specific behaviour for this pass.
• Do not change wallet, signer, Recovery Key, QR, inheritance, or transaction logic.
• Do not introduce new screens, new terminology, or new visual patterns.
• Reuse existing Keeper components and design system.

Required process:

• Review each attached screenshot before implementation.
• Identify the exact screen/component shown in each screenshot.
• Fix the visible UI issue shown in that screenshot.
• Prefer fixing shared components if the same issue appears in multiple screens.
• After changes, verify the affected screens against the screenshots.

Areas likely covered by the screenshots:

• Passport setup: segmented control contrast and selected/unselected states must be clearly readable.
• Passport setup: scanner, header, “Upload from Gallery”, and “Finish” must not overlap or clip.
• Recovery Key entry screens: use “Recovery Key” consistently, not “seed key”, “Seed Key”, or “Seed Words”.
• Recovery Key entry screens: input fields, placeholders, entered text, focused state, disabled state, and error state must be readable.
• Recovery Key entry screens: keyboard must not hide active fields, “Need Help?”, or “Next”.
• Recovery Key display screen: masked word boxes and number labels must be clearly visible.
• Reset Inheritance Key screen: fix clipped/misaligned key icon/card layout.
• Reset Inheritance Key screen: avoid user-facing “Re-vault”; use “move bitcoin to a new wallet” if explanation is needed.
• QR screen: QR code must not overlap the header and must scale within its container.
• QR screen: “Copy” and “Next” must remain visible and tappable.
• Toast/banner: must not cover the primary CTA. If shown near the bottom, it should appear above the fixed button area.

Copy rules:

• Use “Recovery Key” for the 12-word backup.
• Use “bitcoin”, not “crypto”.
• Keep button labels short.
• Do not truncate Recovery Key warnings or security-critical copy.
• Do not shrink fonts to force-fit text.

Design requirements:

• Use existing Keeper typography, spacing, cards, inputs, buttons, segmented controls, dropdowns, QR container, toast/banner, and bottom action container.
• Fix contrast using existing theme tokens.
• Respect iOS and Android safe areas.
• Fixed bottom CTAs must not overlap content, keyboard, or toast.
• Scrollable screens must have enough bottom padding.
• Test on small iPhone width, small Android width, and increased system font size.

Acceptance criteria:

• Every static screenshot attached to this issue has been reviewed.
• Every visible UI issue in the static screenshots is fixed.
• Text and controls are readable in normal, focused, disabled, and error states.
• No header, QR, toast, keyboard, or CTA overlap remains.
• Recovery Key terminology is consistent.
• No product logic is changed.
• No new visual system or terminology is introduced.

[cakesoft-swati]

• Verified this issue on Keeper app v 2.5.12(597)