screen-reader-accessibility-testinglisted

# Screen Reader Accessibility Testing ## Objective Verify that people using screen readers or keyboard-only navigation can understand, operate, and recover from critical product journeys without relying on visual presentation. ## Test matrix Select combinations proportionate to supported users and risk: - Windows: NVDA with Firefox or Chrome. Add JAWS with Chrome or Edge when required. - macOS and iOS: VoiceOver with Safari. - Android: TalkBack with Chrome. - Windows built-in coverage: Narrator with Edge when it is a supported combination. Record assistive-technology, browser, operating-system, and application versions. Do not generalize one combination's result to every platform. ## Workflow 1. Define critical journeys, supported combinations, expected outcomes, test accounts, data, exclusions, and WCAG 2.2 Level AA target. 2. Test keyboard-only operation first. Verify logical order, visible focus, skip mechanisms, traps, menus, dialogs, popovers, grids, shortcuts, and recovery. 3. Navigate by headings, landmarks, links, controls, form fields, tables, and other relevant rotor or element lists. Verify structure and discoverability. 4. Check every control's accessible name, role, state, value, description, instructions, and error association. Confirm visual labels match spoken labels. 5. Exercise forms, validation, authentication, search, filters, sorting, pagination, uploads, notifications, destructive actions, and completion feedback. 6. Verify focus placement and an