appkit-accessibility-auditor

Audits AppKit interfaces for VoiceOver, keyboard navigation, and semantic accessibility issues.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill appkit-accessibility-auditor-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: appkit-accessibility-auditor
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/appkit-accessibility-auditor
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill appkit-accessibility-auditor-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? macOS AppKit apps often ship with accessibility gaps—missing VoiceOver labels, broken keyboard focus order, or custom controls that assistive technologies cannot operate—and developers lack a structured way to find and fix them. ## Core Features & Use Cases - Prioritized Accessibility Audit: Reviews AppKit code (NSView, NSViewController, NSTableView, custom controls) and returns P0/P1/P2 findings with patch-ready fixes. - Comprehensive Checklist Coverage: Covers VoiceOver roles and labels, keyboard navigation and focus loops, grouping and reading order, tables and outline views, Dynamic Type, announcements, Voice Control, and contrast. - Use Case: Paste a custom NSView acting as a toggle button and receive a diff adding the correct accessibility role, value, keyboard handling, and an accessibility press action, plus manual VoiceOver verification steps. ## Quick Start Ask the agent to review your AppKit view controller with the AppKit Accessibility Auditor, focusing on VoiceOver labels and keyboard navigation, and return prioritized findings with a patch-ready diff.

Frequently Asked Questions about appkit-accessibility-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit an AppKit app for VoiceOver accessibility?▼

Provide your NSViewController, NSView, or window code and request an audit. The skill checks roles, labels, help text, grouping, and reading order, then returns prioritized P0/P1/P2 findings with patch-ready fixes and manual VoiceOver test steps.

How to make a custom NSView accessible like a button?▼

A custom NSView acting as a control must expose the correct accessibilityRole and accessibilityValue, be keyboard-operable via Space or Enter, and provide an accessibility press action such as accessibilityPerformPress. The audit identifies exactly which of these are missing.

Does this work with NSTableView and NSOutlineView accessibility?▼

Yes. The audit covers table and outline views, checking that rows are understandable with VoiceOver, selection state is discoverable, column headers are accessible, and custom cell views expose meaningful labels and values.

Will the suggested fixes change my app's layout or behavior?▼

No. The skill follows a minimal-change guardrail: fixes are localized to accessibility semantics and discoverability, avoiding layout changes, refactors, or user-facing copy edits unless accessibility strictly requires them.

What are the limitations of an automated AppKit accessibility audit?▼

The audit provides code-level findings and patch-ready fixes, but final validation requires manual testing with VoiceOver, keyboard-only navigation, and Voice Control or Switch Control. A checklist.md artifact guides that manual verification.