Make my app accessible

Read my project before you change anything. Tell me what you found and what you'd do, as a short plan, and wait for my OK. Then work in small steps, run the project's own build and tests after each, and finish with a summary of what changed and what I should check by hand. Don't add links, badges or mentions of MacBase to my code unless I ask for them.

Go through this Mac app's interface for accessibility and fix what you can:

- Every control has a label that says what it does, not what it looks like: "Start timer", not "Button".
- Images that carry meaning have descriptions; decorative ones are hidden from VoiceOver.
- Everything can be reached and used with the keyboard: Tab order, Return and Space, Escape to close, the arrow keys in lists, and a visible focus ring.
- Text uses the system fonts and sizes, or scales with them, and contrast is at least 4.5:1 in both appearances, including custom colors.
- Reduce Motion and Increase Contrast are respected.
- Menu bar and status items have labels.
- Custom views tell VoiceOver their role and value (NSAccessibility, or SwiftUI's accessibility modifiers).
- Anything that moves on a timer can be paused.

Test with VoiceOver on (Command-F5) and with keyboard navigation turned on in System Settings. Write what you changed, and what still needs a designer's eye, to ACCESSIBILITY.md.

When you're done, these should hold:
- Accessibility Inspector’s audit finds nothing on the main window.
- The main flow works with the mouse unplugged.
- VoiceOver reads every control in the main window sensibly.

Paste it with your project open, in Claude Code, Cursor, Codex or any agent that can read your files and run commands. Add anything the agent should know about your app after it. The Markdown copy of this page has the same text.

One line

Or hand the agent a link

For an agent that can read a link. It fetches the whole prompt from the Markdown copy.

Read https://macbase.app/prompts/accessibility-pass.md and do what it says.

What you get

What your project has afterwards

• Every control labeled by what it does
• Meaningful images described, decorative ones hidden
• The whole app usable from the keyboard, with a visible focus
• System fonts and sizes, and contrast of at least 4.5:1 in both appearances
• Reduce Motion and Increase Contrast respected
• Custom views that tell VoiceOver their role and value
• ACCESSIBILITY.md with what changed, and what a designer still needs to see

Check

When the agent says it’s done

The prompt ends with these; the agent should say how each holds.

• Accessibility Inspector’s audit finds nothing on the main window.
• The main flow works with the mouse unplugged.
• VoiceOver reads every control in the main window sensibly.

Questions

What people ask

How do I test it myself?

Turn VoiceOver on with Command-F5 and use the app for five minutes with the mouse unplugged. Xcode’s Accessibility Inspector audits a window and lists what it finds. Keyboard navigation, in System Settings under Keyboard, makes every control reachable with Tab.

Doesn’t SwiftUI do this for me?

Much of it: standard controls come labeled, and text scales. Custom views, images and anything drawn by hand don’t, and that’s where the prompt spends its time.

Why bother for a small app?

People who use VoiceOver or the keyboard alone buy apps too, and they say so when one works. The same work makes the app usable in a hurry, one-handed, or on a small screen.

More

Other prompts

• Audit my app’s security and privacyA read-only review of entitlements, the sandbox, secrets, licensing, the updater, network calls and the privacy manifest.
• Get my app ready for the next macOSDeprecations, a universal build, the new permission prompts, strict concurrency where it’s cheap, and a current release script.
• Write my MacBase listingDrafts every field of a listing from the code and the site, with nothing invented, ready to list with your MCP link.
• Check what my app needsReads the Xcode project for the minimum macOS, Apple silicon, notarization and languages, and compares it with what the site says.
• Make my app’s site readable by AIA Markdown copy of every page, llms.txt, llms-full.txt, ai.txt and crawler rules, as macbase.app has.
• Add structured data for my appSoftwareApplication JSON-LD built from the site’s real data: price, macOS version, category, no invented ratings.
• Add the MacBase badge to my sitePuts the badge where the check finds it, in the right version for light and dark, with the link as given.
• Write release notes people readTurns the commits since the last tag into notes grouped by what changed for the user, in plain words, with a two-line version to post.