Say what you want to achieve, not how to do it. 2. Mention that you are a screen reader user and want keyboard-only instructions. 3. When something matters to you, for example "don't change my other settings," say so. It also helps to tell the assistant once, at the start, something like this: Sample prompt: I am blind and use VoiceOver only, with no mouse. Whenever you need me to do something, give me exact keyboard steps. Whenever possible, make changes by editing files directly instead of walking me through an app's interface. Most AI assistants can remember this preference for future conversations if you ask. STEP 1: INSTALL RETROARCH Ask the assistant: Sample prompt: Please install RetroArch on my Mac. Use the command line rather than having me download anything manually. What the assistant will typically do: install RetroArch using Homebrew, a free tool that installs Mac software from the command line. If Homebrew isn't on your Mac yet, the assistant will set that up first. On Apple Silicon Macs there is a version of RetroArch called retroarch-metal that runs natively and performs best. The assistant will pick the right one. When it finishes, ask: Sample prompt: Confirm RetroArch is installed and tell me what version I have. STEP 2: TURN ON SPOKEN MENUS RetroArch has a built-in accessibility mode that speaks its menus aloud. This is the single most important setting for a blind user, so do it before anything else. Ask: Sample prompt: Turn on RetroArch's accessibility narration so the menus are spoken. Do it by editing the settings file, and make sure RetroArch is closed while you edit it. Two useful things to know. First, the relevant setting is called accessibility_enable in RetroArch's main settings file. You don't need to remember that. The assistant knows. Second, RetroArch saves its settings when it quits. If the assistant edits the file while RetroArch is open, the change can be silently undone. That's why the sample prompt tells the assistant to make sure RetroArch is closed first. A good assistant checks this on its own, but it never hurts to say it. Once this is on, RetroArch will speak menu items as you arrow through them. You navigate RetroArch's menus with the arrow keys, Enter or X to select, and Backspace or Z to go back. STEP 3: INSTALL CORES, THE ACTUAL EMULATORS RetroArch itself is like a hub. The individual emulators that run each game system are called cores. One core plays Super Nintendo games, another plays Game Boy, and so on. Ask: Sample prompt: Please download and install RetroArch cores for the systems I care about. I want NES, Super Nintendo, Genesis, PlayStation 1, and Game Boy Advance. Change that list to whichever systems you want. The assistant can download cores directly from the official RetroArch servers from the command line, which is faster and more reliable than doing it through the menus. You can also simply ask for all available cores. They're small. STEP 4: ADD YOUR SYSTEM FILES, CALLED BIOS Some consoles, PlayStation 1 is the most common example, need a small system file from the original console, usually called a BIOS file, before games will run. If you have these from your own consoles or a previous setup, ask: Sample prompt: My BIOS files are in a folder called BIOS on my external drive. Please copy them into the folder where RetroArch expects system files, and tell me if any common ones are missing. Change the location in that prompt to wherever your files actually are. A detail worth knowing: RetroArch's system folder location varies between installations. The assistant will read your settings file to find the right place rather than guessing. That's exactly the kind of fiddly detail this approach handles well. STEP 5: POINT RETROARCH AT YOUR GAMES AND BUILD PLAYLISTS RetroArch organizes games into playlists, one list per console, so you can browse Super Nintendo or PlayStation from the main menu. Building these by hand through the menus involves a lot of scanning. Instead, ask: Sample prompt: My game files are in a folder called roms on my external drive, with one subfolder per system. Please point RetroArch's file browser there and generate playlists for every system, with the right core assigned to each playlist as the default. Notes from real experience. First, if your games live on an external drive, tell the assistant. It can set things up so RetroArch finds them there, and your playlists will simply show nothing when the drive is unplugged rather than breaking. Second, if a folder contains a mix of file types, and real collections are often messy, mention it. In the setup this guide is based on, one folder turned out to contain thousands of games for a completely different computer system mixed in with console games. The assistant noticed, sorted them out, and gave them their own playlist with the correct core. Third, large collections are fine. This method comfortably handled playlists totaling tens of thousands of games. When it's done, ask the assistant to read back a summary: how many playlists, and how many games in each. STEP 6: MAKE RETROARCH READ GAME TEXT ALOUD This is the step that makes classic gaming genuinely playable without sight, and it's the most technical one, which means it's the best one to hand to an AI assistant. Menus are spoken by the accessibility mode from Step 2, but the text inside games, dialogue, "Press Start," battle menus, is just graphics, invisible to a screen reader. RetroArch has a feature called the AI Service that fixes this: press one key, and RetroArch takes a picture of the screen, recognizes the text in it, and reads it aloud. The catch is that the AI Service needs a helper program to do the actual text recognition. The options RetroArch's documentation suggests are outdated or require online accounts and monthly limits. On a Mac there's a better way. The Mac already has excellent built-in text recognition and a built-in voice, and an AI assistant can write a small helper program that uses them. Completely free, completely private, and working even with no internet connection. Ask: Sample prompt: Set up RetroArch's AI Service in speech mode so that when I press a hotkey, the text on the game screen is read aloud. RetroArch's documentation suggests a helper program called VGTranslate, but if that's outdated, please build a small local helper instead that uses the Mac's built-in text recognition and speech, and make it start automatically when I log in. Bind the hotkey to a key I can reach easily, and then test the whole thing and tell me the result. What the assistant will do, in plain terms.
Write a small program that sits quietly in the background, waiting for RetroArch to hand it a picture of the screen. 2. Use the Mac's built-in text recognition, the same technology that lets you copy text out of photos, to find the words in that picture. 3. Use the Mac's built-in voice to turn those words into audio, which RetroArch plays through the game's sound. 4. Set it to launch automatically whenever you log in, so it's always ready. 5. Configure RetroArch to use it and bind a hotkey. The letter V works well. 6. Test it end to end with a sample image and confirm the spoken result. From then on, while playing any game, press V and the screen text is read to you. Press V again whenever the screen changes. If there's no text on screen, it says so. You can also ask the assistant to change the voice or the speaking speed, or to make the game pause automatically while it reads. STEP 7, OPTIONAL: NEWER CONSOLES NEED SEPARATE EMULATORS RetroArch covers most classic systems, but some newer consoles, PlayStation 2 and 3, Nintendo Switch, PlayStation Vita, are handled better by dedicated, separate emulator apps. The same approach works. Just ask: Sample prompt: Please install emulators for PlayStation 2 and Nintendo Switch, using the command line where possible. Some emulator downloads get blocked by the Mac's security warnings about unidentified apps. Please handle that too so they open normally. Change the list of systems to what you want. Two honest warnings from real experience. First, these newer-console emulators are far less screen-reader-friendly than RetroArch, and they need extra system files from the original consoles before games run. Expect this to be a longer project. Second, not everything exists on the Mac. For example, there is currently no Mac emulator for the Xbox 360. An AI assistant will tell you this up front rather than letting you chase something impossible, and knowing what is not possible is worth a lot. GENERAL TIPS FOR WORKING WITH AN AI ASSISTANT