[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VF6HTQC6HC3JQKZ2M4R62":3,"skill-same:01M79VF6HTQC6HC3JQKZ2M4R62":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M79VF6HTQC6HC3JQKZ2M4R62","Accessibility Auditor",null,"Web accessibility specialist for WCAG compliance, ARIA implementation, and inclusive design. Use when auditing websites for accessibility issues, implementing WCAG 2.1 AA\u002FAAA standards, testing with screen readers, or ensuring ADA compliance. Expert in semantic HTML, keyboard navigation, and assistive technology compatibility.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Faccessibility-auditor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Accessibility Auditor\ndescription: Web accessibility specialist for WCAG compliance, ARIA implementation, and inclusive design. Use when auditing websites for accessibility issues, implementing WCAG 2.1 AA\u002FAAA standards, testing with screen readers, or ensuring ADA compliance. Expert in semantic HTML, keyboard navigation, and assistive technology compatibility.\n---\n\n# Accessibility Auditor\n\nComprehensive guidance for creating accessible web experiences that comply with WCAG standards and serve users of all abilities effectively.\n\n## When to Use This Skill\n\nUse this skill when:\n- Auditing websites for accessibility compliance\n- Implementing WCAG 2.1 Level AA or AAA standards\n- Fixing accessibility violations and errors\n- Testing with screen readers (NVDA, JAWS, VoiceOver)\n- Ensuring keyboard navigation works correctly\n- Implementing ARIA attributes and landmarks\n- Preparing for ADA or Section 508 compliance audits\n- Designing inclusive user experiences\n\n## WCAG 2.1 Principles (POUR)\n\n### 1. Perceivable\nUsers must be able to perceive the information being presented.\n\n### 2. Operable\nUsers must be able to operate the interface.\n\n### 3. Understandable\nUsers must be able to understand the information and interface.\n\n### 4. Robust\nContent must be robust enough to work with current and future technologies.\n\n## Common Accessibility Issues & Fixes\n\n### 1. Missing Alt Text for Images\n\n**❌ Problem:**\n```html\n\u003Cimg src=\"\u002Fproducts\u002Fshoes.jpg\">\n```\n\n**✅ Solution:**\n```html\n\u003C!-- Informative image -->\n\u003Cimg src=\"\u002Fproducts\u002Fshoes.jpg\" alt=\"Red Nike Air Max running shoes with white swoosh\">\n\n\u003C!-- Decorative image -->\n\u003Cimg src=\"\u002Fdecorative-pattern.svg\" alt=\"\" role=\"presentation\">\n\n\u003C!-- Logo that links -->\n\u003Ca href=\"\u002F\">\n  \u003Cimg src=\"\u002Flogo.png\" alt=\"Company Name - Home\">\n\u003C\u002Fa>\n```\n\n**Rules:**\n- Informative images: Describe the content\u002Ffunction\n- Decorative images: Use empty alt (alt=\"\")\n- Functional images: Describe the action\n- Complex images: Provide detailed description nearby\n\n### 2. Low Color Contrast\n\n**❌ Problem:**\n```css\n\u002F* Contrast ratio 2.5:1 - Fails WCAG *\u002F\n.text {\n  color: #767676;\n  background: #ffffff;\n}\n```\n\n**✅ Solution:**\n```css\n\u002F* Contrast ratio 4.5:1+ - Passes AA *\u002F\n.text {\n  color: #595959;\n  background: #ffffff;\n}\n\n\u002F* Contrast ratio 7:1+ - Passes AAA *\u002F\n.text-high-contrast {\n  color: #333333;\n  background: #ffffff;\n}\n```\n\n**Requirements:**\n- Normal text (\u003C 18px): 4.5:1 minimum (AA), 7:1 enhanced (AAA)\n- Large text (≥ 18px or ≥ 14px bold): 3:1 minimum (AA), 4.5:1 enhanced (AAA)\n- UI components and graphics: 3:1 minimum\n\n### 3. Non-Semantic HTML\n\n**❌ Problem:**\n```html\n\u003Cdiv class=\"button\" onclick=\"submitForm()\">Submit\u003C\u002Fdiv>\n\u003Cdiv class=\"heading\">Page Title\u003C\u002Fdiv>\n\u003Cdiv class=\"nav-menu\">...\u003C\u002Fdiv>\n```\n\n**✅ Solution:**\n```html\n\u003Cbutton type=\"submit\" onclick=\"submitForm()\">Submit\u003C\u002Fbutton>\n\u003Ch1>Page Title\u003C\u002Fh1>\n\u003Cnav aria-label=\"Main navigation\">...\u003C\u002Fnav>\n```\n\n**Semantic Elements:**\n- `\u003Cbutton>` for buttons\n- `\u003Ca>` for links\n- `\u003Ch1>` - `\u003Ch6>` for headings (hierarchical)\n- `\u003Cnav>`, `\u003Cmain>`, `\u003Caside>`, `\u003Carticle>`, `\u003Csection>` for landmarks\n- `\u003Cul>`, `\u003Col>`, `\u003Cli>` for lists\n- `\u003Ctable>`, `\u003Cth>`, `\u003Ctd>` for tabular data\n\n### 4. Missing Form Labels\n\n**❌ Problem:**\n```html\n\u003Cinput type=\"email\" placeholder=\"Enter your email\">\n```\n\n**✅ Solution:**\n```html\n\u003C!-- Explicit label -->\n\u003Clabel for=\"email\">Email Address\u003C\u002Flabel>\n\u003Cinput type=\"email\" id=\"email\" name=\"email\">\n\n\u003C!-- Implicit label -->\n\u003Clabel>\n  Email Address\n  \u003Cinput type=\"email\" name=\"email\">\n\u003C\u002Flabel>\n\n\u003C!-- Hidden label (for tight layouts) -->\n\u003Clabel for=\"search\" class=\"sr-only\">Search\u003C\u002Flabel>\n\u003Cinput type=\"text\" id=\"search\" placeholder=\"Search...\">\n```\n\n**Best Practices:**\n- Every form field must have an associated label\n- Labels should be visible (don't rely on placeholder)\n- Use aria-label only when visual label isn't possible\n- Group related fields with `\u003Cfieldset>` and `\u003Clegend>`\n\n### 5. Keyboard Navigation Issues\n\n**❌ Problem:**\n```html\n\u003Cdiv onclick=\"handleClick()\">Click me\u003C\u002Fdiv>\n\u003Ca href=\"javascript:void(0)\" onclick=\"doSomething()\">Action\u003C\u002Fa>\n```\n\n**✅ Solution:**\n```html\n\u003C!-- Use proper button -->\n\u003Cbutton onclick=\"handleClick()\">Click me\u003C\u002Fbutton>\n\n\u003C!-- If div required, make it accessible -->\n\u003Cdiv\n  role=\"button\"\n  tabindex=\"0\"\n  onclick=\"handleClick()\"\n  onkeydown=\"handleKeyPress(event)\"\n>\n  Click me\n\u003C\u002Fdiv>\n\n\u003Cscript>\nfunction handleKeyPress(event) {\n  if (event.key === 'Enter' || event.key === ' ') {\n    event.preventDefault();\n    handleClick();\n  }\n}\n\u003C\u002Fscript>\n```\n\n**Keyboard Requirements:**\n- All interactive elements must be keyboard accessible\n- Visible focus indicators (outline or custom styling)\n- Logical tab order (matches visual flow)\n- Skip links for repetitive content\n- No keyboard traps (users can navigate away)\n\n### 6. Missing ARIA Landmarks\n\n**❌ Problem:**\n```html\n\u003Cdiv class=\"header\">...\u003C\u002Fdiv>\n\u003Cdiv class=\"main-content\">...\u003C\u002Fdiv>\n\u003Cdiv class=\"sidebar\">...\u003C\u002Fdiv>\n\u003Cdiv class=\"footer\">...\u003C\u002Fdiv>\n```\n\n**✅ Solution:**\n```html\n\u003Cheader role=\"banner\">\n  \u003Cnav aria-label=\"Main navigation\">...\u003C\u002Fnav>\n\u003C\u002Fheader>\n\n\u003Cmain role=\"main\">\n  \u003Ch1>Page Title\u003C\u002Fh1>\n  \u003Carticle>...\u003C\u002Farticle>\n\u003C\u002Fmain>\n\n\u003Caside role=\"complementary\" aria-label=\"Related articles\">\n  ...\n\u003C\u002Faside>\n\n\u003Cfooter role=\"contentinfo\">\n  ...\n\u003C\u002Ffooter>\n```\n\n**Common Landmarks:**\n- `banner` - Site header\n- `navigation` - Navigation menus\n- `main` - Primary content (one per page)\n- `complementary` - Supporting content\n- `contentinfo` - Site footer\n- `search` - Search functionality\n- `form` - Form regions\n\n### 7. Inaccessible Modals\u002FDialogs\n\n**❌ Problem:**\n```html\n\u003Cdiv class=\"modal\">\n  \u003Cdiv class=\"content\">\n    Modal content\n    \u003Cbutton onclick=\"closeModal()\">Close\u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n**✅ Solution:**\n```html\n\u003Cdiv\n  role=\"dialog\"\n  aria-modal=\"true\"\n  aria-labelledby=\"modal-title\"\n  aria-describedby=\"modal-desc\"\n>\n  \u003Ch2 id=\"modal-title\">Confirm Action\u003C\u002Fh2>\n  \u003Cp id=\"modal-desc\">Are you sure you want to delete this item?\u003C\u002Fp>\n\n  \u003Cbutton onclick=\"confirmAction()\">Confirm\u003C\u002Fbutton>\n  \u003Cbutton onclick=\"closeModal()\">Cancel\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n\n\u003Cscript>\n\u002F\u002F Focus management\nfunction openModal() {\n  const modal = document.querySelector('[role=\"dialog\"]');\n  const focusableElements = modal.querySelectorAll(\n    'button, [href], input, select, textarea, [tabindex]:not([tabindex=\"-1\"])'\n  );\n\n  \u002F\u002F Store previous focus\n  previousFocus = document.activeElement;\n\n  \u002F\u002F Focus first element\n  focusableElements[0].focus();\n\n  \u002F\u002F Trap focus\n  modal.addEventListener('keydown', trapFocus);\n}\n\nfunction closeModal() {\n  \u002F\u002F Return focus\n  if (previousFocus) previousFocus.focus();\n}\n\nfunction trapFocus(event) {\n  if (event.key !== 'Tab') return;\n\n  const focusableElements = Array.from(\n    modal.querySelectorAll('button, [href], input, select, textarea, [tabindex]:not([tabindex=\"-1\"])')\n  );\n\n  const firstElement = focusableElements[0];\n  const lastElement = focusableElements[focusableElements.length - 1];\n\n  if (event.shiftKey && document.activeElement === firstElement) {\n    lastElement.focus();\n    event.preventDefault();\n  } else if (!event.shiftKey && document.activeElement === lastElement) {\n    firstElement.focus();\n    event.preventDefault();\n  }\n}\n\u003C\u002Fscript>\n```\n\n**Modal Requirements:**\n- `role=\"dialog\"` or `role=\"alertdialog\"`\n- `aria-modal=\"true\"` to indicate modal behavior\n- `aria-labelledby` pointing to title\n- `aria-describedby` for description (optional)\n- Focus management (trap and restore)\n- Close on Escape key\n- Prevent background scrolling\n\n### 8. Missing Skip Links\n\n**✅ Solution:**\n```html\n\u003Ca href=\"#main-content\" class=\"skip-link\">\n  Skip to main content\n\u003C\u002Fa>\n\n\u003Cheader>\n  \u003Cnav>...\u003C\u002Fnav>\n\u003C\u002Fheader>\n\n\u003Cmain id=\"main-content\" tabindex=\"-1\">\n  \u003C!-- Page content -->\n\u003C\u002Fmain>\n\n\u003Cstyle>\n.skip-link {\n  position: absolute;\n  top: -40px;\n  left: 0;\n  background: #000;\n  color: #fff;\n  padding: 8px;\n  text-decoration: none;\n  z-index: 100;\n}\n\n.skip-link:focus {\n  top: 0;\n}\n\u003C\u002Fstyle>\n```\n\n## ARIA Best Practices\n\n### ARIA Attributes Reference\n\n**States:**\n- `aria-checked` - Checkbox\u002Fradio state\n- `aria-disabled` - Disabled state\n- `aria-expanded` - Expanded\u002Fcollapsed state\n- `aria-hidden` - Hidden from assistive technology\n- `aria-pressed` - Toggle button state\n- `aria-selected` - Selected state\n\n**Properties:**\n- `aria-label` - Accessible name\n- `aria-labelledby` - ID reference for label\n- `aria-describedby` - ID reference for description\n- `aria-live` - Live region updates\n- `aria-required` - Required field\n- `aria-invalid` - Validation state\n\n### Live Regions\n\n```html\n\u003C!-- Polite: Wait for pause in speech -->\n\u003Cdiv aria-live=\"polite\" aria-atomic=\"true\">\n  Item added to cart\n\u003C\u002Fdiv>\n\n\u003C!-- Assertive: Interrupt immediately -->\n\u003Cdiv aria-live=\"assertive\" role=\"alert\">\n  Error: Payment failed\n\u003C\u002Fdiv>\n\n\u003C!-- Status message -->\n\u003Cdiv role=\"status\" aria-live=\"polite\">\n  Saving changes...\n\u003C\u002Fdiv>\n```\n\n### Custom Components\n\n**Accordion:**\n```html\n\u003Cdiv class=\"accordion\">\n  \u003Cbutton\n    aria-expanded=\"false\"\n    aria-controls=\"panel-1\"\n    id=\"accordion-1\"\n  >\n    Section 1\n  \u003C\u002Fbutton>\n  \u003Cdiv id=\"panel-1\" role=\"region\" aria-labelledby=\"accordion-1\" hidden>\n    Panel content\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n**Tabs:**\n```html\n\u003Cdiv role=\"tablist\" aria-label=\"Content sections\">\n  \u003Cbutton\n    role=\"tab\"\n    aria-selected=\"true\"\n    aria-controls=\"panel-1\"\n    id=\"tab-1\"\n  >\n    Tab 1\n  \u003C\u002Fbutton>\n  \u003Cbutton\n    role=\"tab\"\n    aria-selected=\"false\"\n    aria-controls=\"panel-2\"\n    id=\"tab-2\"\n    tabindex=\"-1\"\n  >\n    Tab 2\n  \u003C\u002Fbutton>\n\u003C\u002Fdiv>\n\n\u003Cdiv role=\"tabpanel\" id=\"panel-1\" aria-labelledby=\"tab-1\">\n  Panel 1 content\n\u003C\u002Fdiv>\n\u003Cdiv role=\"tabpanel\" id=\"panel-2\" aria-labelledby=\"tab-2\" hidden>\n  Panel 2 content\n\u003C\u002Fdiv>\n```\n\n## Testing Checklist\n\n### Automated Testing\n- [ ] Run axe DevTools or WAVE browser extension\n- [ ] Check HTML validation (W3C Validator)\n- [ ] Test color contrast ratios\n- [ ] Verify heading hierarchy\n- [ ] Check for missing alt text\n\n### Manual Testing\n- [ ] Navigate entire site using only keyboard (Tab, Enter, Escape, Arrow keys)\n- [ ] Test with screen reader (NVDA, JAWS, or VoiceOver)\n- [ ] Verify focus indicators are visible\n- [ ] Check form validation messages are announced\n- [ ] Test modal focus trapping\n- [ ] Verify skip links work\n- [ ] Test with browser zoom at 200%\n- [ ] Check page reflow at different viewport sizes\n- [ ] Disable JavaScript and verify core functionality\n- [ ] Test with Windows High Contrast mode\n\n### Screen Reader Testing\n\n**VoiceOver (Mac):**\n- Enable: Cmd + F5\n- Navigate: Control + Option + Arrow keys\n- Read all: Control + Option + A\n\n**NVDA (Windows):**\n- Navigate: Arrow keys (browse mode) or Tab (focus mode)\n- Read all: NVDA + Down Arrow\n- Elements list: NVDA + F7\n\n**Test Scenarios:**\n- Can users understand page structure?\n- Are headings descriptive and hierarchical?\n- Are form labels clear and associated?\n- Are error messages announced?\n- Can users complete key tasks without vision?\n\n## Accessibility Statement\n\nInclude on website:\n\n```markdown\n# Accessibility Statement\n\nWe are committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards.\n\n## Conformance Status\nThis website is partially conformant with WCAG 2.1 Level AA. \"Partially conformant\" means that some parts of the content do not fully conform to the accessibility standard.\n\n## Feedback\nWe welcome your feedback on the accessibility of this site. Please contact us:\n- Email: accessibility@example.com\n- Phone: +1-555-0123\n\n## Known Issues\n- [List any known accessibility issues and planned fixes]\n\nLast updated: [Date]\n```\n\n## Resources\n\n**Tools:**\n- axe DevTools (browser extension)\n- WAVE (web accessibility evaluation tool)\n- Lighthouse (Chrome DevTools)\n- Colour Contrast Analyser\n- Screen readers: NVDA, JAWS, VoiceOver\n\n**Guidelines:**\n- WCAG 2.1: https:\u002F\u002Fwww.w3.org\u002FWAI\u002FWCAG21\u002Fquickref\u002F\n- ARIA Authoring Practices: https:\u002F\u002Fwww.w3.org\u002FWAI\u002FARIA\u002Fapg\u002F\n\nAccessibility is not optional—it's a fundamental requirement for creating inclusive web experiences. Prioritize it from the start of every project, not as an afterthought.\n","# Accessibility Auditor\n\nComprehensive guidance for creating accessible web experiences that comply with WCAG standards and serve users of all abilities effectively.\n\n## When to Use This Skill\n\nUse this skill when:\n- Auditing websites for accessibility compliance\n- Implementing WCAG 2.1 Level AA or AAA standards\n- Fixing accessibility violations and errors\n- Testing with screen readers (NVDA, JAWS, VoiceOver)\n- Ensuring keyboard navigation works correctly\n- Implementing ARIA attributes and landmarks\n- Preparing for ADA or Section 508 compliance audits\n- Designing inclusive user experiences\n\n## WCAG 2.1 Principles (POUR)\n\n### 1. Perceivable\nUsers must be able to perceive the information being presented.\n\n### 2. Operable\nUsers must be able to operate the interface.\n\n### 3. Understandable\nUsers must be able to understand the information and interface.\n\n### 4. Robust\nContent must be robust enough to work with current and future technologies.\n\n## Common Accessibility Issues & Fixes\n\n### 1. Missing Alt Text for Images\n\n**❌ Problem:**\n```html\n\u003Cimg src=\"\u002Fproducts\u002Fshoes.jpg\">\n```\n\n**✅ Solution:**\n```html\n\u003C!-- Informative image -->\n\u003Cimg src=\"\u002Fproducts\u002Fshoes.jpg\" alt=\"Red Nike Air Max running shoes with white swoosh\">\n\n\u003C!-- Decorative image -->\n\u003Cimg src=\"\u002Fdecorative-pattern.svg\" alt=\"\" role=\"presentation\">\n\n\u003C!-- Logo that links -->\n\u003Ca href=\"\u002F\">\n  \u003Cimg src=\"\u002Flogo.png\" alt=\"Company Name - Home\">\n\u003C\u002Fa>\n```\n\n**Rules:**\n- Informative images: Describe the content\u002Ffunction\n- Decorative images: Use empty alt (alt=\"\")\n- Functional images: Describe the action\n- Complex images: Provide detailed description nearby\n\n### 2. Low Color Contrast\n\n**❌ Problem:**\n```css\n\u002F* Contrast ratio 2.5:1 - Fails WCAG *\u002F\n.text {\n  color: #767676;\n  background: #ffffff;\n}\n```\n\n**✅ Solution:**\n```css\n\u002F* Contrast ratio 4.5:1+ - Passes AA *\u002F\n.text {\n  color: #595959;\n  background: #ffffff;\n}\n\n\u002F* Contrast ratio 7:1+ - Passes AAA *\u002F\n.text-high-contrast {\n  color: #333333;\n  background: #ffffff;\n}\n```\n\n**Requirements:**\n- Normal text (\u003C 18px): 4.5:1 minimum (AA), 7:1 enhanced (AAA)\n- Large text (≥ 18px or ≥ 14px bold): 3:1 minimum (AA), 4.5:1 enhanced (AAA)\n- UI components and graphics: 3:1 minimum\n\n### 3. Non-Semantic HTML\n\n**❌ Problem:**\n```html\n\u003Cdiv class=\"button\" onclick=\"submitForm()\">Submit\u003C\u002Fdiv>\n\u003Cdiv class=\"heading\">Page Title\u003C\u002Fdiv>\n\u003Cdiv class=\"nav-menu\">...\u003C\u002Fdiv>\n```\n\n**✅ Solution:**\n```html\n\u003Cbutton type=\"submit\" onclick=\"submitForm()\">Submit\u003C\u002Fbutton>\n\u003Ch1>Page Title\u003C\u002Fh1>\n\u003Cnav aria-label=\"Main navigation\">...\u003C\u002Fnav>\n```\n\n**Semantic Elements:**\n- `\u003Cbutton>` for buttons\n- `\u003Ca>` for links\n- `\u003Ch1>` - `\u003Ch6>` for headings (hierarchical)\n- `\u003Cnav>`, `\u003Cmain>`, `\u003Caside>`, `\u003Carticle>`, `\u003Csection>` for landmarks\n- `\u003Cul>`, `\u003Col>`, `\u003Cli>` for lists\n- `\u003Ctable>`, `\u003Cth>`, `\u003Ctd>` for tabular data\n\n### 4. Missing Form Labels\n\n**❌ Problem:**\n```html\n\u003Cinput type=\"email\" placeholder=\"Enter your email\">\n```\n\n**✅ Solution:**\n```html\n\u003C!-- Explicit label -->\n\u003Clabel for=\"email\">Email Address\u003C\u002Flabel>\n\u003Cinput type=\"email\" id=\"email\" name=\"email\">\n\n\u003C!-- Implicit label -->\n\u003Clabel>\n  Email Address\n  \u003Cinput type=\"email\" name=\"email\">\n\u003C\u002Flabel>\n\n\u003C!-- Hidden label (for tight layouts) -->\n\u003Clabel for=\"search\" class=\"sr-only\">Search\u003C\u002Flabel>\n\u003Cinput type=\"text\" id=\"search\" placeholder=\"Search...\">\n```\n\n**Best Practices:**\n- Every form field must have an associated label\n- Labels should be visible (don't rely on placeholder)\n- Use aria-label only when visual label isn't possible\n- Group related fields with `\u003Cfieldset>` and `\u003Clegend>`\n\n### 5. Keyboard Navigation Issues\n\n**❌ Problem:**\n```html\n\u003Cdiv onclick=\"handleClick()\">Click me\u003C\u002Fdiv>\n\u003Ca href=\"javascript:void(0)\" onclick=\"doSomething()\">Action\u003C\u002Fa>\n```\n\n**✅ Solution:**\n```html\n\u003C!-- Use proper button -->\n\u003Cbutton onclick=\"handleClick()\">Click me\u003C\u002Fbutton>\n\n\u003C!-- If div required, make it accessible -->\n\u003Cdiv\n  role=\"button\"\n  tabindex=\"0\"\n  onclick=\"handleClick()\"\n  onkeydown=\"handleKeyPress(event)\"\n>\n  Click me\n\u003C\u002Fdiv>\n\n\u003Cscript>\nfunction handleKeyPress(event) {\n  if (event.key === 'Enter' || event.key === ' ') {\n    event.preventDefault();\n    handleClick();\n  }\n}\n\u003C\u002Fscript>\n```\n\n**Keyboard Requirements:**\n- All interactive elements must be keyboard accessible\n- Visible focus indicators (outline or custom styling)\n- Logical tab order (matches visual flow)\n- Skip links for repetitive content\n- No keyboard traps (users can navigate away)\n\n### 6. Missing ARIA Landmarks\n\n**❌ Problem:**\n```html\n\u003Cdiv class=\"header\">...\u003C\u002Fdiv>\n\u003Cdiv class=\"main-content\">...\u003C\u002Fdiv>\n\u003Cdiv class=\"sidebar\">...\u003C\u002Fdiv>\n\u003Cdiv class=\"footer\">...\u003C\u002Fdiv>\n```\n\n**✅ Solution:**\n```html\n\u003Cheader role=\"banner\">\n  \u003Cnav aria-label=\"Main navigation\">...\u003C\u002Fnav>\n\u003C\u002Fheader>\n\n\u003Cmain role=\"main\">\n  \u003Ch1>Page Title\u003C\u002Fh1>\n  \u003Carticle>...\u003C\u002Farticle>\n\u003C\u002Fmain>\n\n\u003Caside role=\"complementary\" aria-label=\"Related articles\">\n  ...\n\u003C\u002Faside>\n\n\u003Cfooter role=\"contentinfo\">\n  ...\n\u003C\u002Ffooter>\n```\n\n**Common Landmarks:**\n- `banner` - Site header\n- `navigation` - Navigation menus\n- `main` - Primary content (one per page)\n- `complementary` - Supporting content\n- `contentinfo` - Site footer\n- `search` - Search functionality\n- `form` - Form regions\n\n### 7. Inaccessible Modals\u002FDialogs\n\n**❌ Problem:**\n```html\n\u003Cdiv class=\"modal\">\n  \u003Cdiv class=\"content\">\n    Modal content\n    \u003Cbutton onclick=\"closeModal()\">Close\u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n**✅ Solution:**\n```html\n\u003Cdiv\n  role=\"dialog\"\n  aria-modal=\"true\"\n  aria-labelledby=\"modal-title\"\n  aria-describedby=\"modal-desc\"\n>\n  \u003Ch2 id=\"modal-title\">Confirm Action\u003C\u002Fh2>\n  \u003Cp id=\"modal-desc\">Are you sure you want to delete this item?\u003C\u002Fp>\n\n  \u003Cbutton onclick=\"confirmAction()\">Confirm\u003C\u002Fbutton>\n  \u003Cbutton onclick=\"closeModal()\">Cancel\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n\n\u003Cscript>\n\u002F\u002F Focus management\nfunction openModal() {\n  const modal = document.querySelector('[role=\"dialog\"]');\n  const focusableElements = modal.querySelectorAll(\n    'button, [href], input, select, textarea, [tabindex]:not([tabindex=\"-1\"])'\n  );\n\n  \u002F\u002F Store previous focus\n  previousFocus = document.activeElement;\n\n  \u002F\u002F Focus first element\n  focusableElements[0].focus();\n\n  \u002F\u002F Trap focus\n  modal.addEventListener('keydown', trapFocus);\n}\n\nfunction closeModal() {\n  \u002F\u002F Return focus\n  if (previousFocus) previousFocus.focus();\n}\n\nfunction trapFocus(event) {\n  if (event.key !== 'Tab') return;\n\n  const focusableElements = Array.from(\n    modal.querySelectorAll('button, [href], input, select, textarea, [tabindex]:not([tabindex=\"-1\"])')\n  );\n\n  const firstElement = focusableElements[0];\n  const lastElement = focusableElements[focusableElements.length - 1];\n\n  if (event.shiftKey && document.activeElement === firstElement) {\n    lastElement.focus();\n    event.preventDefault();\n  } else if (!event.shiftKey && document.activeElement === lastElement) {\n    firstElement.focus();\n    event.preventDefault();\n  }\n}\n\u003C\u002Fscript>\n```\n\n**Modal Requirements:**\n- `role=\"dialog\"` or `role=\"alertdialog\"`\n- `aria-modal=\"true\"` to indicate modal behavior\n- `aria-labelledby` pointing to title\n- `aria-describedby` for description (optional)\n- Focus management (trap and restore)\n- Close on Escape key\n- Prevent background scrolling\n\n### 8. Missing Skip Links\n\n**✅ Solution:**\n```html\n\u003Ca href=\"#main-content\" class=\"skip-link\">\n  Skip to main content\n\u003C\u002Fa>\n\n\u003Cheader>\n  \u003Cnav>...\u003C\u002Fnav>\n\u003C\u002Fheader>\n\n\u003Cmain id=\"main-content\" tabindex=\"-1\">\n  \u003C!-- Page content -->\n\u003C\u002Fmain>\n\n\u003Cstyle>\n.skip-link {\n  position: absolute;\n  top: -40px;\n  left: 0;\n  background: #000;\n  color: #fff;\n  padding: 8px;\n  text-decoration: none;\n  z-index: 100;\n}\n\n.skip-link:focus {\n  top: 0;\n}\n\u003C\u002Fstyle>\n```\n\n## ARIA Best Practices\n\n### ARIA Attributes Reference\n\n**States:**\n- `aria-checked` - Checkbox\u002Fradio state\n- `aria-disabled` - Disabled state\n- `aria-expanded` - Expanded\u002Fcollapsed state\n- `aria-hidden` - Hidden from assistive technology\n- `aria-pressed` - Toggle button state\n- `aria-selected` - Selected state\n\n**Properties:**\n- `aria-label` - Accessible name\n- `aria-labelledby` - ID reference for label\n- `aria-describedby` - ID reference for description\n- `aria-live` - Live region updates\n- `aria-required` - Required field\n- `aria-invalid` - Validation state\n\n### Live Regions\n\n```html\n\u003C!-- Polite: Wait for pause in speech -->\n\u003Cdiv aria-live=\"polite\" aria-atomic=\"true\">\n  Item added to cart\n\u003C\u002Fdiv>\n\n\u003C!-- Assertive: Interrupt immediately -->\n\u003Cdiv aria-live=\"assertive\" role=\"alert\">\n  Error: Payment failed\n\u003C\u002Fdiv>\n\n\u003C!-- Status message -->\n\u003Cdiv role=\"status\" aria-live=\"polite\">\n  Saving changes...\n\u003C\u002Fdiv>\n```\n\n### Custom Components\n\n**Accordion:**\n```html\n\u003Cdiv class=\"accordion\">\n  \u003Cbutton\n    aria-expanded=\"false\"\n    aria-controls=\"panel-1\"\n    id=\"accordion-1\"\n  >\n    Section 1\n  \u003C\u002Fbutton>\n  \u003Cdiv id=\"panel-1\" role=\"region\" aria-labelledby=\"accordion-1\" hidden>\n    Panel content\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n**Tabs:**\n```html\n\u003Cdiv role=\"tablist\" aria-label=\"Content sections\">\n  \u003Cbutton\n    role=\"tab\"\n    aria-selected=\"true\"\n    aria-controls=\"panel-1\"\n    id=\"tab-1\"\n  >\n    Tab 1\n  \u003C\u002Fbutton>\n  \u003Cbutton\n    role=\"tab\"\n    aria-selected=\"false\"\n    aria-controls=\"panel-2\"\n    id=\"tab-2\"\n    tabindex=\"-1\"\n  >\n    Tab 2\n  \u003C\u002Fbutton>\n\u003C\u002Fdiv>\n\n\u003Cdiv role=\"tabpanel\" id=\"panel-1\" aria-labelledby=\"tab-1\">\n  Panel 1 content\n\u003C\u002Fdiv>\n\u003Cdiv role=\"tabpanel\" id=\"panel-2\" aria-labelledby=\"tab-2\" hidden>\n  Panel 2 content\n\u003C\u002Fdiv>\n```\n\n## Testing Checklist\n\n### Automated Testing\n- [ ] Run axe DevTools or WAVE browser extension\n- [ ] Check HTML validation (W3C Validator)\n- [ ] Test color contrast ratios\n- [ ] Verify heading hierarchy\n- [ ] Check for missing alt text\n\n### Manual Testing\n- [ ] Navigate entire site using only keyboard (Tab, Enter, Escape, Arrow keys)\n- [ ] Test with screen reader (NVDA, JAWS, or VoiceOver)\n- [ ] Verify focus indicators are visible\n- [ ] Check form validation messages are announced\n- [ ] Test modal focus trapping\n- [ ] Verify skip links work\n- [ ] Test with browser zoom at 200%\n- [ ] Check page reflow at different viewport sizes\n- [ ] Disable JavaScript and verify core functionality\n- [ ] Test with Windows High Contrast mode\n\n### Screen Reader Testing\n\n**VoiceOver (Mac):**\n- Enable: Cmd + F5\n- Navigate: Control + Option + Arrow keys\n- Read all: Control + Option + A\n\n**NVDA (Windows):**\n- Navigate: Arrow keys (browse mode) or Tab (focus mode)\n- Read all: NVDA + Down Arrow\n- Elements list: NVDA + F7\n\n**Test Scenarios:**\n- Can users understand page structure?\n- Are headings descriptive and hierarchical?\n- Are form labels clear and associated?\n- Are error messages announced?\n- Can users complete key tasks without vision?\n\n## Accessibility Statement\n\nInclude on website:\n\n```markdown\n# Accessibility Statement\n\nWe are committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards.\n\n## Conformance Status\nThis website is partially conformant with WCAG 2.1 Level AA. \"Partially conformant\" means that some parts of the content do not fully conform to the accessibility standard.\n\n## Feedback\nWe welcome your feedback on the accessibility of this site. Please contact us:\n- Email: accessibility@example.com\n- Phone: +1-555-0123\n\n## Known Issues\n- [List any known accessibility issues and planned fixes]\n\nLast updated: [Date]\n```\n\n## Resources\n\n**Tools:**\n- axe DevTools (browser extension)\n- WAVE (web accessibility evaluation tool)\n- Lighthouse (Chrome DevTools)\n- Colour Contrast Analyser\n- Screen readers: NVDA, JAWS, VoiceOver\n\n**Guidelines:**\n- WCAG 2.1: https:\u002F\u002Fwww.w3.org\u002FWAI\u002FWCAG21\u002Fquickref\u002F\n- ARIA Authoring Practices: https:\u002F\u002Fwww.w3.org\u002FWAI\u002FARIA\u002Fapg\u002F\n\nAccessibility is not optional—it's a fundamental requirement for creating inclusive web experiences. Prioritize it from the start of every project, not as an afterthought.\n",{"name":5,"description":7},"main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Faccessibility-auditor","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill \"Accessibility Auditor\"",{"tool":35,"command":36},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill \"Accessibility Auditor\"",{"tool":38,"command":39},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill \"Accessibility Auditor\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Faccessibility-auditor\u002FSKILL.md",true,[],[44,51,60,67,74,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":55,"licenseFileUrl":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]