
Apple Hig Expert
Apply Apple Human Interface Guidelines accessibility pillars—VoiceOver labels, 44pt targets, Dynamic Type, and contrast—while building iOS or Apple-platform UI.
Overview
apple-hig-expert is an agent skill for the Build phase that guides Apple HIG-aligned accessibility implementation including VoiceOver, Dynamic Type, contrast, and tap-target requirements.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill apple-hig-expertWhat is this skill?
- Four accessibility pillars: Perceivable, Operable, Understandable, Robust
- VoiceOver: meaningful labels and hints—not generic “Button 1”
- 44×44 point minimum tap targets and Switch Control / AssistiveTouch operability
- Dynamic Type with scaling layouts and no unnecessary text clipping
- Contrast ratios: 4.5:1 normal text minimum (large-text rules per HIG)
- Minimum tap target: 44×44 points
- Normal text contrast minimum: 4.5:1 against background
Adoption & trust: 524 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent-generated iOS UI looks fine visually but fails VoiceOver, Dynamic Type, or contrast expectations.
Who is it for?
Solo builders creating or polishing SwiftUI/UIKit interfaces before TestFlight or App Store submission.
Skip if: Cross-platform web-only products with no Apple-native UI surface.
When should I use this skill?
Building or reviewing Apple-platform UI for accessibility compliance, VoiceOver, Dynamic Type, or contrast.
What do I get? / Deliverables
Screens and components ship with HIG-grounded accessibility labels, targets, and layout behavior assistive technologies can interpret.
- Accessibility-ready component and screen guidance
- Checklist-aligned VoiceOver labels, hints, and layout behavior
Recommended Skills
Journey fit
Build/frontend is where HIG and accessibility requirements become concrete SwiftUI or UIKit implementation choices. Frontend subphase covers perceivable, operable, and understandable UI patterns agents often skip when rushing layouts.
How it compares
Use as an HIG accessibility checklist layer—not as a general Android Material design guide.
Common Questions / FAQ
Who is apple-hig-expert for?
Independent iOS and Apple-ecosystem developers and designers using coding agents who need consistent accessibility guidance in the build loop.
When should I use apple-hig-expert?
During Build frontend while implementing navigation, forms, and custom controls—especially before Ship review or launch ASO when accessibility affects quality perception.
Is apple-hig-expert safe to install?
It is documentation-style guidance without mandated tool calls; review the Security Audits panel on this page for the skill package source.
SKILL.md
READMESKILL.md - Apple Hig Expert
# Accessibility Compliance Guide Accessibility isn't a feature; it's a foundational standard. Apple's design philosophy requires apps to be fully usable by everyone, regardless of their physical or cognitive abilities. ## The 4 Pillars of Accessibility ### 1. Perceivable Information and UI components must be presentable to users in ways they can perceive. - **VoiceOver**: Provide meaningful accessibility labels and hints. Avoid "Button 1". Use "Submit Order" with hint "Double tap to place your order." - **Visuals**: Don't rely on color alone to convey meaning (e.g., use icons + color for errors). ### 2. Operable User interface components and navigation must be operable. - **Tap Targets**: 44x44 points minimum. - **Motor Control**: Support Switch Control and AssistiveTouch. ### 3. Understandable Information and the operation of the user interface must be understandable. - **Predictability**: Use standard Apple UI patterns (Tab Bars, Sidebars) so users already know how they work. ### 4. Robust Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. ## Technical Requirements (2026) ### Dynamic Type Apps must respond to system-wide font size changes. - **Scaling Layouts**: Use Auto Layout or SwiftUI `VStack`/`HStack` that wrap content when fonts get large. - **No Clipped Text**: Text should never be truncated unnecessarily. ### Contrast Ratios - **Normal Text**: 4.5:1 minimum against its background. - **Large Text**: 3:1 minimum. - **Liquid Glass Exception**: Be extremely careful with translucency (vibrancy). If a background is too busy, reduce transparency for accessibility. ### Haptics & Audio - Provide haptic feedback for primary actions (success, failure, selection change). - Ensure all audio content has captions or visual equivalents. ## Checklist for Designers - [ ] Does the app work in Grayscale mode? - [ ] Are all buttons at least 44pt tall? - [ ] Is every icon labeled for VoiceOver? - [ ] Does the layout remain usable at the largest Dynamic Type size? - [ ] Have you tested with "Reduce Transparency" enabled in system settings? # Platform Specific Guidelines While Apple aims for a unified aesthetic (Liquid Glass), each platform has unique ergonomics and hardware constraints. ## iOS (iPhone) Designed for one-handed operation and touch-first input. - **Bottom Navigation**: Primary controls should be reachable by the thumb at the bottom (Tab Bars, Toolbars). - **Safe Area**: Avoid placing UI near the Dynamic Island or the home indicator. - **Dynamic Island**: Use Live Activities and the Dynamic Island for high-value background status (e.g., timers, delivery status). ## macOS (Desktop) Designed for precision cursor input and multitasking. - **Sidebars**: Use for primary navigation. - **Menu Bar**: Always provide standard File, Edit, and View menus. - **Windowing**: Support multi-window environments and Split View. - **Keyboard Shortcuts**: Every primary action must have a `Cmd` + [Key] equivalent. ## visionOS (Spatial Computing) Designed for eyes (gaze) and hands (gestures). - **Windows**: Have a physical presence in space. They cast shadows and reflect light. - **Ornaments**: Floating controls that attach to the edge of a window. - **Gaze-Contingent Feedback**: Elements should react (subtle hover state) when the user looks at them. - **Z-Axis**: Use depth to prioritize content. Closer items are more important. ## watchOS (Wrist) Designed for "Glances" — 2 to 5 second interactions. - **Vertical Layout**: Scroll everything vertically using the Digital Crown. - **Complications**: Design for the watch face to provide high-value data at a glance. - **Full-Bleed Images**: Use the entire screen to reduce the perception of bezels. ## Platform Differences Table | Feature | iOS | macOS | visionOS | |---------|-----|-------|----------| | **Navigation** | Tab Bar / Nav Bar | Sidebar / Menu Bar | Ornaments / Sidebars | | **Input** | Touch / Voice | Mouse / Tr