CRITICAL story-no-access-screen-restricted-roles-organization-admin-006 3 pts
3
Story Points
Critical
Priority
No-Access Screen for Restricted Roles
Feature

User Story

As a Organization Administrator
I want the no-access screen to be fully navigable with a screen reader and to display with sufficient contrast and scalable text
So that I can understand the access restriction and my options even if I use assistive technology or have low vision

Acceptance Criteria

  • Given a VoiceOver user lands on the no-access screen, when the screen appears, then the live region announcer triggers an announcement of the denial headline without requiring manual navigation
  • Given a screen-reader user navigates through the no-access screen, when they traverse all focusable elements, then the heading, explanation text, and all action buttons are announced in logical order with appropriate roles
  • Given the no-access screen is displayed, when it is evaluated against WCAG 2.2 AA contrast requirements, then all text elements meet a minimum 4.5:1 contrast ratio against the background
  • Given a user has increased their device font size to the largest accessibility setting, when the no-access screen renders, then all text is fully visible and no content is truncated or overlapping
  • Given the no-access screen contains interactive buttons, when the touch targets are measured, then each button meets the 44×44 dp minimum touch target requirement

Business Value

Blindeforbundet, NHF, and HLF collectively serve users with visual, motor, and cognitive impairments for whom accessibility is not an enhancement but a prerequisite. The no-access screen is a security boundary that all users will encounter, making it a high-visibility touchpoint for accessibility quality. Failures here — such as a screen reader receiving no announcement — directly block users from understanding their situation and recovering, constituting a critical usability failure with potential legal and reputational implications under Norwegian accessibility law (WCAG 2.2 AA is legally required for public digital services in Norway).