Skip to content

[P3][Memory-Retrieval] Name phone switches and text fields for screen readers #329

Closed

Description

@bloodf

User outcome

A screen-reader user can name every switch and text field on the phone memory pages.

Gap (found by #103)

mobile/src/ui/forms.tsx: ToggleRow renders <Switch> with no accessibilityLabel (its title is a sibling Text), and FieldRow renders <TextInput> with its label as a sibling Text only. The phone memory pages use these for automatic recall, capture conversation, group capture, recall budgets, per-turn cap, connection/endpoint/embedding fields, secret entry and OpenViking bindings, so those controls have no accessible name (#101 acceptance: every control has an accessible name). Row/MemoryAction/menus are fine (Pressable text; menu has title, value label).

Proposed change

Root fix in forms.tsx: Switch accessibilityLabel={title}; TextInput accessibilityLabel={props.accessibilityLabel ?? label ?? props.placeholder}. One test in forms.test.ts. No new dependency; no memory page rewrite.

Acceptance

  • Every ToggleRow and labelled FieldRow exposes its title/label as accessible name
  • Focused check in mobile/src/ui/forms.test.ts

Found by #103. Parent: #16.

Current delivery boundary

Keep narrow shared-form accessible-name fix separate from memory localization #330. Draft #362 has zero changed files and does not prove work shipped. Link parent assessment #103 and generic audit #159.

Priority: normal (urgency, separate from roadmap P3). Foundational delivery or acceptance within the existing roadmap; no evidence of a current critical incident.

Related implementation history: #332, #362. Draft, source review, publication and merge are separate from the acceptance evidence required by this issue.

The published draft currently has zero changed files; preserve any unpublished work and confirm the next owner before resuming.

Existing PR review — 2026-10-19

Draft #362 remains open at 9cbb966b142b95fa835897f3e6323832da796e66 with zero changed files, also verified against current main 4760281f2b9cb24eec4438a473e7226cd4e3980c. It is a reservation, not a completed implementation or a ready merge. No acceptance boxes were checked and no feature/runtime result was inferred. Existing historical assessments retain their original revisions and limitations. Resume only with a bounded result and preserved unpublished work; phase, labels, dependencies and Project fields remain unchanged.

Activity

  1. added
    roadmapManaged Beans capability roadmap
    phase:P3Roadmap phase P3; not a blanket dependency
    area:memoryBeans memory workstream
    on Oct 13, 2026
  2. added
    priority:normalUrgency: normal; schedule after high-priority work. Independent of roadmap phase.
    platform:androidScope: Android; implementation and acceptance require target-specific evidence.
    platform:iosScope: iOS; implementation and acceptance require target-specific evidence.
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:memoryBeans memory workstreamphase:P3Roadmap phase P3; not a blanket dependencyplatform:androidScope: Android; implementation and acceptance require target-specific evidence.platform:iosScope: iOS; implementation and acceptance require target-specific evidence.priority:normalUrgency: normal; schedule after high-priority work. Independent of roadmap phase.roadmapManaged Beans capability roadmaptype:implementationRoadmap implementation

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions