Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

duo-accessibility

Makes iPhone Duo apps work with VoiceOver, Dynamic Type, Reduce Motion, Increase Contrast, hardware keyboards, Switch Control and Voice Control on both displays. Use it when VoiceOver reads two panes row by row or loses its place after the phone folds or unfolds, when text truncates or clips on the 5.4-inch outer display at large text sizes, when a hinge effect or resize animation ignores Reduce Motion, when colours fail contrast, when keyboard shortcuts or focus don't work, or when you add accessibility labels, identifiers or audits. Covers accessibilityElement(children: .contain), accessibilitySortPriority, AccessibilityFocusState with a delayed move after a size-class change, AnyLayout and ViewThatFits reflow with isAccessibilitySize, ScaledMetric, accessibilityReduceMotion with onHingeChange, colorSchemeContrast, keyboardShortcut, accessibilityInputLabels, modifiers before .position, Accessibility Inspector, performAccessibilityAudit and XCUIDevice voiceOverService UI tests on the

Kimeur · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Kimeur/duology --skill duo-accessibility

About this skill


name: duo-accessibility description: "Makes iPhone Duo apps work with VoiceOver, Dynamic Type, Reduce Motion, Increase Contrast, hardware keyboards, Switch Control and Voice Control on both displays. Use it when VoiceOver reads two panes row by row or loses its place after the phone folds or unfolds, when text truncates or clips on the 5.4-inch outer display at large text sizes, when a hinge effect or resize animation ignores Reduce Motion, when colours fail contrast, when keyboard shortcuts or focus don't work, or when you add accessibility labels, identifiers or audits. Covers accessibilityElement(children: .contain), accessibilitySortPriority, AccessibilityFocusState with a delayed move after a size-class change, AnyLayout and ViewThatFits reflow with isAccessibilitySize, ScaledMetric, accessibilityReduceMotion with onHingeChange, colorSchemeContrast, keyboardShortcut, accessibilityInputLabels, modifiers before .position, Accessibility Inspector, performAccessibilityAudit and XCUIDevice voiceOverService UI tests on the iPhone Duo simulator." metadata: verified: "Xcode 27.1 (27A9275), iOS 27.1 simulator, device: no" sources: "https://github.com/Kimeur/duology/blob/main/reference/sources.md"

duo-accessibility

iPhone Duo changes shape while people use it. One pane becomes two, a row of text gets about twice the width, the window jumps to another display. Accessibility settings don't change with it: the same VoiceOver user, text size and Reduce Motion setting meet every layout. This skill makes each layout work for them.

Load neighbours for depth: duo-design-system (type scale, colour tokens, contrast checks), duo-transitions (animating the resize), duo-postures (hinge effects), duo-ergonomics (44 pt targets), duo-testing (UI test setup), duo-shared-screen (two people, one screen).

Labels: measured means we ran it in a probe app with UI tests on the shared iPhone Duo simulator (Xcode 27.1, iOS 27.1, 18 October 2026). Unverified means we could not confirm it. Everything else links to Apple. Details: references/evidence.md.

Rules

  1. Make each pane a VoiceOver container. Two panes side by side are read row by row otherwise.
  2. Keep the pane order stable in every pose. Change it only with accessibilitySortPriority, never by pose.
  3. After a fold or unfold, put VoiceOver back where the person was. Wait for the new layout first.
  4. Reflow at large text sizes. Never truncate or clip. Design the closed outer display at the largest size first.
  5. Under Reduce Motion: no hinge effects, no moving or zooming resize animations. Fades only.
  6. Check every custom colour with Increase Contrast on, in light and dark. Never show state with colour alone.
  7. Give every main command a keyboard shortcut and a label. Every drag, swipe and hinge input needs a button or a named action.
  8. Use system controls. Give icon-only buttons a title (Label), because vertical bars hide it on screen and VoiceOver, Voice Control and the overflow menu still need it. Give your own icon-only buttons a 44 pt frame inside the label.
  9. Put accessibility modifiers, contentShape and gestures before .position.
  10. Test closed, open and partly folded: Accessibility Inspector by hand, performAccessibilityAudit and a VoiceOver walk in UI tests.

1. VoiceOver order across two panes

VoiceOver reads top to bottom, then leading to trailing, the way people read the language (HIG, VoiceOver). Two panes side by side break that. Measured, closed and open, with two plain panes in an HStack:

Inbox, Heading | Message, Heading | Left 1 | Right 1 | Left 2 | Right 2 | Left 3 | Right 3
  • Moving the right pane 20 pt lower did not help. ArrangementView with .split read row by row too, open; closed, it showed only the primary (measured).
  • NavigationSplitView already reads the sidebar, then the detail (measured open). Leave it alone.

Make each pane a container with accessibilityElement(children: .contain). VoiceOver then visits all of one container's children before the next container (doc).

import SwiftUI

extension View {
    /// One VoiceOver container per pane: the whole pane is read before the next one.
    /// A higher priority is read first; the default is 0, leading pane first.
    func accessibilityPane(_ label: LocalizedStringKey, priority: Double = 0) -> some View {
        accessibilityElement(children: .contain)
            .accessibilityLabel(label)
            .accessibilitySortPriority(priority)
    }
}

@available(iOS 27.1, *)
struct ArticleWithComments: View {
    var body: some View {
        ArrangementView {
            ScrollView { Text("Article text") }
                .accessibilityPane("Article")
        } secondary: {
            List(1...20, id: \.self) { Text("Comment \($0)") }
                .accessibilityPane("Comments")
        }
    }
}

Measured with containers labelled "Inbox pane" and "Message pane": Inbox, Heading | Left 1 | Left 2 | Left 3 | Message pane, Message, Heading | Right 1 | .... VoiceOver spoke the second pane's label (the probe's own text; VoiceOver adds no "pane") as it entered it, but not the first pane's label at the start. With accessibilitySortPriority(1) on the right pane, VoiceOver read it first. Higher numbers go first; the default is 0 (doc).

  • Add a heading trait (.accessibilityAddTraits(.isHeader)) to each pane's title so the rotor can jump between panes.
  • The fold is not an element. Content that crosses it needs nothing. In a two-page layout, make each page a container ("Page 12").
  • Don't hide a visible pane with accessibilityHidden. Closed, a pane that is not on screen is already gone.
  • UIKit, recipes
Read the complete source ↗