apple-ui-accessibility-workflowlisted

# Apple UI Accessibility Workflow ## Purpose Provide a docs-first workflow for Apple UI accessibility implementation and review. Keep the first version SwiftUI-first while still covering the UIKit and AppKit bridge surface when SwiftUI code wraps platform-native views or when an accessibility behavior only makes sense in those underlying frameworks. It is not the Apple-docs router, not the SwiftUI app-structure workflow, and not the Xcode execution workflow. ## When To Use - Use this skill when the user wants help making a SwiftUI view, control, list, form, chart, or composite UI more accessible. - Use this skill when the user wants help reviewing Apple UI semantics such as labels, values, hints, roles, traits, actions, headings, or grouping behavior. - Use this skill when the user wants help deciding whether the default accessibility tree is sufficient or whether a view needs explicit accessibility modifiers. - Use this skill when the user wants help shaping the accessibility tree with `accessibilityElement(children:)`, `accessibilityChildren`, `accessibilityRepresentation`, hiding rules, or synthetic accessibility content. - Use this skill when the user wants help understanding where SwiftUI accessibility stops and UIKit or AppKit accessibility responsibilities begin. - Use this skill when the user wants accessibility-specific verification expectations for VoiceOver, focus order, Dynamic Type, contrast, reduced motion, or related Apple platform settings. - Recommend `e