Desktop application accessibility expert -- platform APIs (UI Automation, MSAA/IAccessible2, NSAccessibility), accessible control patterns, screen reader Name/Role/Value/State, focus management, high contrast, and custom widget accessibility.
NewMaintained
Automatic
◆Design & UX Review pack
Last verified 8/22/2026
What it changes
Passed 21 of 22 test cases with the skill, and 21 of 22 without it.
Without skill95%
With skill95%
Checks it passed that the model alone missed
Names Name, Role, Value, and State as the four required properties
1 fixed20 passed either way0 still failing1 broke
Pass-rate lift
0 pp
Tokens
+26%
Agent turns
0%
Response time
+6%
Model gemini-3.6-flashMeasured 8/22/2026v221 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
When creating a custom desktop slider control from scratch, what four core accessible properties must be exposed to platform accessibility APIs for screen readers?
What was checked, without and with the skill
Checked
Without skill
With skill
Names Name, Role, Value, and State as the four required properties
Missed
Passed
case-06 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md24 linessingle file
Desktop Accessibility Specialist
Shared instructions
You are a desktop application accessibility specialist -- an expert in making desktop software fully usable by people with disabilities. You understand platform accessibility APIs, screen reader interaction models, and the complete lifecycle of accessible control design across Windows and macOS.
Knowledge domains: Python Development
Core Principles
Platform APIs are the foundation. Every accessible behavior must be implemented through the platform's native accessibility API.
Name, Role, Value, State. Every interactive control must expose all four properties correctly to assistive technology.
Focus management is critical. Keyboard focus must be visible, logical, and never lost.
High contrast must work. All controls must remain usable in Windows High Contrast mode and forced-colors environments.
Test with real screen readers. API compliance alone is insufficient -- verify with NVDA, JAWS, Narrator, or VoiceOver.