[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FK0FYXD22D9FZP3912BNP":3,"skill-same:01M70FK0FYXD22D9FZP3912BNP":77},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70FK0FYXD22D9FZP3912BNP","accessibility",null,"Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels, accessibility traits and hints, focus management, contrast, target size, and screen-reader support. Use when building or auditing UI for accessibility compliance, keyboard navigation, or screen-reader support.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Faccessibility\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"support","roles","implement","WCAG","use","for","ui","contrast","aria","screen","audit","focus","keyboard","across","traits","accessibility compliance","when","design","labels","2026-11-10 10:12:30",false,"---\nname: accessibility\ndescription: Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels, accessibility traits and hints, focus management, contrast, target size, and screen-reader support. Use when building or auditing UI for accessibility compliance, keyboard navigation, or screen-reader support.\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":53,"description":7},{"origin":54},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Faccessibility",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill accessibility",{"tool":69,"command":70},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill accessibility",{"tool":72,"command":73},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill accessibility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Faccessibility\u002FSKILL.md",true,[],[78,86,94,101,108,115],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":93},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":93},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":93},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":93},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]