apple-text-accessibility

To make a custom UITextView accessible with VoiceOver in SwiftUI, enable VoiceOver support in UITextView and implement appropriate accessibility traits, ensuring isAccessibilityElement, accessibilityLabel, and accessibilityValue are properly exposed across the SwiftUI wrapper.

For a custom text editor in UIKit, you need to implement isAccessibilityElement, accessibilityTraits, accessibilityLabel, accessibilityValue, and UIAccessibilityReadingContent to ensure VoiceOver properly announces and reads the text content.

Wrapping UITextView in SwiftUI can break VoiceOver and Dynamic Type if accessibility is not bridged correctly. You must apply proper accessibility traits, hints, and isAccessibilityElement configuration to maintain usability.

Implementing UIAccessibilityReadingContent in a custom text editor requires providing line-by-line text content and frame information so VoiceOver can read specific sections of the editor accurately across iOS versions.

VoiceOver may not read custom text editor text if the view lacks proper accessibilityValue, isAccessibilityElement configuration, or UIAccessibilityReadingContent adoption, preventing the screen reader from accessing the text content.

The best way to support Dynamic Type in custom Apple text editors is applying accessibility hints, custom view traits, and standard text scaling properties, ensuring compatible scaling across both UIKit and SwiftUI frameworks.