iOS Accessibility & Testability Agent FAQs

Question 1

How does the /audit-accessibility command work?

Accepted Answer

It captures a simulator screenshot and accessibility hierarchy dump via idb, identifies elements missing identifiers, and suggests code-level fixes based on your naming convention.

Question 2

Does this skill work with both SwiftUI and UIKit?

Accepted Answer

Yes, it provides specific implementation patterns and auditing capabilities for both SwiftUI views and UIKit components like UIButton and UITextField.

Question 3

Why is a naming convention important for identifiers?

Accepted Answer

A consistent pattern like {scope}_{type}_{name} ensures that automated tests remain stable even when layouts change, text is updated, or the app is localized into different languages.

Question 4

Can this skill help with Maestro testing?

Accepted Answer

Absolutely. It ensures all interactive elements have unique IDs, which is the most reliable way for Maestro to target elements without relying on fragile text-based or coordinate-based selectors.

Question 5

What is the difference between accessibilityIdentifier and accessibilityLabel?

Accepted Answer

accessibilityIdentifier is a non-localized string used exclusively for automated testing (idb, Maestro, XCUITest), while accessibilityLabel is a localized description read by VoiceOver for users.

iOS Accessibility & Testability Agent

Características Principales

Casos de Uso

iOS Accessibility & Testability Agent

Características Principales

Casos de Uso