Accessibility
Design and audit UI to WCAG 2.2 Level AA across Web, iOS, and Android, with cross-platform ARIA mapping.
- What
- Design and audit UI to WCAG 2.2 Level AA across Web, iOS, and Android, with cross-platform ARIA mapping.
- Cost
- Free
- Needs
- Use "accessibility" with an AI agent that has file tools (Read, Write), such as Claude Code, or paste it into a chat with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a practical accessibility skill for designing, implementing, and auditing interfaces to WCAG 2.2 Level AA across Web, iOS, and Android. It works through the POUR principles (Perceivable, Operable, Understandable, Robust) as a five-step implementation flow: identify the component role (semantic native elements first), define perceivable attributes (4.5:1 contrast, text alternatives, 400% reflow), implement operable controls (24x24px minimum targets, visible focus, keyboard reachability), ensure understandable logic (consistent navigation, descriptive errors, no redundant entry), and verify robust compatibility (correct Name/Role/Value, live regions). The standout asset is its cross-platform mapping table: every pattern is given in HTML/ARIA, SwiftUI (accessibilityLabel, traits, hints), and Jetpack Compose (semantics, contentDescription) side by side, with copy-paste examples for each. An anti-patterns section names the usual sins (div-buttons, color-only meaning, unfocused modals, redundant alt text) and a best-practices checklist closes the loop. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it implements the technical side of WCAG, it does not replace testing with real assistive-technology users; platform APIs evolve, spot-check generated attributes against current docs. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "accessibility" with an AI agent that has file tools (Read, Write), such as Claude Code, or paste it into a chat with your Muse. Prerequisites: no API key, no paid service. For audits, the agent needs access to the codebase. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/accessibility/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat and add: "Audit [component/page/app] for WCAG 2.2 Level AA. Platform: [Web/iOS/Android]." Or during a build: "Implement [component] accessibly: semantic roles, labels, focus management, and contrast." 3. Ask for the best-practices checklist at the end and verify each item against your code. Tip: name the platform up front to get the right mapping (ARIA vs SwiftUI vs Compose). For modals and dropdowns, explicitly ask it to check focus trapping and focus restoration. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets or API keys into it, and review anything the agent proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.