[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWH32SN5SN47VDTA31CDGB":3,"skill-same:01M6JWH32SN5SN47VDTA31CDGB":75},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6JWH32SN5SN47VDTA31CDGB","accessibility-operable",null,"Use this skill when the question is whether users can *operate* a UI — keyboard, switch device, voice, screen-reader gestures — not just by mouse or touch. Trigger when designing keyboard navigation, focus management for modals\u002Fmenus\u002Fpopovers, drag-and-drop with alternatives, motion-heavy interactions, or any flow that asks the user to do something. Covers WCAG Principle 2 (Operable). Sub-aspect of `accessibility`; read that first if you haven't already.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-operable\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"accessibility","accessibility operable","when","gestures","alternatives","for","operate","you","drag","screen","keyboard","trigger","focus","drop","do","switch","read","question","just","flow","ui","2026-11-10 10:12:30",false,"---\nname: accessibility-operable\ndescription: 'Use this skill when the question is whether users can *operate* a UI — keyboard, switch device, voice, screen-reader gestures — not just by mouse or touch. Trigger when designing keyboard navigation, focus management for modals\u002Fmenus\u002Fpopovers, drag-and-drop with alternatives, motion-heavy interactions, or any flow that asks the user to do something. Covers WCAG Principle 2 (Operable). Sub-aspect of `accessibility`; read that first if you haven''t already.'\n---\n\n# Accessibility — Operable\n\nWCAG Principle 2: user-interface components and navigation must be operable.\n\nThe five sub-criteria, simplified:\n\n1. **Keyboard accessible** — everything that works with mouse must work with keyboard.\n2. **Enough time** — timing-out interactions are warned and extendable.\n3. **Seizures and physical reactions** — no flashing content; respect motion preferences.\n4. **Navigable** — users can find content and know where they are.\n5. **Input modalities** — touch and other input methods supported with adequate target size.\n\n## 1. Keyboard accessible\n\n### Every interactive element is reachable via Tab\n\nThe default `Tab` order follows DOM source order and only includes natively focusable elements: `\u003Ca href>`, `\u003Cbutton>`, `\u003Cinput>`, `\u003Cselect>`, `\u003Ctextarea>`, `\u003Csummary>`, `\u003Ciframe>`, plus elements with `tabindex=\"0\"`.\n\n- **Use semantic elements.** `\u003Cbutton>`, not `\u003Cdiv onclick>`.\n- **Use `tabindex=\"0\"`** to add custom interactive elements to tab order.\n- **Use `tabindex=\"-1\"`** to make an element programmatically focusable (e.g., for focus management) but not reachable via Tab.\n- **Avoid `tabindex` > 0.** Positive tabindex creates a custom tab order that's almost always worse than DOM order and bewilders screen readers.\n\n### Visible focus indicators\n\nThe user must see where focus is. Browsers provide default focus rings; never `outline: none` without a replacement.\n\n```css\n\u002F* Right: replace, don't remove *\u002F\n:focus { outline: none; }\n:focus-visible {\n  outline: 2px solid hsl(220 90% 50%);\n  outline-offset: 2px;\n  border-radius: 0.25rem;\n}\n\n\u002F* Wrong: removes the only signal a keyboard user has *\u002F\n*:focus { outline: none; }\n```\n\n`:focus-visible` (rather than `:focus`) shows the ring only when focus arrived via keyboard (or non-pointer means), not on every mouse click. This addresses the historical \"designers don't want focus rings on click\" concern without sacrificing keyboard accessibility.\n\n### Standard keys for standard interactions\n\nHonor user expectations:\n\n| Key | Behavior |\n|---|---|\n| `Tab` | Focus next; `Shift+Tab` for previous |\n| `Enter` \u002F `Space` | Activate button, follow link, toggle checkbox |\n| `Esc` | Close overlay (Dialog, Sheet, Popover, Combobox) |\n| Arrow keys | Move within radio groups, sliders, tabs, menus, comboboxes |\n| `Home` \u002F `End` | First \u002F last in a list or menu |\n| `Page Up` \u002F `Down` | Scroll a region |\n| `\u002F` | Often: focus search (de facto convention) |\n| `Cmd\u002FCtrl+K` | Often: open command palette (de facto convention) |\n\nARIA Authoring Practices Guide documents canonical keyboard interactions for every common pattern.\n\n### No keyboard traps\n\nA keyboard trap is a region where focus enters and cannot leave via keyboard alone. Common offenders:\n\n- Custom datepickers without arrow-key escape.\n- Embedded iframes with their own focus management that don't release.\n- Modal dialogs without `Esc` to close.\n\n**Test:** keyboard-only walkthrough. If you ever get stuck and have to mouse to escape, you have a trap.\n\n### Focus management for overlays\n\nWhen a modal opens:\n\n1. Move focus into the modal (typically the first focusable element, or a \"primary\" focus target).\n2. Trap focus inside until the modal closes.\n3. Restore focus to the trigger element when the modal closes.\n\n```js\n\u002F\u002F Pseudocode — in practice use a library that handles edge cases\nfunction openModal(modal, trigger) {\n  modal.dataset.previousFocus = trigger;\n  const focusables = modal.querySelectorAll('a, button, input, [tabindex=\"0\"]');\n  focusables[0]?.focus();\n  \u002F\u002F ... trap focus on Tab\u002FShift+Tab within `focusables` ...\n}\n\nfunction closeModal(modal) {\n  modal.previousFocus?.focus();\n}\n```\n\nMost accessible UI libraries (Radix UI, React Aria, headless component sets) do this automatically. Custom-built modals that skip focus management are inaccessible.\n\n### Skip links\n\n```html\n\u003Ca href=\"#main\" class=\"skip-link\">Skip to main content\u003C\u002Fa>\n\u003Cheader>\u003Cnav>... 50 nav items ...\u003C\u002Fnav>\u003C\u002Fheader>\n\u003Cmain id=\"main\">...\u003C\u002Fmain>\n\n\u003Cstyle>\n  .skip-link {\n    position: absolute;\n    left: -10000px;\n    top: auto;\n  }\n  .skip-link:focus {\n    position: fixed;\n    top: 8px; left: 8px;\n    padding: 8px 16px;\n    background: black; color: white;\n    z-index: 100;\n  }\n\u003C\u002Fstyle>\n```\n\nKeyboard users tab past nav to reach content quickly. Visible only on focus so it doesn't clutter sighted-mouse-user views.\n\n## 2. Enough time\n\n### Adjustable timing\n\nIf the system has timeouts (session expiry, captcha re-verify, time-limited form), users must be able to:\n\n- Turn it off, OR\n- Extend it, OR\n- Adjust it (across a wide range, ≥ 10× default).\n\nExceptions: real-time events (auctions), where time limit is essential.\n\n```html\n\u003C!-- Right: warn before timeout, allow extension -->\n\u003Cdialog open>\n  \u003Ch2>Session about to expire\u003C\u002Fh2>\n  \u003Cp>You have 60 seconds before your session ends.\u003C\u002Fp>\n  \u003Cbutton onclick=\"extendSession()\">Stay signed in\u003C\u002Fbutton>\n\u003C\u002Fdialog>\n```\n\n### No moving \u002F blinking content (without controls)\n\nContent that auto-moves, blinks, or scrolls for more than 5 seconds must be pause-able \u002F stop-able.\n\nThis includes carousels, animated banners, news tickers, autoplaying video.\n\n## 3. Seizures and physical reactions\n\n### Three flashes or below\n\nWCAG 2.3.1: don't have content that flashes more than 3 times per second. Photosensitive epilepsy can be triggered by flashing in the 3–55 Hz range.\n\nIn practice, this rules out: rapid strobe effects, blinking text (don't), high-contrast flashing animations.\n\n### Motion preferences\n\nWCAG 2.3.3: respect `prefers-reduced-motion`. Many users (vestibular disorders, migraine, motion sensitivity) have configured their OS to request reduced motion.\n\n```css\n@media (prefers-reduced-motion: reduce) {\n  *, *::before, *::after {\n    animation-duration: 0.01ms !important;\n    animation-iteration-count: 1 !important;\n    transition-duration: 0.01ms !important;\n    scroll-behavior: auto !important;\n  }\n}\n```\n\nFor specific motion that's *meaningful* (a state change indicator), allow it but make it briefer \u002F less dramatic in reduced-motion mode.\n\n## 4. Navigable\n\n### Page titles\n\nEvery page has a unique, descriptive `\u003Ctitle>`:\n\n```html\n\u003Ctitle>Settings — Notifications — Acme\u003C\u002Ftitle>\n```\n\nScreen reader users hear the title on page load; tab labels show it; browser history relies on it. Generic \"Acme\" titles for every page are useless.\n\n### Focus order matches reading order\n\nWhen a user tabs through a page, focus should follow the visual \u002F logical reading order. CSS-rearranged elements (Grid, Flex order) can break this — test.\n\n### Link purpose\n\nLinks should be understandable from their text alone (or from text + immediately-adjacent context). Screen reader users navigate by listing all links.\n\n```html\n\u003C!-- Wrong: \"click here\" tells the screen reader user nothing -->\n\u003Cp>To read more, \u003Ca href=\"\u002Fblog\u002Fpost\">click here\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003C!-- Right: link text describes destination -->\n\u003Cp>Read more in \u003Ca href=\"\u002Fblog\u002Fpost\">our annual review\u003C\u002Fa>.\u003C\u002Fp>\n```\n\n### Multiple ways to find content\n\nWCAG 2.4.5 (AA): provide more than one way to find a page (search, sitemap, navigation, related-content links). Helps users with cognitive impairments and users who navigate non-linearly.\n\n### Headings and labels are descriptive\n\n`\u003Ch2>Article\u003C\u002Fh2>` — useless. `\u003Ch2>Q4 sales recap\u003C\u002Fh2>` — useful.\n\n### Focus visible (covered above)\n\n### Location indicators\n\nUsers need to know where they are. Breadcrumbs, current-page highlighting in nav, page titles all serve this.\n\n```html\n\u003Cnav>\n  \u003Ca href=\"\u002Fdashboard\">Dashboard\u003C\u002Fa>\n  \u003Ca href=\"\u002Fprojects\" aria-current=\"page\">Projects\u003C\u002Fa>\n  \u003Ca href=\"\u002Fteam\">Team\u003C\u002Fa>\n\u003C\u002Fnav>\n```\n\n`aria-current=\"page\"` tells assistive tech which item is current; visual styling reinforces it.\n\n## 5. Input modalities\n\n### Target size (covered in `fitts-law-touch-targets`)\n\nWCAG 2.5.5 (AAA): targets ≥ 44×44 CSS px.\nWCAG 2.5.8 (AA, 2.2): targets ≥ 24×24 CSS px with adequate spacing.\n\n### Pointer gestures\n\nMulti-pointer or path-based gestures (pinch, swipe, drag) must have single-pointer alternatives:\n\n- Pinch-to-zoom → buttons \u002F keyboard for zoom in\u002Fout.\n- Swipe-to-delete → swipe + always-visible action button.\n- Drag-and-drop → keyboard reorder (arrows + spacebar).\n\n### Pointer cancellation\n\nThe user can cancel a pointer action by moving away before lifting. Don't trigger destructive actions on `mousedown`; trigger on `mouseup` or `click`.\n\n### Label in name\n\nThe accessible name must include any visible label text. Pattern:\n\n```html\n\u003C!-- Right: visible text matches accessible name -->\n\u003Cbutton>Save\u003C\u002Fbutton>\n\n\u003C!-- Wrong: aria-label overrides visible text, voice control breaks -->\n\u003Cbutton aria-label=\"Submit\">Save\u003C\u002Fbutton>\n\u003C!-- Voice user says \"click Save\" — fails because the accessible name is \"Submit\" -->\n```\n\n### Motion actuation\n\nFunctions triggered by device motion (shake, tilt) must have UI alternatives. Some users physically can't shake a device.\n\n## Worked example: an accessible dropdown menu\n\n```html\n\u003Cdiv class=\"dropdown\">\n  \u003Cbutton id=\"menu-button\"\n          aria-haspopup=\"true\"\n          aria-expanded=\"false\"\n          aria-controls=\"actions-menu\">\n    Actions\n  \u003C\u002Fbutton>\n  \u003Cul id=\"actions-menu\"\n      role=\"menu\"\n      hidden\n      aria-labelledby=\"menu-button\">\n    \u003Cli role=\"menuitem\" tabindex=\"-1\">Edit\u003C\u002Fli>\n    \u003Cli role=\"menuitem\" tabindex=\"-1\">Duplicate\u003C\u002Fli>\n    \u003Cli role=\"menuitem\" tabindex=\"-1\">Archive\u003C\u002Fli>\n    \u003Cli role=\"separator\">\u003C\u002Fli>\n    \u003Cli role=\"menuitem\" tabindex=\"-1\" class=\"destructive\">Delete\u003C\u002Fli>\n  \u003C\u002Ful>\n\u003C\u002Fdiv>\n```\n\nJavaScript to handle:\n\n- `Enter`\u002F`Space`\u002F`ArrowDown` on the button: open menu, focus first item.\n- `ArrowUp`\u002F`ArrowDown` in menu: move focus.\n- `Home`\u002F`End`: first \u002F last item.\n- `Esc`: close, return focus to button.\n- `Tab`: close, move to next focusable.\n- Click outside: close.\n\nPlus `aria-expanded` toggles between `\"true\"` and `\"false\"`.\n\nThis is verbose because menus genuinely have a lot of expected behavior. Use Radix, React Aria, or another library that implements WAI-ARIA Menu pattern correctly — don't roll your own.\n\n## Anti-patterns\n\n- **`outline: none` without a replacement.** Single largest accessibility crime in modern web design.\n- **`\u003Cdiv onclick>`.** Not focusable, not keyboard-operable, not announced as a button. Use `\u003Cbutton>`.\n- **Mouse-only menus.** Hover-revealed menus that close on `mouseout` with no keyboard equivalent.\n- **Modal traps.** Modals that don't close on `Esc`, don't trap focus, don't restore focus on close.\n- **Custom date pickers without keyboard.** Date pickers are notoriously inaccessible; if you must build one, follow ARIA Authoring Practices.\n- **Drag-only reorder.** No keyboard alternative for sorting or reordering.\n- **Auto-advancing carousels.** Focus thrash on every slide change; no way for keyboard users to read content before it disappears.\n\n## Heuristics\n\n1. **Unplug your mouse.** Walk through every primary flow. Anything you can't do with keyboard alone is broken.\n2. **Tab around the page.** Focus indicators visible? Tab order logical? Any traps?\n3. **Try `Esc` everywhere.** Open every overlay; `Esc` should close it.\n4. **Test with `prefers-reduced-motion: reduce`.** macOS: System Settings → Accessibility → Display → Reduce Motion. Are critical animations still meaningful? Are decorative ones gone?\n5. **Voice-control test.** macOS Voice Control or Windows Speech Recognition. Say \"click [visible text].\" If the click works, label-in-name is correct.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-perceivable`** — what users see; complementary.\n- **`accessibility-understandable`** — what users comprehend.\n- **`accessibility-robust`** — markup that assistive tech can rely on.\n- **`fitts-law`** and **`fitts-law-touch-targets`** (interaction) — target size.\n- **`feedback-loop`** (interaction) — keyboard interactions need visible feedback too.\n","# Accessibility — Operable\n\nWCAG Principle 2: user-interface components and navigation must be operable.\n\nThe five sub-criteria, simplified:\n\n1. **Keyboard accessible** — everything that works with mouse must work with keyboard.\n2. **Enough time** — timing-out interactions are warned and extendable.\n3. **Seizures and physical reactions** — no flashing content; respect motion preferences.\n4. **Navigable** — users can find content and know where they are.\n5. **Input modalities** — touch and other input methods supported with adequate target size.\n\n## 1. Keyboard accessible\n\n### Every interactive element is reachable via Tab\n\nThe default `Tab` order follows DOM source order and only includes natively focusable elements: `\u003Ca href>`, `\u003Cbutton>`, `\u003Cinput>`, `\u003Cselect>`, `\u003Ctextarea>`, `\u003Csummary>`, `\u003Ciframe>`, plus elements with `tabindex=\"0\"`.\n\n- **Use semantic elements.** `\u003Cbutton>`, not `\u003Cdiv onclick>`.\n- **Use `tabindex=\"0\"`** to add custom interactive elements to tab order.\n- **Use `tabindex=\"-1\"`** to make an element programmatically focusable (e.g., for focus management) but not reachable via Tab.\n- **Avoid `tabindex` > 0.** Positive tabindex creates a custom tab order that's almost always worse than DOM order and bewilders screen readers.\n\n### Visible focus indicators\n\nThe user must see where focus is. Browsers provide default focus rings; never `outline: none` without a replacement.\n\n```css\n\u002F* Right: replace, don't remove *\u002F\n:focus { outline: none; }\n:focus-visible {\n  outline: 2px solid hsl(220 90% 50%);\n  outline-offset: 2px;\n  border-radius: 0.25rem;\n}\n\n\u002F* Wrong: removes the only signal a keyboard user has *\u002F\n*:focus { outline: none; }\n```\n\n`:focus-visible` (rather than `:focus`) shows the ring only when focus arrived via keyboard (or non-pointer means), not on every mouse click. This addresses the historical \"designers don't want focus rings on click\" concern without sacrificing keyboard accessibility.\n\n### Standard keys for standard interactions\n\nHonor user expectations:\n\n| Key | Behavior |\n|---|---|\n| `Tab` | Focus next; `Shift+Tab` for previous |\n| `Enter` \u002F `Space` | Activate button, follow link, toggle checkbox |\n| `Esc` | Close overlay (Dialog, Sheet, Popover, Combobox) |\n| Arrow keys | Move within radio groups, sliders, tabs, menus, comboboxes |\n| `Home` \u002F `End` | First \u002F last in a list or menu |\n| `Page Up` \u002F `Down` | Scroll a region |\n| `\u002F` | Often: focus search (de facto convention) |\n| `Cmd\u002FCtrl+K` | Often: open command palette (de facto convention) |\n\nARIA Authoring Practices Guide documents canonical keyboard interactions for every common pattern.\n\n### No keyboard traps\n\nA keyboard trap is a region where focus enters and cannot leave via keyboard alone. Common offenders:\n\n- Custom datepickers without arrow-key escape.\n- Embedded iframes with their own focus management that don't release.\n- Modal dialogs without `Esc` to close.\n\n**Test:** keyboard-only walkthrough. If you ever get stuck and have to mouse to escape, you have a trap.\n\n### Focus management for overlays\n\nWhen a modal opens:\n\n1. Move focus into the modal (typically the first focusable element, or a \"primary\" focus target).\n2. Trap focus inside until the modal closes.\n3. Restore focus to the trigger element when the modal closes.\n\n```js\n\u002F\u002F Pseudocode — in practice use a library that handles edge cases\nfunction openModal(modal, trigger) {\n  modal.dataset.previousFocus = trigger;\n  const focusables = modal.querySelectorAll('a, button, input, [tabindex=\"0\"]');\n  focusables[0]?.focus();\n  \u002F\u002F ... trap focus on Tab\u002FShift+Tab within `focusables` ...\n}\n\nfunction closeModal(modal) {\n  modal.previousFocus?.focus();\n}\n```\n\nMost accessible UI libraries (Radix UI, React Aria, headless component sets) do this automatically. Custom-built modals that skip focus management are inaccessible.\n\n### Skip links\n\n```html\n\u003Ca href=\"#main\" class=\"skip-link\">Skip to main content\u003C\u002Fa>\n\u003Cheader>\u003Cnav>... 50 nav items ...\u003C\u002Fnav>\u003C\u002Fheader>\n\u003Cmain id=\"main\">...\u003C\u002Fmain>\n\n\u003Cstyle>\n  .skip-link {\n    position: absolute;\n    left: -10000px;\n    top: auto;\n  }\n  .skip-link:focus {\n    position: fixed;\n    top: 8px; left: 8px;\n    padding: 8px 16px;\n    background: black; color: white;\n    z-index: 100;\n  }\n\u003C\u002Fstyle>\n```\n\nKeyboard users tab past nav to reach content quickly. Visible only on focus so it doesn't clutter sighted-mouse-user views.\n\n## 2. Enough time\n\n### Adjustable timing\n\nIf the system has timeouts (session expiry, captcha re-verify, time-limited form), users must be able to:\n\n- Turn it off, OR\n- Extend it, OR\n- Adjust it (across a wide range, ≥ 10× default).\n\nExceptions: real-time events (auctions), where time limit is essential.\n\n```html\n\u003C!-- Right: warn before timeout, allow extension -->\n\u003Cdialog open>\n  \u003Ch2>Session about to expire\u003C\u002Fh2>\n  \u003Cp>You have 60 seconds before your session ends.\u003C\u002Fp>\n  \u003Cbutton onclick=\"extendSession()\">Stay signed in\u003C\u002Fbutton>\n\u003C\u002Fdialog>\n```\n\n### No moving \u002F blinking content (without controls)\n\nContent that auto-moves, blinks, or scrolls for more than 5 seconds must be pause-able \u002F stop-able.\n\nThis includes carousels, animated banners, news tickers, autoplaying video.\n\n## 3. Seizures and physical reactions\n\n### Three flashes or below\n\nWCAG 2.3.1: don't have content that flashes more than 3 times per second. Photosensitive epilepsy can be triggered by flashing in the 3–55 Hz range.\n\nIn practice, this rules out: rapid strobe effects, blinking text (don't), high-contrast flashing animations.\n\n### Motion preferences\n\nWCAG 2.3.3: respect `prefers-reduced-motion`. Many users (vestibular disorders, migraine, motion sensitivity) have configured their OS to request reduced motion.\n\n```css\n@media (prefers-reduced-motion: reduce) {\n  *, *::before, *::after {\n    animation-duration: 0.01ms !important;\n    animation-iteration-count: 1 !important;\n    transition-duration: 0.01ms !important;\n    scroll-behavior: auto !important;\n  }\n}\n```\n\nFor specific motion that's *meaningful* (a state change indicator), allow it but make it briefer \u002F less dramatic in reduced-motion mode.\n\n## 4. Navigable\n\n### Page titles\n\nEvery page has a unique, descriptive `\u003Ctitle>`:\n\n```html\n\u003Ctitle>Settings — Notifications — Acme\u003C\u002Ftitle>\n```\n\nScreen reader users hear the title on page load; tab labels show it; browser history relies on it. Generic \"Acme\" titles for every page are useless.\n\n### Focus order matches reading order\n\nWhen a user tabs through a page, focus should follow the visual \u002F logical reading order. CSS-rearranged elements (Grid, Flex order) can break this — test.\n\n### Link purpose\n\nLinks should be understandable from their text alone (or from text + immediately-adjacent context). Screen reader users navigate by listing all links.\n\n```html\n\u003C!-- Wrong: \"click here\" tells the screen reader user nothing -->\n\u003Cp>To read more, \u003Ca href=\"\u002Fblog\u002Fpost\">click here\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003C!-- Right: link text describes destination -->\n\u003Cp>Read more in \u003Ca href=\"\u002Fblog\u002Fpost\">our annual review\u003C\u002Fa>.\u003C\u002Fp>\n```\n\n### Multiple ways to find content\n\nWCAG 2.4.5 (AA): provide more than one way to find a page (search, sitemap, navigation, related-content links). Helps users with cognitive impairments and users who navigate non-linearly.\n\n### Headings and labels are descriptive\n\n`\u003Ch2>Article\u003C\u002Fh2>` — useless. `\u003Ch2>Q4 sales recap\u003C\u002Fh2>` — useful.\n\n### Focus visible (covered above)\n\n### Location indicators\n\nUsers need to know where they are. Breadcrumbs, current-page highlighting in nav, page titles all serve this.\n\n```html\n\u003Cnav>\n  \u003Ca href=\"\u002Fdashboard\">Dashboard\u003C\u002Fa>\n  \u003Ca href=\"\u002Fprojects\" aria-current=\"page\">Projects\u003C\u002Fa>\n  \u003Ca href=\"\u002Fteam\">Team\u003C\u002Fa>\n\u003C\u002Fnav>\n```\n\n`aria-current=\"page\"` tells assistive tech which item is current; visual styling reinforces it.\n\n## 5. Input modalities\n\n### Target size (covered in `fitts-law-touch-targets`)\n\nWCAG 2.5.5 (AAA): targets ≥ 44×44 CSS px.\nWCAG 2.5.8 (AA, 2.2): targets ≥ 24×24 CSS px with adequate spacing.\n\n### Pointer gestures\n\nMulti-pointer or path-based gestures (pinch, swipe, drag) must have single-pointer alternatives:\n\n- Pinch-to-zoom → buttons \u002F keyboard for zoom in\u002Fout.\n- Swipe-to-delete → swipe + always-visible action button.\n- Drag-and-drop → keyboard reorder (arrows + spacebar).\n\n### Pointer cancellation\n\nThe user can cancel a pointer action by moving away before lifting. Don't trigger destructive actions on `mousedown`; trigger on `mouseup` or `click`.\n\n### Label in name\n\nThe accessible name must include any visible label text. Pattern:\n\n```html\n\u003C!-- Right: visible text matches accessible name -->\n\u003Cbutton>Save\u003C\u002Fbutton>\n\n\u003C!-- Wrong: aria-label overrides visible text, voice control breaks -->\n\u003Cbutton aria-label=\"Submit\">Save\u003C\u002Fbutton>\n\u003C!-- Voice user says \"click Save\" — fails because the accessible name is \"Submit\" -->\n```\n\n### Motion actuation\n\nFunctions triggered by device motion (shake, tilt) must have UI alternatives. Some users physically can't shake a device.\n\n## Worked example: an accessible dropdown menu\n\n```html\n\u003Cdiv class=\"dropdown\">\n  \u003Cbutton id=\"menu-button\"\n          aria-haspopup=\"true\"\n          aria-expanded=\"false\"\n          aria-controls=\"actions-menu\">\n    Actions\n  \u003C\u002Fbutton>\n  \u003Cul id=\"actions-menu\"\n      role=\"menu\"\n      hidden\n      aria-labelledby=\"menu-button\">\n    \u003Cli role=\"menuitem\" tabindex=\"-1\">Edit\u003C\u002Fli>\n    \u003Cli role=\"menuitem\" tabindex=\"-1\">Duplicate\u003C\u002Fli>\n    \u003Cli role=\"menuitem\" tabindex=\"-1\">Archive\u003C\u002Fli>\n    \u003Cli role=\"separator\">\u003C\u002Fli>\n    \u003Cli role=\"menuitem\" tabindex=\"-1\" class=\"destructive\">Delete\u003C\u002Fli>\n  \u003C\u002Ful>\n\u003C\u002Fdiv>\n```\n\nJavaScript to handle:\n\n- `Enter`\u002F`Space`\u002F`ArrowDown` on the button: open menu, focus first item.\n- `ArrowUp`\u002F`ArrowDown` in menu: move focus.\n- `Home`\u002F`End`: first \u002F last item.\n- `Esc`: close, return focus to button.\n- `Tab`: close, move to next focusable.\n- Click outside: close.\n\nPlus `aria-expanded` toggles between `\"true\"` and `\"false\"`.\n\nThis is verbose because menus genuinely have a lot of expected behavior. Use Radix, React Aria, or another library that implements WAI-ARIA Menu pattern correctly — don't roll your own.\n\n## Anti-patterns\n\n- **`outline: none` without a replacement.** Single largest accessibility crime in modern web design.\n- **`\u003Cdiv onclick>`.** Not focusable, not keyboard-operable, not announced as a button. Use `\u003Cbutton>`.\n- **Mouse-only menus.** Hover-revealed menus that close on `mouseout` with no keyboard equivalent.\n- **Modal traps.** Modals that don't close on `Esc`, don't trap focus, don't restore focus on close.\n- **Custom date pickers without keyboard.** Date pickers are notoriously inaccessible; if you must build one, follow ARIA Authoring Practices.\n- **Drag-only reorder.** No keyboard alternative for sorting or reordering.\n- **Auto-advancing carousels.** Focus thrash on every slide change; no way for keyboard users to read content before it disappears.\n\n## Heuristics\n\n1. **Unplug your mouse.** Walk through every primary flow. Anything you can't do with keyboard alone is broken.\n2. **Tab around the page.** Focus indicators visible? Tab order logical? Any traps?\n3. **Try `Esc` everywhere.** Open every overlay; `Esc` should close it.\n4. **Test with `prefers-reduced-motion: reduce`.** macOS: System Settings → Accessibility → Display → Reduce Motion. Are critical animations still meaningful? Are decorative ones gone?\n5. **Voice-control test.** macOS Voice Control or Windows Speech Recognition. Say \"click [visible text].\" If the click works, label-in-name is correct.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-perceivable`** — what users see; complementary.\n- **`accessibility-understandable`** — what users comprehend.\n- **`accessibility-robust`** — markup that assistive tech can rely on.\n- **`fitts-law`** and **`fitts-law-touch-targets`** (interaction) — target size.\n- **`feedback-loop`** (interaction) — keyboard interactions need visible feedback too.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-operable",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-operable",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-operable",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-operable","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-operable\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Foperable-deep-dive.md","REFERENCE","参考文档",5114,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-operable\u002Freferences\u002Foperable-deep-dive.md",[76,86,94,102,110,118],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":80,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"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":80,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":85},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":85},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":85},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":85},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]