CRITICAL story-contact-and-notes-search-organization-admin-006 5 pts
5
Story Points
Critical
Priority
Contact & Notes Search
Feature

User Story

As a Organization Administrator
I want the search screen and all search interactions to be fully accessible via screen readers (VoiceOver, TalkBack) and keyboard/switch access navigation
So that coordinators and peer mentors who rely on assistive technology can use search equally effectively without encountering inaccessible barriers

Acceptance Criteria

  • Given a screen reader is active, when the search screen opens, then the search input field is announced with a descriptive label (e.g., 'Search contacts and notes')
  • Given search results update, when new results are rendered, then a live region announces the result count (e.g., '5 results found')
  • Given the results list is navigated via screen reader, when each result is focused, then the contact name, type (peer mentor or contact), and chapter are announced
  • Given an empty state is shown, when a screen reader focuses the empty state, then the empty state message is fully readable as text (not image-only)
  • Given switch access navigation is used, when traversing the search screen, then focus order follows a logical sequence: input → filter controls → results list
  • Given the search input has focus, when the user submits via keyboard return, then the search executes and focus moves to the first result

Business Value

Accessibility is a non-negotiable MUST HAVE for all organizations, listed as Phase 1 priority. Blindeforbundet's users include people who are blind or visually impaired and depend entirely on screen readers for app interaction. Failing to make search accessible would exclude a core user segment from a critical feature, violating both the organizations' missions and WCAG 2.2 AA compliance requirements that underpin funding and regulatory obligations.