Accessibility and Cross-Browser Test Coverage Review
Check front-end testing beyond the happy path.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review front-end test coverage. Browsers and devices supported: [SUPPORTED_ENVIRONMENTS]. Current tests (unit, component, end-to-end, accessibility checks): [FRONTEND_TESTS]. Check coverage of keyboard use, focus handling, labels, error states, responsive layouts, slow networks, and the main supported browsers. Note what automated checks can and cannot detect and where manual testing is needed. Return a matrix of flows against environments, gaps with suggested tests, and a short manual test script. Standards references should be confirmed [VERIFY]. Add a worked matrix with invented flows: sign-in keyboard yes, screen reader no, small screen yes, slow network no; checkout keyboard partial, screen reader no, small screen yes. Suggest automated checks for labels and contrast, plus a manual script of 20 minutes per flow. List browser versions to test, based on analytics supplied by me. Note that automated checks catch only part of the problems. Add a short manual script for a keyboard and screen reader pass of one key flow, with expected spoken output at each step, and a list of browsers and versions based on the usage data I supply. Record issues in a shared log.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.