Audit advanced Works with: Any AI

Mobile App Onboarding Accessibility Audit

Table output Has example

Check first-run screens for screen reader and motor access.

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.

Audit the onboarding of a mobile app. Screen-by-screen description including text, buttons, gestures, permissions requests and animations: [ONBOARDING_SCREENS]. Platform: [PLATFORM]. Accessibility features we have tested: [TESTED_FEATURES].

Check labels for controls, focus order, touch target size, gesture alternatives, dynamic type behaviour, contrast, motion, permission prompts explained in plain language, timing, and error messages. State which points need testing with a screen reader on a device.

Return a table with Screen, Problem, Severity (red, amber, green) and Fix, a score from 1 to 10 for operability and clarity, and a device test script. Platform guidelines and legal requirements are [VERIFY].

Add a check of the account creation and sign-in steps, including password managers, one-time codes and biometrics, since onboarding often blocks users here. Suggest how to describe the findings to the product team in terms of user tasks that fail.

Then prepare a user testing plan with people who use assistive technology. Define the participants, such as screen reader users, switch users, people with low vision and people who use voice control, and describe fair payment, consent, accessible materials and support during sessions. Write five tasks based on onboarding, the success measures, and the observation sheet. Explain how to combine the findings with the audit table to prioritise fixes, and how to report back to participants. Add a developer checklist for each release covering labels, focus order, contrast, text scaling, motion and error handling, and an automated test list with its limits. Include guidance on writing release notes about accessibility improvements honestly. Platform guidelines and legal obligations change, so mark them [VERIFY] and confirm with a qualified accessibility specialist.

Add a note on keeping a log of every accessibility issue reported by users after release, with the date fixed and the version that fixed it, so progress can be shown honestly.

Do not claim conformance. Describe barriers by who is affected and what they cannot do, keep the language respectful, and recommend that a qualified accessibility specialist confirm the high-severity findings before I rely on them.

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 Any AI or another assistant.

Screen table (invented fitness app)
Welcome: video auto-plays with no pause; no captions. Red.
Permissions prompt: explains "needs location" but reads as icon only to screen reader. Amber.
Goal selection: cards have no labels; focus order skips third card. Red.
Sign-up: error text in red only, not announced. Red.
Text scaling at largest size cuts off the Continue button. Red.
Score: operability 3, clarity 5.
Device test script: screen reader on, navigate welcome, choose a goal, create an account, reach the home screen.
Platform guidance and legal duties [VERIFY] with a specialist.

• audit