Enhancing the accessibility of your SwiftUI app

At a glance

Project structure

Source bundle/
└── Sources/
    ├── App.swift
    ├── Views/
    │   ├── TripsView.swift
    │   ├── ContactAlertView.swift
    │   ├── BeachesView.swift
    │   ├── CommentMessageView.swift
    │   └── ContentView.swift
    ├── Widget/
    │   ├── WidgetBundle.swift
    │   ├── WidgetIntents.swift
    │   ├── BeachView.swift
    │   └── Widget.swift
    └── Model/
        ├── Trip.swift
        └── Comment.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 6 project/configuration file(s) and 53 source declaration(s).

Overall architecture

flowchart LR
    N1["App"]
    N2["ContentView"]
    N3["Provider"]
    N4["SwiftUI / SwiftData APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Sources/App.swift:11 — architecture anchor

@main
struct SwiftUIAccessibilitySampleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
        .modelContainer(for: [Trip.self, Beach.self, Contact.self])
    }
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Accessibility.

Ownership and state

classDiagram
    Location *-- Double : lat
    Location *-- Double : long
    Location *-- UUID : id
    Location *-- String : title

Ownership evidence

Sources/Model/Trip.swift:17 — stored dependency or nearest verified ownership anchor

    struct Location: Codable {
        var lat: Double
        var long: Double
    }

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

Sources/Model/Trip.swift:92 — representative execution boundary

protocol TripAttachment {
    var imageName: String { get }
    var label: String { get }
    var color: Color { get }
    var configuration: TripAttachmentConfiguration { get }

    @MainActor
    func performAction()
}

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

Sources/Model/Trip.swift:86 — representative type boundary

protocol TripAttachment {
    var imageName: String { get }
    // ...
}

The source explicitly defines local protocol relationships: LocationAttachment → TripAttachment, WebsiteAttachment → TripAttachment.

Access control

Reference code

Sources/Model/Beach.swift:69 — representative boundary

extension Beach {
    private static let beachGradientMix = 0.25
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: SwiftUIAccessibilitySampleApp; Player: ContactAlertPlayer; Provider: Provider; View: AttachmentOverlayView, BeachView, BeachesView, CommentMessageView, ContactAlertHeaderView.
• Protocols: TripAttachment.
• Methods: editAlerts, toggleOverlay, toggleFavorite, createReply, createNewTrip, togglePlayAction, pathForSound, audioPlayerDidFinishPlaying.
• Files: Sources/Views/TripsView.swift, Sources/Views/ContactAlertView.swift, Sources/Model/Trip.swift, Sources/Views/BeachesView.swift, Sources/Views/CommentMessageView.swift, Sources/Views/ContentView.swift.

Architecture takeaways

• App is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, SwiftData, AppIntents, WidgetKit through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation