Access the Organization Selection Screen with a Screen Reader
Blindeforbundet's users include visually impaired peer helpers for whom screen reader support is not a nice-to-have but a hard requirement. The org selection screen must be fully navigable with VoiceOver (iOS) and TalkBack (Android). Every interactive element — organization cards, the selection action, error messages, and the progress indicator — must have correct semantic labels, focus order, and role announcements. The wcag-semantics-label-resolver (688-wcag-semantics-label-resolver), semantics-wrapper-widget (606-semantics-wrapper-widget), and live-region-announcer (608-live-region-announcer) are used to ensure compliance. Organization names and role labels resolved via the terminology system must also be correctly surfaced to accessibility services.
User Story
Audience Summaries
Blindeforbundet — one of the four founding partner organizations — has a hard contractual and ethical requirement for full screen reader accessibility on all core platform screens. Their peer mentors are themselves visually impaired individuals serving other visually impaired people, meaning inaccessible entry screens would completely exclude an entire founding organization from using the platform. This story ensures WCAG 2.2 AA compliance on the org selection screen, fulfilling the legal accessibility obligation under Norwegian universal design law, protecting the contractual relationship with Blindeforbundet, and demonstrating the platform's commitment to inclusive design — a significant trust signal for future nonprofit partners operating in the disability services sector.
This story has a hard dependency on story-organization-selection-screen-peer-mentor-001 and must be delivered in the same release window as the base org selection screen. The scope involves integrating three accessibility infrastructure components — wcag-semantics-label-resolver (688), semantics-wrapper-widget (606), and live-region-announcer (608) — with the existing card UI. QA requires physical device testing on both iOS (VoiceOver) and Android (TalkBack), with specialized accessibility testers or tooling such as Accessibility Scanner and Xcode Accessibility Inspector. Acceptance criteria include a formal WCAG 2.2 AA audit pass, adding compliance verification overhead to the sprint.
Stakeholder sign-off from Blindeforbundet's representative is recommended before marking this story as accepted. Risk of underestimating testing effort is high given platform and screen reader variability.
Implementation requires wrapping all interactive elements on the org selection screen with the semantics-wrapper-widget (606-semantics-wrapper-widget) to provide correct semantic roles, labels, and focus order for both VoiceOver and TalkBack. The wcag-semantics-label-resolver (688) must resolve dynamically loaded organization names and role labels from the terminology system into accessible strings before they reach the accessibility tree. The live-region-announcer (608) must be triggered on: initial list load completion, selection confirmation, and error states — ensuring screen reader users receive real-time feedback without manual navigation. Focus must be programmatically placed on the first card on screen load.
The onboarding progress indicator requires an accessible description string. Edge cases include cards with missing logos or branding data (fallback labels required), and error states announced as assertive live regions. All changes must be tested against WCAG 2.2 AA success criteria 1.1.1, 1.3.1, 2.1.1, 2.4.3, and 4.1.2.
Acceptance Criteria
- Given I am a VoiceOver user on iOS, When the org selection screen loads, Then focus is automatically placed on the first organization card and VoiceOver announces the organization name, my role, and that the card is tappable
- Given I am using a screen reader, When I navigate through the list of organization cards, Then each card is announced with the organization name, my role within that organization, and any relevant status information
- Given I am using a screen reader, When I double-tap to select an organization, Then VoiceOver announces confirmation of the selection and that the app is loading the home screen
- Given an error occurs loading the organization list, When I am using a screen reader, Then the error message is announced via a live region without requiring me to navigate to it manually
- Given the onboarding progress indicator is visible, When I am using a screen reader, Then the step progress is announced as part of the screen's accessibility description
- Given the org selection screen is displayed, When I run an accessibility audit, Then there are no WCAG 2.2 AA violations on this screen
Business Value
Blindeforbundet — one of the four founding organizations — explicitly requires full screen reader support (VoiceOver/JAWS) as a hard requirement, not a future enhancement. Their peer mentors are themselves visually impaired individuals serving other visually impaired people. A screen-inaccessible org selection screen would categorically exclude Blindeforbundet's peer mentors from using the platform entirely, making it impossible to deliver the contracted solution to this organization. WCAG 2.2 AA compliance on the entry screens is therefore a contractual and ethical obligation.
Components
- Semantics Wrapper Widget ui
- Live Region Announcer ui
- Screen Reader Detection Service service
- Accessibility Audit Service service
- Semantics Service Facade infrastructure
- WCAG 2.2 AA Compliance Checker infrastructure
- Accessibility Live Region Announcer infrastructure
- Organization Selection Screen ui
- Organization Card Widget ui
- WCAG Semantics Label Resolver infrastructure