Navigate the Contact List with a Screen Reader
All elements of the Contact List screen must meet WCAG 2.2 AA accessibility requirements. Contact Card Widgets carry semantic labels so screen readers can announce contact name, status, area, and available actions. The Contact Search Bar is reachable without additional navigation steps. Touch targets for all interactive elements meet the minimum size requirements. The View Switcher Widget announces its current state and available options. The filter panel announces filter options and active filter state. All status changes (search results loading, filter applied, offline indicator) are announced via accessibility live regions. This story covers the accessibility layer across all contact list interactions.
User Story
Acceptance Criteria
- Given a VoiceOver or JAWS user navigates to the Contacts screen, when they move through the list, then each contact card announces name, status, area, and available actions in a logical order
- Given a screen reader user reaches the Contact Search Bar, when navigating the screen, then the search bar is reachable without requiring additional navigation gestures beyond standard linear navigation
- Given a screen reader user activates a filter, when the filter is applied and results update, then the change in result count or state is announced via an accessibility live region
- Given a screen reader user interacts with the View Switcher Widget, when they toggle it, then the new view state is announced
- Given any interactive element in the contact list, when measured, then all touch targets are at least 44x44 logical pixels (WCAG 2.2 AA minimum)
- Given an offline indicator is shown, when a screen reader user encounters it, then the indicator text is announced
Business Value
Blindeforbundet (Norwegian Association of the Blind) is a primary client organisation and has visually impaired peer mentors as core users. Screen reader support is not an optional enhancement — it is a prerequisite for those users to participate at all. NHF also serves users with motor and cognitive challenges who rely on assistive technologies. Failing WCAG 2.2 AA compliance risks legal non-compliance and excludes a significant portion of the intended user base from the most-used screen in the application.