/assistive-access

name: assistive-access
description: Assistive Access implementation for cognitive accessibility including simplified scenes, navigation icons, runtime detection, and design principles. Use when optimizing apps for Assistive Access mode.
allowed-tools: [Read, Glob, Grep]
last_verified: 2026-07-16
review_by: 2027-06-22
os_version: iOS 27 / macOS 27

Assistive Access

Guide for implementing Assistive Access support in iOS and iPadOS apps. Assistive Access (iOS 17+/iPadOS 17+) provides a streamlined system experience for people with cognitive disabilities, presenting simplified interfaces with large controls and reduced complexity.

When This Skill Activates

• User wants to add Assistive Access support to their app
• User asks about cognitive accessibility or simplified interfaces
• User mentions `AssistiveAccess`, `UISupportsAssistiveAccess`, or assistive access scenes
• User needs runtime detection of Assistive Access mode
• User is reviewing accessibility compliance for cognitive disabilities
• User asks about `.assistiveAccessNavigationIcon`

Setup

The Three Integration Levels (WWDC25 238)

• **No adoption**: the app runs in a reduced frame to leave room for the system back

button always shown along the bottom (back returns to the Assistive Access Home Screen). The reduced frame keeps apps built for specific device sizes rendering correctly.

• **Full screen as-is** (`UISupportsFullScreenInAssistiveAccess`): for apps already

designed for cognitive accessibility — AAC apps and similar tools. The app looks identical to normal, just full-screen; requires layout that adapts to arbitrary sizes.

• **`AssistiveAccess` scene** (`UISupportsAssistiveAccess` + the scene below, iOS 26/

iPadOS 26): a tailored experience where native controls automatically render in the large, prominent Assistive Access style and follow the user's grid-or-rows layout setting. Recommended when unsure (WWDC25 238).

The Assistive Access mode itself shipped with iOS 17; the `AssistiveAccess` scene type, `UISupportsAssistiveAccess` key, and `.assistiveAccess` preview trait are iOS 26 APIs.

Step 1: Declare Support in Info.plist

Add these keys to your app's `Info.plist` so the system lists your app as an "Optimized App" in Assistive Access configuration:

<key>UISupportsAssistiveAccess</key>
<true/>

For AAC (Augmentative and Alternative Communication) apps or similar tools that need full-screen presentation:

<key>UISupportsAssistiveAccess</key>
<true/>
<key>UISupportsFullScreenInAssistiveAccess</key>
<true/>

Step 2: Add the Assistive Access Scene

SwiftUI

Add an `AssistiveAccess` scene alongside your standard `WindowGroup`:

@main
struct MyApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }

        AssistiveAccess {
            AssistiveAccessContentView()
        }
    }
}

The system automatically uses the `AssistiveAccess` scene when the device is in Assistive Access mode and falls back to `WindowGroup` otherwise.

UIKit

Use `UIHostingSceneDelegate` with a static `rootScene` property that returns an `AssistiveAccess` scene:

class AssistiveAccessSceneDelegate: UIHostingSceneDelegate {
    static var rootScene: some Scene {
        AssistiveAccess {
            AssistiveAccessContentView()
        }
    }
}

Register the scene configuration in your app delegate with the `.windowAssistiveAccessApplication` role:

func application(
    _ application: UIApplication,
    configurationForConnecting connectingSceneSession: UISceneSession,
    options: UIScene.ConnectionOptions
) -> UISceneConfiguration {
    let config = UISceneConfiguration(
        name: "Assistive Access",
        sessionRole: .windowAssistiveAccessApplication
    )
    config.delegateClass = AssistiveAccessSceneDelegate.self
    return config
}

Runtime Detection

Detect whether Assistive Access mode is active at runtime to conditionally adjust behavior:

struct AdaptiveView: View {
    @Environment(\.accessibilityAssistiveAccessEnabled) var assistiveAccessEnabled

    var body: some View {
        if assistiveAccessEnabled {
            SimplifiedView()
        } else {
            FullFeatureView()
        }
    }
}

Use this to hide advanced features, reduce information density, or switch to larger controls even within a shared view hierarchy.

Navigation Icons

Assistive Access uses large grid-based navigation, and icons paired with text reduce cognitive load. Give **every navigation title** an icon, not just the root (WWDC25 238):

// Paired with the navigation title of each screen
DrawView()
    .navigationTitle("Draw")
    .assistiveAccessNavigationIcon(systemImage: "hand.draw.fill")

// Using a custom image from the asset catalog
GalleryView()
    .navigationTitle("Gallery")
    .assistiveAccessNavigationIcon(Image("custom-icon"))

Design Principles

These six principles guide what to build in your Assistive Access scene.

1. Distill to Core Functionality

Identify the one or two most essential features and present only those. Remove secondary workflows, settings screens, and advanced options.

// ✅ Good: Only the core action
struct AssistiveAccessContentView: View {
    var body: some View {
        VStack(spacing: 24) {
            MessageListView()
            ComposeButton()
        }
    }
}

// ❌ Bad: Exposing the full app with all tabs
struct AssistiveAccessContentView: View {
    var body: some View {
        TabView {
            MessagesTab()
            ContactsTab()
            SettingsTab()
            ProfileTab()
        }
    }
}

2. Clear, Prominent Controls

Use large buttons with ample spacing. Native SwiftUI controls automatically adopt Assistive Access styling, so prefer standard `Button`, `Toggle`, and `Picker` over custom controls.

// ✅ Good: Large, standard controls with generous spacing
VStack(s