[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DASSP0CG2NAWFS6TE2CAYE":3,"skill-same:01M7DASSP0CG2NAWFS6TE2CAYE":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DASSP0CG2NAWFS6TE2CAYE","accessibility",null,"Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support. standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS\u002FAndroid).","MoradDev\u002Fskills-unified","MoradDev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F72839584?v=4","01M7DASN3HYHFBYW4ZNMPTHQ63","01M7DASN4N6P4P9WMEFRE2V0TF",2,"MIT","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Faccessibility\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: accessibility\ndescription: Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.\n  standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS\u002FAndroid).\nmetadata:\n  origin: ECC\n---\n\n# Accessibility (WCAG 2.2)\n\nThis skill ensures that digital interfaces are Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those using screen readers, switch controls, or keyboard navigation. It focuses on the technical implementation of WCAG 2.2 success criteria.\n\n## When to Use\n\n- Defining UI component specifications for Web, iOS, or Android.\n- Auditing existing code for accessibility barriers or compliance gaps.\n- Implementing new WCAG 2.2 standards like Target Size (Minimum) and Focus Appearance.\n- Mapping high-level design requirements to technical attributes (ARIA roles, traits, hints).\n\n## Core Concepts\n\n- **POUR Principles**: The foundation of WCAG (Perceivable, Operable, Understandable, Robust).\n- **Semantic Mapping**: Using native elements over generic containers to provide built-in accessibility.\n- **Accessibility Tree**: The representation of the UI that assistive technologies actually \"read.\"\n- **Focus Management**: Controlling the order and visibility of the keyboard\u002Fscreen reader cursor.\n- **Labeling & Hints**: Providing context through `aria-label`, `accessibilityLabel`, and `contentDescription`.\n\n## How It Works\n\n### Step 1: Identify the Component Role\n\nDetermine the functional purpose (e.g., Is this a button, a link, or a tab?). Use the most semantic native element available before resorting to custom roles.\n\n### Step 2: Define Perceivable Attributes\n\n- Ensure text contrast meets **4.5:1** (normal) or **3:1** (large\u002FUI).\n- Add text alternatives for non-text content (images, icons).\n- Implement responsive reflow (up to 400% zoom without loss of function).\n\n### Step 3: Implement Operable Controls\n\n- Ensure a minimum **24x24 CSS pixel** target size (WCAG 2.2 SC 2.5.8).\n- Verify all interactive elements are reachable via keyboard and have a visible focus indicator (SC 2.4.11).\n- Provide single-pointer alternatives for dragging movements.\n\n### Step 4: Ensure Understandable Logic\n\n- Use consistent navigation patterns.\n- Provide descriptive error messages and suggestions for correction (SC 3.3.3).\n- Implement \"Redundant Entry\" (SC 3.3.7) to prevent asking for the same data twice.\n\n### Step 5: Verify Robust Compatibility\n\n- Use correct `Name, Role, Value` patterns.\n- Implement `aria-live` or live regions for dynamic status updates.\n\n## Accessibility Architecture Diagram\n\n```mermaid\nflowchart TD\n  UI[\"UI Component\"] --> Platform{Platform?}\n  Platform -->|Web| ARIA[\"WAI-ARIA + HTML5\"]\n  Platform -->|iOS| SwiftUI[\"Accessibility Traits + Labels\"]\n  Platform -->|Android| Compose[\"Semantics + ContentDesc\"]\n\n  ARIA --> AT[\"Assistive Technology (Screen Readers, Switches)\"]\n  SwiftUI --> AT\n  Compose --> AT\n```\n\n## Cross-Platform Mapping\n\n| Feature            | Web (HTML\u002FARIA)          | iOS (SwiftUI)                        | Android (Compose)                                           |\n| :----------------- | :----------------------- | :----------------------------------- | :---------------------------------------------------------- |\n| **Primary Label**  | `aria-label` \u002F `\u003Clabel>` | `.accessibilityLabel()`              | `contentDescription`                                        |\n| **Secondary Hint** | `aria-describedby`       | `.accessibilityHint()`               | `Modifier.semantics { stateDescription = ... }`             |\n| **Action Role**    | `role=\"button\"`          | `.accessibilityAddTraits(.isButton)` | `Modifier.semantics { role = Role.Button }`                 |\n| **Live Updates**   | `aria-live=\"polite\"`     | `.accessibilityLiveRegion(.polite)`  | `Modifier.semantics { liveRegion = LiveRegionMode.Polite }` |\n\n## Examples\n\n### Web: Accessible Search\n\n```html\n\u003Cform role=\"search\">\n  \u003Clabel for=\"search-input\" class=\"sr-only\">Search products\u003C\u002Flabel>\n  \u003Cinput type=\"search\" id=\"search-input\" placeholder=\"Search...\" \u002F>\n  \u003Cbutton type=\"submit\" aria-label=\"Submit Search\">\n    \u003Csvg aria-hidden=\"true\">...\u003C\u002Fsvg>\n  \u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\n### iOS: Accessible Action Button\n\n```swift\nButton(action: deleteItem) {\n    Image(systemName: \"trash\")\n}\n.accessibilityLabel(\"Delete item\")\n.accessibilityHint(\"Permanently removes this item from your list\")\n.accessibilityAddTraits(.isButton)\n```\n\n### Android: Accessible Toggle\n\n```kotlin\nSwitch(\n    checked = isEnabled,\n    onCheckedChange = { onToggle() },\n    modifier = Modifier.semantics {\n        contentDescription = \"Enable notifications\"\n    }\n)\n```\n\n## Anti-Patterns to Avoid\n\n- **Div-Buttons**: Using a `\u003Cdiv>` or `\u003Cspan>` for a click event without adding a role and keyboard support.\n- **Color-Only Meaning**: Indicating an error or status _only_ with a color change (e.g., turning a border red).\n- **Uncontained Modal Focus**: Modals that don't trap focus, allowing keyboard users to navigate background content while the modal is open. Focus must be contained _and_ escapable via the `Escape` key or an explicit close button (WCAG SC 2.1.2).\n- **Redundant Alt Text**: Using \"Image of...\" or \"Picture of...\" in alt text (screen readers already announce the role \"Image\").\n\n## Best Practices Checklist\n\n- [ ] Interactive elements meet the **24x24px** (Web) or **44x44pt** (Native) target size.\n- [ ] Focus indicators are clearly visible and high-contrast.\n- [ ] Modals **contain focus** while open, and release it cleanly on close (`Escape` key or close button).\n- [ ] Dropdowns and menus restore focus to the trigger element on close.\n- [ ] Forms provide text-based error suggestions.\n- [ ] All icon-only buttons have a descriptive text label.\n- [ ] Content reflows properly when text is scaled.\n\n## References\n\n- [WCAG 2.2 Guidelines](https:\u002F\u002Fwww.w3.org\u002FTR\u002FWCAG22\u002F)\n- [WAI-ARIA Authoring Practices](https:\u002F\u002Fwww.w3.org\u002FTR\u002Fwai-aria-practices\u002F)\n- [iOS Accessibility Programming Guide](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Faccessibility)\n- [iOS Human Interface Guidelines - Accessibility](https:\u002F\u002Fdeveloper.apple.com\u002Fdesign\u002Fhuman-interface-guidelines\u002Faccessibility)\n- [Android Accessibility Developer Guide](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Ftopics\u002Fui\u002Faccessibility)\n\n## Related Skills\n\n- `frontend-patterns`\n- `design-system`\n- `liquid-glass-design`\n- `swiftui-patterns`\n","# Accessibility (WCAG 2.2)\n\nThis skill ensures that digital interfaces are Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those using screen readers, switch controls, or keyboard navigation. It focuses on the technical implementation of WCAG 2.2 success criteria.\n\n## When to Use\n\n- Defining UI component specifications for Web, iOS, or Android.\n- Auditing existing code for accessibility barriers or compliance gaps.\n- Implementing new WCAG 2.2 standards like Target Size (Minimum) and Focus Appearance.\n- Mapping high-level design requirements to technical attributes (ARIA roles, traits, hints).\n\n## Core Concepts\n\n- **POUR Principles**: The foundation of WCAG (Perceivable, Operable, Understandable, Robust).\n- **Semantic Mapping**: Using native elements over generic containers to provide built-in accessibility.\n- **Accessibility Tree**: The representation of the UI that assistive technologies actually \"read.\"\n- **Focus Management**: Controlling the order and visibility of the keyboard\u002Fscreen reader cursor.\n- **Labeling & Hints**: Providing context through `aria-label`, `accessibilityLabel`, and `contentDescription`.\n\n## How It Works\n\n### Step 1: Identify the Component Role\n\nDetermine the functional purpose (e.g., Is this a button, a link, or a tab?). Use the most semantic native element available before resorting to custom roles.\n\n### Step 2: Define Perceivable Attributes\n\n- Ensure text contrast meets **4.5:1** (normal) or **3:1** (large\u002FUI).\n- Add text alternatives for non-text content (images, icons).\n- Implement responsive reflow (up to 400% zoom without loss of function).\n\n### Step 3: Implement Operable Controls\n\n- Ensure a minimum **24x24 CSS pixel** target size (WCAG 2.2 SC 2.5.8).\n- Verify all interactive elements are reachable via keyboard and have a visible focus indicator (SC 2.4.11).\n- Provide single-pointer alternatives for dragging movements.\n\n### Step 4: Ensure Understandable Logic\n\n- Use consistent navigation patterns.\n- Provide descriptive error messages and suggestions for correction (SC 3.3.3).\n- Implement \"Redundant Entry\" (SC 3.3.7) to prevent asking for the same data twice.\n\n### Step 5: Verify Robust Compatibility\n\n- Use correct `Name, Role, Value` patterns.\n- Implement `aria-live` or live regions for dynamic status updates.\n\n## Accessibility Architecture Diagram\n\n```mermaid\nflowchart TD\n  UI[\"UI Component\"] --> Platform{Platform?}\n  Platform -->|Web| ARIA[\"WAI-ARIA + HTML5\"]\n  Platform -->|iOS| SwiftUI[\"Accessibility Traits + Labels\"]\n  Platform -->|Android| Compose[\"Semantics + ContentDesc\"]\n\n  ARIA --> AT[\"Assistive Technology (Screen Readers, Switches)\"]\n  SwiftUI --> AT\n  Compose --> AT\n```\n\n## Cross-Platform Mapping\n\n| Feature            | Web (HTML\u002FARIA)          | iOS (SwiftUI)                        | Android (Compose)                                           |\n| :----------------- | :----------------------- | :----------------------------------- | :---------------------------------------------------------- |\n| **Primary Label**  | `aria-label` \u002F `\u003Clabel>` | `.accessibilityLabel()`              | `contentDescription`                                        |\n| **Secondary Hint** | `aria-describedby`       | `.accessibilityHint()`               | `Modifier.semantics { stateDescription = ... }`             |\n| **Action Role**    | `role=\"button\"`          | `.accessibilityAddTraits(.isButton)` | `Modifier.semantics { role = Role.Button }`                 |\n| **Live Updates**   | `aria-live=\"polite\"`     | `.accessibilityLiveRegion(.polite)`  | `Modifier.semantics { liveRegion = LiveRegionMode.Polite }` |\n\n## Examples\n\n### Web: Accessible Search\n\n```html\n\u003Cform role=\"search\">\n  \u003Clabel for=\"search-input\" class=\"sr-only\">Search products\u003C\u002Flabel>\n  \u003Cinput type=\"search\" id=\"search-input\" placeholder=\"Search...\" \u002F>\n  \u003Cbutton type=\"submit\" aria-label=\"Submit Search\">\n    \u003Csvg aria-hidden=\"true\">...\u003C\u002Fsvg>\n  \u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\n### iOS: Accessible Action Button\n\n```swift\nButton(action: deleteItem) {\n    Image(systemName: \"trash\")\n}\n.accessibilityLabel(\"Delete item\")\n.accessibilityHint(\"Permanently removes this item from your list\")\n.accessibilityAddTraits(.isButton)\n```\n\n### Android: Accessible Toggle\n\n```kotlin\nSwitch(\n    checked = isEnabled,\n    onCheckedChange = { onToggle() },\n    modifier = Modifier.semantics {\n        contentDescription = \"Enable notifications\"\n    }\n)\n```\n\n## Anti-Patterns to Avoid\n\n- **Div-Buttons**: Using a `\u003Cdiv>` or `\u003Cspan>` for a click event without adding a role and keyboard support.\n- **Color-Only Meaning**: Indicating an error or status _only_ with a color change (e.g., turning a border red).\n- **Uncontained Modal Focus**: Modals that don't trap focus, allowing keyboard users to navigate background content while the modal is open. Focus must be contained _and_ escapable via the `Escape` key or an explicit close button (WCAG SC 2.1.2).\n- **Redundant Alt Text**: Using \"Image of...\" or \"Picture of...\" in alt text (screen readers already announce the role \"Image\").\n\n## Best Practices Checklist\n\n- [ ] Interactive elements meet the **24x24px** (Web) or **44x44pt** (Native) target size.\n- [ ] Focus indicators are clearly visible and high-contrast.\n- [ ] Modals **contain focus** while open, and release it cleanly on close (`Escape` key or close button).\n- [ ] Dropdowns and menus restore focus to the trigger element on close.\n- [ ] Forms provide text-based error suggestions.\n- [ ] All icon-only buttons have a descriptive text label.\n- [ ] Content reflows properly when text is scaled.\n\n## References\n\n- [WCAG 2.2 Guidelines](https:\u002F\u002Fwww.w3.org\u002FTR\u002FWCAG22\u002F)\n- [WAI-ARIA Authoring Practices](https:\u002F\u002Fwww.w3.org\u002FTR\u002Fwai-aria-practices\u002F)\n- [iOS Accessibility Programming Guide](https:\u002F\u002Fdeveloper.apple.com\u002Fdocumentation\u002Faccessibility)\n- [iOS Human Interface Guidelines - Accessibility](https:\u002F\u002Fdeveloper.apple.com\u002Fdesign\u002Fhuman-interface-guidelines\u002Faccessibility)\n- [Android Accessibility Developer Guide](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Ftopics\u002Fui\u002Faccessibility)\n\n## Related Skills\n\n- `frontend-patterns`\n- `design-system`\n- `liquid-glass-design`\n- `swiftui-patterns`\n",{"name":5,"metadata":23,"description":7},{"origin":24},"ECC","main","7542b2fc80051758dfb288b450cb344d3bdfca35","curation\u002Fskills\u002Faccessibility",0,"https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified","https:\u002F\u002Fgithub.com\u002FMoradDev","2026-11-07 21:53:24",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MoradDev\u002Fskills-unified --skill accessibility",{"tool":38,"command":39},"bunx","bunx skills add MoradDev\u002Fskills-unified --skill accessibility",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MoradDev\u002Fskills-unified --skill accessibility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Faccessibility\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7DB9J6N2PSGECQ6FTWW7B2H","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7DB9CCWT4YW7B791QN43E3Q","vue-patterns","Vue.js 3 Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns. Activates for Vue, Nuxt, Vite, or Pinia projects. Use when building or reviewing Vue 3, Nuxt, or Pinia code — Composition API, reactivity, or router navigation.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fvue-patterns\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7DB976FM2CAWT807EA36MXM","vite-patterns","Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fvite-patterns\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7DB93JZRAWFB5QHH0C8DZ8N","using-agent-skills","Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7DB8YYW1PEDS7H2AA86TE2E","ui-demo","Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fui-demo\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7DB8RPQPW2R6GKJW618VDST","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices. Use when building or reviewing SwiftUI views, @Observable state, navigation, or render performance.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[]]