apple-design-accessibility
Skill1 starsChanged 51 days agoMITView on GitHub
Design or audit accessible and inclusive Apple-platform interfaces, including VoiceOver, larger text, alternate inputs, motion accommodations, and right-to-left localization.
In this repository32 other files it gives its agents.
- grok-firstSkill
- opencode-firstSkill
- apple-design-aiSkill
- apple-design-commerceSkill
- apple-design-connected-technologiesSkill
- apple-design-contentSkill
- apple-design-controlsSkill
- apple-design-foundationsSkill
- apple-design-gamesSkill
- apple-design-healthSkill
- apple-design-inputsSkill
- apple-design-iosSkill
- apple-design-mediaSkill
- apple-design-menusSkill
- apple-design-navigationSkill
- apple-design-patternsSkill
- apple-design-platformsSkill
- apple-design-presentationSkill
- apple-design-principlesSkill
- apple-design-privacy-identitySkill
- apple-design-spatialSkill
- apple-design-system-experiencesSkill
- design-maestroSkill
- forjaSkill
- product-studioSkill
- temperaSkill
- bambu-h2c-slice-printSkill
- bambu-print-troubleshootSkill
- blender-print-readySkill
- fdm-print-preflightSkill
- ads-videoSkill
- tutorial-videoSkill
The file
Files
Apple Accessibility and Inclusion
Apply the skill
Begin with a real task path, including error recovery. Evaluate whether it remains operable and understandable through the relevant combinations of vision, hearing, motor, cognitive, and language needs. Read the specific references that apply; do not reduce accessibility to a contrast score.
For a review, report the blocked task, affected interaction or setting, evidence, and smallest useful fix. A screenshot can reveal visual risks but cannot prove focus order, labels, gestures, announcements, or keyboard behavior. Separate inspected behavior from untested assumptions.
For implementation, prefer built-in semantics and accessibility settings, and verify custom components with the actual assistive technology. Test localization with meaningful text and bidirectional content. State what was tested and which checks still require a device or participant.
Topic references
Select the topic that matches the design decision; do not load this entire list by default.
- Accessibility
- VoiceOver
- Inclusion
- Right to left
Source use
These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.
Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.
The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

