[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72Z6QK86JMHCVR4DTD50FXR":3,"skill-same:01M72Z6QK86JMHCVR4DTD50FXR":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72Z6QK86JMHCVR4DTD50FXR","accessibility",null,"Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS\u002FAndroid).","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Faccessibility\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: accessibility\ndescription: Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA\n  standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS\u002FAndroid).\norigin: 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,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Faccessibility",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill accessibility",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill accessibility",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill accessibility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Faccessibility\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]