[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CRVGRAJRBEWKPWJM8EM536":3,"skill-same:01M7CRVGRAJRBEWKPWJM8EM536":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CRVGRAJRBEWKPWJM8EM536","accessibility-basics",null,"Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs\u002Fmenus, visible focus, and never color as the only signal","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Ffrontend-developer\u002Fskills\u002Faccessibility-basics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: accessibility-basics\ncategory: frontend\ndescription: Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs\u002Fmenus, visible focus, and never color as the only signal\nsource: vercel-labs\u002Fweb-interface-guidelines (MIT), adapted\n---\n# Accessibility Basics\n\n## Overview\n\nAccessibility is not a pass at the end — it's built into each component. The recurring defects are `div` with `onClick` instead of a button, icon buttons with no label, and custom menus\u002Fdialogs that trap keyboard users.\n\n**Core principle:** Semantic HTML and the accessible primitives do most of the work — reach for them first.\n\n## Rules\n\n- **Semantic HTML first:** `button` for actions, `a` for navigation, headings in order with exactly one `\u003Ch1>` per page. A `div` with `onClick` is a defect (no keyboard, no role).\n- **Every control is labeled:** every form control has an associated `\u003Clabel>`; every icon-only button has an `aria-label`; decorative icons are `aria-hidden`.\n- **Dialogs and menus are keyboard-navigable:** focus moves in on open, is trapped while open, and returns to the trigger on close — the Radix primitives do this, so use them instead of hand-rolling.\n- **Visible focus everywhere:** never remove an outline without a replacement `:focus-visible` style; sticky\u002Ffixed elements never cover the focus ring.\n- **Color is never the only signal:** pair status with an icon or text; keep contrast ≥4.5:1 for body text and ≥3:1 for large text, in both themes.\n- **Touch and zoom:** hit targets ≥44px on phone \u002F ≥24px on desktop (pad a smaller visual out to that size); a checkbox or radio shares one hit target with its label (`\u003Clabel>` wrapping both, or `htmlFor`) so the combined row reaches 44px with no dead zone between box and text; `\u003Cinput>` font size ≥16px on phones to stop iOS auto-zoom; never disable browser zoom (`user-scalable=no`, `maximum-scale=1`).\n- **Motion:** respect `prefers-reduced-motion` via `motion-reduce:` on any animation you add; smooth anchor scrolling only as `motion-safe:scroll-smooth` on `\u003Chtml>`, never unconditional `scroll-behavior: smooth`.\n- **Structure for screen readers:** page landmarks (`header`, `nav`, `main`, `footer`), a skip-to-content link before the nav, `scroll-margin-top` on anchor targets sitting under a sticky header, and `lang` on `\u003Chtml>` matching the active locale.\n- **Live regions:** toasts and inline validation messages use `aria-live=\"polite\"` so assistive tech announces them without stealing focus.\n- **Forms:** on submit, move focus to the first invalid field; its error is linked with `aria-describedby` and the field carries `aria-invalid`.\n\n## Worked Example\n\n```tsx\n\u002F\u002F ❌ not keyboard-accessible, no role, no label\n\u003Cdiv className=\"icon-btn\" onClick={onDelete}>\u003CTrashIcon \u002F>\u003C\u002Fdiv>\n\n\u002F\u002F ✅ real button, labeled, gets focus + Enter\u002FSpace for free\n\u003Cbutton type=\"button\" aria-label=\"Delete task\" onClick={onDelete}>\n  \u003CTrashIcon aria-hidden \u002F>\n\u003C\u002Fbutton>\n```\n\nThe `button` is focusable and keyboard-activatable with no extra code; the `aria-label` gives screen readers the action; `aria-hidden` on the icon stops it being announced twice.\n\n## Proving keyboard behaviour\n\nThere is no keyboard-press browser tool at runtime (`browser_click`\u002F`browser_fill` only) — prove tab order, `Escape`, and focus-return in a co-located RTL component test instead of a manual browser pass:\n\n```tsx\ntest(\"closes on Escape and returns focus to the trigger\", async () => {\n  const user = userEvent.setup();\n  render(\u003CMenuExample \u002F>);\n  await user.click(screen.getByRole(\"button\", { name: \"Actions\" }));\n  await user.keyboard(\"{Escape}\");\n  expect(screen.getByRole(\"button\", { name: \"Actions\" })).toHaveFocus();\n});\n```\n\n`user.tab()` walks focus order, `user.keyboard('{Escape}')` fires the key, `toHaveFocus()` asserts the result — this is how keyboard behaviour is verified since the browser tools have no key-press action.\n\n## Common Mistakes\n\n- `div`\u002F`span` with `onClick` for an action.\n- Icon-only button with no `aria-label`.\n- A hand-rolled dropdown\u002Fdialog that traps keyboard users → use the Radix primitive.\n- Removing focus outlines with no replacement.\n- Status shown by color alone.\n- A touch target under 44px on phone, or `\u003Cinput>` text under 16px causing iOS zoom.\n- Shipping a keyboard interaction with no test proving it.\n\n## Red Flags\n\n- A clickable element that isn't a `button`\u002F`a`.\n- An interactive widget you built from raw `div`s instead of a primitive.\n- `outline: none` with nothing in its place.\n- `user-scalable=no` or `maximum-scale=1` in a viewport meta tag.\n- A component test suite with no `user.tab()`\u002F`user.keyboard()` coverage for a new interactive widget.\n","# Accessibility Basics\n\n## Overview\n\nAccessibility is not a pass at the end — it's built into each component. The recurring defects are `div` with `onClick` instead of a button, icon buttons with no label, and custom menus\u002Fdialogs that trap keyboard users.\n\n**Core principle:** Semantic HTML and the accessible primitives do most of the work — reach for them first.\n\n## Rules\n\n- **Semantic HTML first:** `button` for actions, `a` for navigation, headings in order with exactly one `\u003Ch1>` per page. A `div` with `onClick` is a defect (no keyboard, no role).\n- **Every control is labeled:** every form control has an associated `\u003Clabel>`; every icon-only button has an `aria-label`; decorative icons are `aria-hidden`.\n- **Dialogs and menus are keyboard-navigable:** focus moves in on open, is trapped while open, and returns to the trigger on close — the Radix primitives do this, so use them instead of hand-rolling.\n- **Visible focus everywhere:** never remove an outline without a replacement `:focus-visible` style; sticky\u002Ffixed elements never cover the focus ring.\n- **Color is never the only signal:** pair status with an icon or text; keep contrast ≥4.5:1 for body text and ≥3:1 for large text, in both themes.\n- **Touch and zoom:** hit targets ≥44px on phone \u002F ≥24px on desktop (pad a smaller visual out to that size); a checkbox or radio shares one hit target with its label (`\u003Clabel>` wrapping both, or `htmlFor`) so the combined row reaches 44px with no dead zone between box and text; `\u003Cinput>` font size ≥16px on phones to stop iOS auto-zoom; never disable browser zoom (`user-scalable=no`, `maximum-scale=1`).\n- **Motion:** respect `prefers-reduced-motion` via `motion-reduce:` on any animation you add; smooth anchor scrolling only as `motion-safe:scroll-smooth` on `\u003Chtml>`, never unconditional `scroll-behavior: smooth`.\n- **Structure for screen readers:** page landmarks (`header`, `nav`, `main`, `footer`), a skip-to-content link before the nav, `scroll-margin-top` on anchor targets sitting under a sticky header, and `lang` on `\u003Chtml>` matching the active locale.\n- **Live regions:** toasts and inline validation messages use `aria-live=\"polite\"` so assistive tech announces them without stealing focus.\n- **Forms:** on submit, move focus to the first invalid field; its error is linked with `aria-describedby` and the field carries `aria-invalid`.\n\n## Worked Example\n\n```tsx\n\u002F\u002F ❌ not keyboard-accessible, no role, no label\n\u003Cdiv className=\"icon-btn\" onClick={onDelete}>\u003CTrashIcon \u002F>\u003C\u002Fdiv>\n\n\u002F\u002F ✅ real button, labeled, gets focus + Enter\u002FSpace for free\n\u003Cbutton type=\"button\" aria-label=\"Delete task\" onClick={onDelete}>\n  \u003CTrashIcon aria-hidden \u002F>\n\u003C\u002Fbutton>\n```\n\nThe `button` is focusable and keyboard-activatable with no extra code; the `aria-label` gives screen readers the action; `aria-hidden` on the icon stops it being announced twice.\n\n## Proving keyboard behaviour\n\nThere is no keyboard-press browser tool at runtime (`browser_click`\u002F`browser_fill` only) — prove tab order, `Escape`, and focus-return in a co-located RTL component test instead of a manual browser pass:\n\n```tsx\ntest(\"closes on Escape and returns focus to the trigger\", async () => {\n  const user = userEvent.setup();\n  render(\u003CMenuExample \u002F>);\n  await user.click(screen.getByRole(\"button\", { name: \"Actions\" }));\n  await user.keyboard(\"{Escape}\");\n  expect(screen.getByRole(\"button\", { name: \"Actions\" })).toHaveFocus();\n});\n```\n\n`user.tab()` walks focus order, `user.keyboard('{Escape}')` fires the key, `toHaveFocus()` asserts the result — this is how keyboard behaviour is verified since the browser tools have no key-press action.\n\n## Common Mistakes\n\n- `div`\u002F`span` with `onClick` for an action.\n- Icon-only button with no `aria-label`.\n- A hand-rolled dropdown\u002Fdialog that traps keyboard users → use the Radix primitive.\n- Removing focus outlines with no replacement.\n- Status shown by color alone.\n- A touch target under 44px on phone, or `\u003Cinput>` text under 16px causing iOS zoom.\n- Shipping a keyboard interaction with no test proving it.\n\n## Red Flags\n\n- A clickable element that isn't a `button`\u002F`a`.\n- An interactive widget you built from raw `div`s instead of a primitive.\n- `outline: none` with nothing in its place.\n- `user-scalable=no` or `maximum-scale=1` in a viewport meta tag.\n- A component test suite with no `user.tab()`\u002F`user.keyboard()` coverage for a new interactive widget.\n",{"name":5,"source":24,"category":25,"description":7},"vercel-labs\u002Fweb-interface-guidelines (MIT), adapted","frontend","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Ffrontend-developer\u002Fskills\u002Faccessibility-basics",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill accessibility-basics",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill accessibility-basics",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill accessibility-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Ffrontend-developer\u002Fskills\u002Faccessibility-basics\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"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":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\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},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\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},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\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},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\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},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]