I would appreciate guidance on separating an application accessibility defect from an Accessibility Inspector/framework issue.
Environment: Xcode 27.2 (25400.63.5), iOS/iPadOS 27.2 simulators and native macOS 26.7.2.
A separate minimal project uses only standard SwiftUI controls and system text styles—no custom fonts, fixed text sizes, environment overrides, third-party libraries or application content:
import SwiftUI
@main struct DynamicTypeProbeApp: App {
var body: some Scene {
WindowGroup {
NavigationStack {
ScrollView {
VStack(alignment: .leading, spacing: 24) {
Text("Dynamic Type diagnostic").font(.largeTitle)
Text("A standard system body label should grow with the device text setting.").font(.body)
Text("A system headline for comparison").font(.headline)
Button("Example button") { }.buttonStyle(.borderedProminent)
}.padding()
}.navigationTitle("Text diagnostic")
}
}
}
}Steps: run this sample, select its simulator/process in Accessibility Inspector, run all audit categories, then compare default and maximum text-size settings. The exported sample audit reports four “Dynamic Type font sizes are unsupported” findings, although the standard text visibly enlarges and reflows. The sample also reports a near-threshold contrast issue and a duplicate-traits finding; I am not assuming all findings have the same cause.
I saw the Apple engineer's reply in https://developer.apple.com/forums/thread/823968 suggesting that similar visually scaling text could indicate an Inspector bug. That thread uses UIKit/custom-font scaling, so I do not assume it establishes the cause of this standard-SwiftUI case.
Separately, a native Mac screen reports a missing description for AppKitWindowHostingView and a parent/child mismatch for NSThemeWidgetZoomMenuRemoteView. A temporary root-container accessibility label did not remove those findings and was reverted. I have not modified private framework classes, disabled audit categories or hidden functional controls to make an audit pass.
Questions:
Should the minimal standard-style sample pass the Dynamic Type audit? Is there a documented configuration or API change I am missing?
What additional evidence would distinguish an Inspector issue from a genuine scaling failure?
For the Mac framework-owned hierarchy findings, what is the supported application-side remedy or minimal isolation procedure?
Which combination of Inspector results and manual VoiceOver/keyboard/large-text checks would you recommend for assessing these specific findings?
I am continuing manual testing and am not treating visible scaling as full accessibility clearance. Please let me know what additional non-app-specific diagnostic information would help.
Thank you,
Luke
1
0
461