Accessibility
24 guidelines • Apple Human Interface Guidelines
Audio
Guidelines for audio content accessibility
Audio Descriptions
WCAG AAProvide audio descriptions for visual media content
Users who are blind or have low vision need descriptions of visual content
Closed Captions
WCAG AProvide captions for all audio and video content
Required for deaf and hard-of-hearing users
Cognitive
Guidelines for cognitive accessibility and clarity
Logical Reading Order
WCAG AContent should follow a logical reading order for screen readers
Ensures content makes sense when read linearly
Error Identification
WCAG AClearly identify and describe errors in form fields
Users need to understand what went wrong and how to fix it
Consistent Navigation
WCAG AANavigation patterns should be consistent throughout the app
Reduces cognitive load and helps users predict interface behavior
Motor
Guidelines for users with motor impairments
Reduce Motion
Respect Reduce Motion setting and provide alternatives to animation
Motion can cause vestibular issues or be distracting for some users
Focus Indicators
WCAG AAAll interactive elements need visible focus states
Required for keyboard and switch control navigation
Full Keyboard Access
WCAG AAll functionality must be accessible via keyboard/switch control
Users with motor impairments may not be able to use touch gestures
Touch
Guidelines for touch-based interactions and target sizes
Minimum Touch Target
WCAG AAAll tappable elements must be at least 44x44 points
44pt × 44ptEnsures users can accurately tap controls regardless of motor ability
Touch Target Spacing
Maintain adequate spacing between touch targets to prevent accidental activation
8pt minimumReduces errors from fat finger taps
Haptic Feedback
Provide haptic feedback for important actions and confirmations
Multi-sensory feedback improves usability and accessibility
Vision
Guidelines for visual accessibility including contrast and text
Text Contrast (Normal)
WCAG AANormal text must have minimum 4.5:1 contrast ratio against background
4.5:1 (AA)WCAG compliance ensures readability for users with low vision
Text Contrast (Large)
WCAG AALarge text (18pt+ or 14pt+ bold) requires minimum 3:1 contrast ratio
3:1 (AA)Larger text is more legible at lower contrast ratios
Enhanced Contrast
WCAG AAAFor AAA compliance, normal text needs 7:1 and large text needs 4.5:1
7:1 / 4.5:1 (AAA)Enhanced readability for users with significant visual impairments
Non-Text Contrast
WCAG AAUI components and graphical objects need 3:1 contrast ratio
3:1Ensures icons, borders, and charts are visible
Minimum Text Size
Body text should be at least 11pt; avoid text smaller than 10pt
11pt minimum (10pt absolute minimum)Ensures text is readable on small screens
Dynamic Type Support
Apps must support Dynamic Type across all text styles
xSmall to AX5 (7 standard + 5 accessibility sizes)Allows users to adjust text size system-wide based on their needs
Color Independence
WCAG ANever use color as the only means of conveying information
Color blind users need additional visual cues like icons, patterns, or text labels
Color Blindness Support
UI should be usable for all types of color blindness
Test with Protanopia, Deuteranopia, Tritanopia filters8% of men and 0.5% of women have some form of color blindness
Reduce Transparency
Respect Reduce Transparency accessibility setting
Transparent or blurred backgrounds can be distracting or hard to read for some users
Increase Contrast Mode
Provide higher contrast when Increase Contrast setting is enabled
Users with low vision may need higher contrast to distinguish elements
VoiceOver Labels
WCAG AAll interactive elements must have meaningful accessibility labels
Screen reader users rely on labels to understand interface elements
VoiceOver Hints
Provide hints for non-obvious interactions
Helps screen reader users understand how to interact with elements
VoiceOver Traits
Apply appropriate accessibility traits (button, link, header, etc.)
Helps screen readers announce elements correctly