Accessibility Test Cases from Specs
7 fill-in slots · from The AI Prompt Handbook for QA Engineers
Your details
0/7 filledAccessibility Test Cases from Specs
Generate accessibility test cases from these accessibility specifications. ACCESSIBILITY SPECS: [Paste the accessibility specs from the user story — view IDs, VoiceOver/TalkBack labels, traits, focus order] PLATFORMS: iOS (VoiceOver) and Android (TalkBack) STANDARD: [WCAG 2.1 AA / Section 508] For each platform, generate test cases covering: SCREEN READER NAVIGATION: - [ ] Every interactive element is reachable by swiping - [ ] Focus order matches the visual layout (top to bottom, left to right) - [ ] Labels are descriptive (not "Button" or "Image") - [ ] Traits/roles are correct (button reads as button, heading as heading) - [ ] Hints provide additional context for non-obvious actions - [ ] Groups are read as single units where specified - [ ] Decorative elements are hidden from the accessibility tree STATE CHANGES: - [ ] Dynamic content changes are announced - [ ] Focus moves correctly after actions (dismiss, submit, error) - [ ] Loading states are communicated - [ ] Error messages are announced immediately SPECIFIC TEST STEPS for each element: 1. Navigate to [element] using [swipe right / tab] 2. Verify VoiceOver/TalkBack reads: "[expected label, value, trait]" 3. Activate with [double tap / enter] 4. Verify [expected behavior and announcement]
Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.