Accessibility Inspector flags standard SwiftUI Dynamic Type text: minimal reproducer and macOS hierarchy warnings

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:

  1. Should the minimal standard-style sample pass the Dynamic Type audit? Is there a documented configuration or API change I am missing?
  2. What additional evidence would distinguish an Inspector issue from a genuine scaling failure?
  3. For the Mac framework-owned hierarchy findings, what is the supported application-side remedy or minimal isolation procedure?
  4. 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
Answered by DTS Engineer in 916936022

Your sample uses the documented way to support Dynamic Type in SwiftUI. WWDC24 session Get started with Dynamic Type says a good Dynamic Type experience "starts with making use of built-in text styles." It also says that in SwiftUI "you can use the font modifier" to choose one. I didn't find a documented change to make to your sample for the four Dynamic Type warnings.

Your 20-line sample made this quick to reproduce. I reproduced those warnings with your sample's view on an iPad Pro running iPadOS 27.2, using Accessibility Inspector from Xcode 27.2. On the same iPad, the XCTest audit performAccessibilityAudit(for:_:), with the .dynamicType audit type, reported no Dynamic Type issues for that view. In the same test run, it did report them for SwiftUI and UIKit text set to a fixed point size. Running that audit in a UI test on a device gives you a second check to compare against the Inspector. The same session also covers checking Dynamic Type sizes with Xcode previews and the debugger's accessibility overrides.

Both tools also report the other two findings, and both are on the button. Its label, "Example button," contains the word "button," which the audit reports as duplicating the button trait. Its white text on blue measures 3.52:1 at 17 points, which the audit reports as nearly passing.

For the Mac, Accessibility Inspector reports "Element has no description" for AppKitWindowHostingView in the unmodified SwiftUI macOS app template, in macOS 27.0.1. I didn't see the NSThemeWidgetZoomMenuRemoteView mismatch there.

Please file the Dynamic Type warnings and the Mac finding as separate bug reports using Feedback Assistant, because each is a separate work item. Your sample works for the first, and the template app works for the second. Once you've filed them, please post the FB numbers here.

Your sample uses the documented way to support Dynamic Type in SwiftUI. WWDC24 session Get started with Dynamic Type says a good Dynamic Type experience "starts with making use of built-in text styles." It also says that in SwiftUI "you can use the font modifier" to choose one. I didn't find a documented change to make to your sample for the four Dynamic Type warnings.

Your 20-line sample made this quick to reproduce. I reproduced those warnings with your sample's view on an iPad Pro running iPadOS 27.2, using Accessibility Inspector from Xcode 27.2. On the same iPad, the XCTest audit performAccessibilityAudit(for:_:), with the .dynamicType audit type, reported no Dynamic Type issues for that view. In the same test run, it did report them for SwiftUI and UIKit text set to a fixed point size. Running that audit in a UI test on a device gives you a second check to compare against the Inspector. The same session also covers checking Dynamic Type sizes with Xcode previews and the debugger's accessibility overrides.

Both tools also report the other two findings, and both are on the button. Its label, "Example button," contains the word "button," which the audit reports as duplicating the button trait. Its white text on blue measures 3.52:1 at 17 points, which the audit reports as nearly passing.

For the Mac, Accessibility Inspector reports "Element has no description" for AppKitWindowHostingView in the unmodified SwiftUI macOS app template, in macOS 27.0.1. I didn't see the NSThemeWidgetZoomMenuRemoteView mismatch there.

Please file the Dynamic Type warnings and the Mac finding as separate bug reports using Feedback Assistant, because each is a separate work item. Your sample works for the first, and the template app works for the second. Once you've filed them, please post the FB numbers here.