[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EM6ADWA9BWNFHMEWYZHFD0":3,"skill-same:01M7EM6ADWA9BWNFHMEWYZHFD0":47},{"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":6,"updatedAt":32,"install":33,"resources":46},"01M7EM6ADWA9BWNFHMEWYZHFD0","accessibility-design-checker",null,"Audit designs for accessibility with WCAG checklists covering color, type, focus, motion, and content.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-accessibility-design-checker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: accessibility-design-checker\ndescription: Audit designs for accessibility with WCAG checklists covering color, type, focus, motion, and content.\ncategory: creative-design\n---\n\n## Overview\n\nAccessible design isn't a separate discipline — it's quality design that works for everyone,\nincluding the 1 in 6 people with significant disabilities. This skill provides a practical audit\nchecklist for designs: color contrast, typography, touch targets, focus states, motion, and content\n— mapped to WCAG 2.2 AA, the standard most organizations target.\n\n## When to use\n\n- Auditing mockups or prototypes for accessibility before handoff\n\n- Checking color contrast and typography choices\n\n- Reviewing interactive states (focus, hover, error) for accessibility\n\n- Evaluating motion and animation for vestibular safety\n\n- Building accessibility into a design system\n\n## Core concepts\n\n- - **WCAG 2.2 AA is the target.** The practical standard: 4.5:1 text contrast (3:1 for large\n  text\u002FUI components), keyboard operability, meaningful focus indicators, no keyboard traps,\n  resizable text to 200%, and reduced-motion support.\n- - **Contrast is math, not opinion.** Every text\u002Fbackground combination gets checked with a\n  contrast tool. This includes text on images (test the worst-case area), placeholder text (often\n  fails), and disabled states (exempt, but don't abuse the exemption).\n- - **Don't rely on color alone.** Status, errors, and data distinctions need a second channel:\n  icons, text labels, patterns, or shapes. Approximately 1 in 12 men has color vision deficiency —\n  design for them explicitly.\n- - **Touch and target sizes.** Minimum 24×24 CSS px (WCAG 2.2 AA), with 44×44 as the recommended\n  target. Spacing between targets matters as much as size — crowded small targets cause mis-taps for\n  everyone.\n- - **Focus must be visible.** Keyboard users navigate by focus indicators. Design them deliberately\n  (don't just accept browser defaults or, worse, remove outlines): high-contrast, consistent, and\n  present on every interactive element.\n- - **Motion and vestibular safety.** Honor prefers-reduced-motion: eliminate parallax, auto-playing\n  animation, and dramatic transitions for users who opt out. Never convey essential info through\n  motion alone.\n\n## Practical workflow\n\n1. 1. **Set the scope.** Which screens\u002Fflows, which level (AA standard), and what counts as a\n   blocker vs nice-to-have. Agree with the team before auditing.\n2. 2. **Check color and contrast.** Run every text\u002Fbackground and UI\u002Fbackground combination through\n   a contrast checker. Simulate deuteranopia, protanopia, and tritanopia on key screens — especially\n   data visualizations and status indicators.\n3. 3. **Review typography.** Minimum sizes (12px absolute floor for captions, 16px+ for body\n   recommended), line height (1.5 for body), resizable to 200% without breakage or horizontal\n   scrolling, no text in images for essential content.\n4. 4. **Audit interactive elements.** Every button\u002Flink\u002Finput: visible focus state, adequate target\n   size, clear labels (not placeholder-only), error identification with text (not just red borders),\n   and logical keyboard\u002Ftab order.\n5. 5. **Evaluate motion.** List all animations: which are essential, which are decorative? Define\n   the reduced-motion fallback for each (usually: crossfade or instant). Check for auto-playing\n   content with pause controls.\n6. 6. **Check content and structure.** Heading hierarchy (no skipped levels), meaningful link text\n   (\"Download report\" not \"click here\"), alt text plan for images (decorative vs informative), form\n   labels and instructions, and reading order on complex layouts.\n7. 7. **Report with severity.** Categorize findings: blocker (fails WCAG AA \u002F blocks task\n   completion), major (significant barrier), minor (polish). Each gets: the issue, where, why it\n   matters, and a concrete fix. Include passing checks too — teams need to know what held up.\n\n## Common pitfalls\n\n- - **Accessibility as a final gate.** Auditing finished designs instead of designing accessibly\n  from the start. Retrofits cost 10x and produce worse results.\n- - **Contrast theater.** Checking the primary button but not placeholder text, captions, or\n  text-on-image. Audit every combination, not just the obvious ones.\n- - **Removing focus outlines.** `outline: none` without a replacement is the most common\n  accessibility vandalism in CSS. Design the focus state; don't delete it.\n- - **Placeholder as label.** Placeholders vanish on input, fail contrast, and aren't read\n  consistently by screen readers. Visible persistent labels, always.\n- - **Decorative motion without fallbacks.** Shipping parallax and auto-play with no reduced-motion\n  path. It's not just exclusion — for some users it's physically harmful.\n- - **Treating the checklist as the ceiling.** WCAG is the floor. Real accessibility includes\n  testing with actual assistive technology users — automated checks and audits catch maybe 40% of\n  real barriers.\n","## Overview\n\nAccessible design isn't a separate discipline — it's quality design that works for everyone,\nincluding the 1 in 6 people with significant disabilities. This skill provides a practical audit\nchecklist for designs: color contrast, typography, touch targets, focus states, motion, and content\n— mapped to WCAG 2.2 AA, the standard most organizations target.\n\n## When to use\n\n- Auditing mockups or prototypes for accessibility before handoff\n\n- Checking color contrast and typography choices\n\n- Reviewing interactive states (focus, hover, error) for accessibility\n\n- Evaluating motion and animation for vestibular safety\n\n- Building accessibility into a design system\n\n## Core concepts\n\n- - **WCAG 2.2 AA is the target.** The practical standard: 4.5:1 text contrast (3:1 for large\n  text\u002FUI components), keyboard operability, meaningful focus indicators, no keyboard traps,\n  resizable text to 200%, and reduced-motion support.\n- - **Contrast is math, not opinion.** Every text\u002Fbackground combination gets checked with a\n  contrast tool. This includes text on images (test the worst-case area), placeholder text (often\n  fails), and disabled states (exempt, but don't abuse the exemption).\n- - **Don't rely on color alone.** Status, errors, and data distinctions need a second channel:\n  icons, text labels, patterns, or shapes. Approximately 1 in 12 men has color vision deficiency —\n  design for them explicitly.\n- - **Touch and target sizes.** Minimum 24×24 CSS px (WCAG 2.2 AA), with 44×44 as the recommended\n  target. Spacing between targets matters as much as size — crowded small targets cause mis-taps for\n  everyone.\n- - **Focus must be visible.** Keyboard users navigate by focus indicators. Design them deliberately\n  (don't just accept browser defaults or, worse, remove outlines): high-contrast, consistent, and\n  present on every interactive element.\n- - **Motion and vestibular safety.** Honor prefers-reduced-motion: eliminate parallax, auto-playing\n  animation, and dramatic transitions for users who opt out. Never convey essential info through\n  motion alone.\n\n## Practical workflow\n\n1. 1. **Set the scope.** Which screens\u002Fflows, which level (AA standard), and what counts as a\n   blocker vs nice-to-have. Agree with the team before auditing.\n2. 2. **Check color and contrast.** Run every text\u002Fbackground and UI\u002Fbackground combination through\n   a contrast checker. Simulate deuteranopia, protanopia, and tritanopia on key screens — especially\n   data visualizations and status indicators.\n3. 3. **Review typography.** Minimum sizes (12px absolute floor for captions, 16px+ for body\n   recommended), line height (1.5 for body), resizable to 200% without breakage or horizontal\n   scrolling, no text in images for essential content.\n4. 4. **Audit interactive elements.** Every button\u002Flink\u002Finput: visible focus state, adequate target\n   size, clear labels (not placeholder-only), error identification with text (not just red borders),\n   and logical keyboard\u002Ftab order.\n5. 5. **Evaluate motion.** List all animations: which are essential, which are decorative? Define\n   the reduced-motion fallback for each (usually: crossfade or instant). Check for auto-playing\n   content with pause controls.\n6. 6. **Check content and structure.** Heading hierarchy (no skipped levels), meaningful link text\n   (\"Download report\" not \"click here\"), alt text plan for images (decorative vs informative), form\n   labels and instructions, and reading order on complex layouts.\n7. 7. **Report with severity.** Categorize findings: blocker (fails WCAG AA \u002F blocks task\n   completion), major (significant barrier), minor (polish). Each gets: the issue, where, why it\n   matters, and a concrete fix. Include passing checks too — teams need to know what held up.\n\n## Common pitfalls\n\n- - **Accessibility as a final gate.** Auditing finished designs instead of designing accessibly\n  from the start. Retrofits cost 10x and produce worse results.\n- - **Contrast theater.** Checking the primary button but not placeholder text, captions, or\n  text-on-image. Audit every combination, not just the obvious ones.\n- - **Removing focus outlines.** `outline: none` without a replacement is the most common\n  accessibility vandalism in CSS. Design the focus state; don't delete it.\n- - **Placeholder as label.** Placeholders vanish on input, fail contrast, and aren't read\n  consistently by screen readers. Visible persistent labels, always.\n- - **Decorative motion without fallbacks.** Shipping parallax and auto-play with no reduced-motion\n  path. It's not just exclusion — for some users it's physically harmful.\n- - **Treating the checklist as the ceiling.** WCAG is the floor. Real accessibility includes\n  testing with actual assistive technology users — automated checks and audits catch maybe 40% of\n  real barriers.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-accessibility-design-checker",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill accessibility-design-checker",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill accessibility-design-checker",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill accessibility-design-checker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-accessibility-design-checker\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]