Browse Business Analysts Section 3: Accessibility Requirements

Generate Accessibility Specifications for a Screen

11 fill-in slots · from The AI Prompt Handbook for Business Analysts

Your details

0/11 filled

Generate Accessibility Specifications for a Screen

Generate accessibility specifications for a screen in our mobile app.

SCREEN NAME: [Name]
SCREEN PURPOSE: [What the user does on this screen]
PLATFORMS: iOS (Swift/SwiftUI) and Android (Kotlin/Compose)

UI ELEMENTS:
1. [Element 1]: [Type - button/label/input/etc.][What it does]
2. [Element 2]: [Type][What it does]
3. [Element 3]: [Type][What it does]
4. [Element 4]: [Type][What it does]

For each element, provide:
1. View ID / Accessibility Identifier (following [camelCase/snake_case] convention, prefix: [prefix])
   - iOS: accessibilityIdentifier value
   - Android: testTag or resource-id value
2. Screen reader label (what VoiceOver on iOS / TalkBack on Android says out loud)
3. Screen reader hint (additional context for the action, if applicable)
4. Accessibility trait/role (button, header, adjustable, static text, etc.)
   - iOS: accessibilityTraits
   - Android: semantics role (Role.Button, Role.Heading, etc.)
5. Dynamic content behavior (what the screen reader announces when the value changes)

Also specify:
- Focus order (tab order for screen reader navigation)
- Group elements that should be read as one unit
- Elements that should be hidden from accessibility (decorative only)
- Announcements triggered by state changes (e.g., "Item added to cart")
  - iOS: UIAccessibility.post(notification:) / AccessibilityNotification
  - Android: announceForAccessibility / LiveRegion

Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.