[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWHEGCMW9B7B4ZA61R72QZ":3,"skill-same:01M6JWHEGCMW9B7B4ZA61R72QZ":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},"01M6JWHEGCMW9B7B4ZA61R72QZ","accessibility-robust",null,"Use this skill when the question is whether assistive technologies — screen readers, voice control, switch devices, refreshable braille displays — can reliably interpret your UI. Trigger when picking between semantic HTML and a custom-built component, when reaching for ARIA, when designing live regions for dynamic content (toasts, validation, search results), or when reviewing a UI built largely from `\u003Cdiv>` elements. Covers WCAG Principle 4 (Robust). 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-robust\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"accessibility robust","accessibility","switch","when","custom","for","you","screen","trigger","braille","live","voice control","aria","html","use","read","question","devices","ui","search","component","2026-11-10 10:12:30",false,"---\nname: accessibility-robust\ndescription: 'Use this skill when the question is whether assistive technologies — screen readers, voice control, switch devices, refreshable braille displays — can reliably interpret your UI. Trigger when picking between semantic HTML and a custom-built component, when reaching for ARIA, when designing live regions for dynamic content (toasts, validation, search results), or when reviewing a UI built largely from `\u003Cdiv>` elements. Covers WCAG Principle 4 (Robust). Sub-aspect of `accessibility`; read that first if you haven''t already.'\n---\n\n# Accessibility — Robust\n\nWCAG Principle 4: content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.\n\nThe two sub-criteria, simplified:\n\n1. **Compatible** — markup is parsed correctly; name, role, and value are programmatically determinable for every UI component.\n2. **Status messages** — programmatically-conveyed status updates without focus shifts.\n\nRobustness is the layer most often broken by frameworks that abstract away HTML semantics. A `\u003Cdiv>`-based UI may be visually identical to a semantic one and entirely opaque to assistive tech.\n\n## 1. Compatible\n\n### Semantic HTML first\n\nUse the right HTML element for the job. Browsers and assistive tech understand semantic elements without further annotation.\n\n| Use this… | …not this |\n|---|---|\n| `\u003Cbutton>` | `\u003Cdiv>` with click handler |\n| `\u003Ca href>` | `\u003Cspan>` with click handler |\n| `\u003Cinput type=\"checkbox\">` | `\u003Cdiv>` with custom toggle |\n| `\u003Cnav>` | `\u003Cdiv class=\"nav\">` |\n| `\u003Cmain>` | `\u003Cdiv class=\"main\">` |\n| `\u003Cform>` | `\u003Cdiv>` with submit button |\n| `\u003Clabel for=\"id\">` | `\u003Cdiv>` next to an input |\n| `\u003Ctable>` for tabular data | nested divs styled as a grid |\n\nThe reason isn't aesthetic; semantic elements come with built-in:\n\n- Keyboard handling (`\u003Cbutton>` activates on Enter\u002FSpace).\n- Focus management (`\u003Ca href>` is in tab order).\n- Accessibility tree role (`\u003Cnav>` is announced as \"navigation landmark\").\n- Default styling that can be overridden but indicates affordance.\n- Form submission, validation, and serialization.\n\nA `\u003Cdiv role=\"button\" tabindex=\"0\" onclick onKeyDown>` is *almost* a button — and you've rebuilt 80% of what `\u003Cbutton>` provides for free, often imperfectly.\n\n### Name, Role, Value\n\nEvery interactive component must have:\n\n- **Name** — what is it? (\"Save,\" \"Email field,\" \"Open menu\")\n- **Role** — what kind of thing is it? (\"button,\" \"textbox,\" \"menu\")\n- **Value** — what's its current state? (\"checked,\" \"expanded,\" \"disabled,\" current text)\n\nNative HTML elements provide all three for free. For custom components, you provide them via ARIA.\n\n```html\n\u003C!-- Native: name from text, role from \u003Cbutton>, value from disabled state -->\n\u003Cbutton disabled>Save\u003C\u002Fbutton>\n\n\u003C!-- Custom: must declare all three -->\n\u003Cdiv role=\"button\"\n     tabindex=\"0\"\n     aria-disabled=\"true\">\n  Save\n\u003C\u002Fdiv>\n```\n\n### When to use ARIA\n\nThe first rule of ARIA: don't use ARIA. The second rule: don't use ARIA when a native element will do. The third rule: when you must use ARIA, use it correctly.\n\n**Use ARIA when:**\n\n- Building a custom component for which no native element exists (combobox, tablist, treegrid, slider) — use the appropriate WAI-ARIA pattern.\n- Adding state to a component that has no native attribute (`aria-expanded`, `aria-current`, `aria-pressed`, `aria-selected`).\n- Providing an accessible name when no visible label exists (`aria-label`, `aria-labelledby`).\n- Associating descriptions or errors with controls (`aria-describedby`).\n- Marking dynamic content for announcement (`aria-live`).\n\n**Don't use ARIA to:**\n\n- Reinvent native semantics (`role=\"button\"` on `\u003Cbutton>`).\n- Override semantics that work (`role=\"presentation\"` on a `\u003Ctable>` of tabular data).\n- \"Fix\" inaccessible custom components without also adding keyboard support and state management.\n\n### ARIA roles, properties, states\n\nA few of the most-used:\n\n| Attribute | Purpose | Example |\n|---|---|---|\n| `role` | Declare what kind of widget | `role=\"dialog\"` |\n| `aria-label` | Accessible name when no visible label | `\u003Cbutton aria-label=\"Close\">×\u003C\u002Fbutton>` |\n| `aria-labelledby` | Accessible name from another element | `\u003Cdialog aria-labelledby=\"title\">` |\n| `aria-describedby` | Description \u002F error \u002F hint | `\u003Cinput aria-describedby=\"hint\">` |\n| `aria-expanded` | Disclosure state | `\u003Cbutton aria-expanded=\"false\">` |\n| `aria-current` | Current item in a set | `\u003Ca aria-current=\"page\">` |\n| `aria-pressed` | Toggle button state | `\u003Cbutton aria-pressed=\"true\">` |\n| `aria-checked` | Custom checkbox\u002Fradio state | `\u003Cdiv role=\"checkbox\" aria-checked=\"true\">` |\n| `aria-selected` | Selected item in a listbox | `\u003Cdiv role=\"option\" aria-selected=\"true\">` |\n| `aria-disabled` | Disabled (when `disabled` attr unavailable) | `\u003Cdiv aria-disabled=\"true\">` |\n| `aria-invalid` | Error state | `\u003Cinput aria-invalid=\"true\">` |\n| `aria-required` | Required field | `\u003Cinput aria-required=\"true\">` |\n| `aria-hidden` | Hide from accessibility tree | `\u003Csvg aria-hidden=\"true\">` |\n| `aria-live` | Announce changes | `\u003Cdiv aria-live=\"polite\">` |\n| `role=\"alert\"` | Important announcement | `\u003Cdiv role=\"alert\">` |\n\nThe WAI-ARIA Authoring Practices Guide documents complete patterns for: combobox, dialog, disclosure, feed, grid, listbox, menu, menubar, radiogroup, slider, tablist, treeview, and more. Reach for these patterns rather than inventing.\n\n### Don't break native semantics\n\nA common mistake: applying ARIA roles that *conflict* with the underlying element.\n\n```html\n\u003C!-- Wrong: \u003Ca href> is already a link; role=\"button\" overrides -->\n\u003Ca href=\"\u002Fsave\" role=\"button\">Save\u003C\u002Fa>\n\n\u003C!-- Wrong: \u003Cul> already has list semantics; role=\"navigation\" doesn't help -->\n\u003Cul role=\"navigation\">...\u003C\u002Ful>\n\n\u003C!-- Wrong: \u003Ctable> for tabular data with role=\"presentation\" strips semantics -->\n\u003Ctable role=\"presentation\">...\u003C\u002Ftable>\n```\n\nIf you must override semantics (rare), you almost always have the wrong base element.\n\n### Validate your HTML\n\nInvalid HTML can cascade in unpredictable ways through accessibility tree construction. Validate occasionally with the W3C HTML Validator.\n\nCommon offenders:\n\n- Duplicate IDs (breaks `aria-labelledby` and `aria-describedby`).\n- Nested interactive elements (`\u003Cbutton>` inside `\u003Ca>`, `\u003Ca>` inside `\u003Cbutton>`).\n- `\u003Cbutton>` inside `\u003Cbutton>`.\n- Form controls not associated with `\u003Clabel>`.\n\n## 2. Status messages\n\nDynamic content updates that don't shift focus need to be announced to screen readers via live regions.\n\n### Live regions\n\n```html\n\u003C!-- Polite: announce when convenient (after current speech) -->\n\u003Cdiv aria-live=\"polite\" id=\"search-results-status\">\u003C\u002Fdiv>\n\n\u003C!-- Assertive: interrupt; for critical messages only -->\n\u003Cdiv aria-live=\"assertive\" id=\"error-status\">\u003C\u002Fdiv>\n```\n\nWhen you populate the live region, the screen reader reads the new content. The region must:\n\n- Be present in the DOM *before* content is added (live regions don't announce content present at page load).\n- Have only the new message inside it, replacing previous content.\n- Be visible to assistive tech (don't `display: none`; use `sr-only` if you don't want it visible).\n\n### `role=\"status\"` and `role=\"alert\"`\n\nConvenience roles with built-in `aria-live` settings:\n\n- `role=\"status\"` ≈ `aria-live=\"polite\"`. For non-critical updates (\"Saved,\" \"Loaded 24 results\").\n- `role=\"alert\"` ≈ `aria-live=\"assertive\"` plus `aria-atomic=\"true\"`. For urgent updates (\"Connection lost,\" \"Form has 3 errors\").\n\n```html\n\u003C!-- Toast notification (status) -->\n\u003Cdiv role=\"status\">Changes saved\u003C\u002Fdiv>\n\n\u003C!-- Form error summary (alert) -->\n\u003Cdiv role=\"alert\">\n  Please fix the following: Email is invalid; Password is too short.\n\u003C\u002Fdiv>\n```\n\nUse `role=\"alert\"` sparingly — it interrupts whatever the screen reader is doing. Reserve for genuine emergencies.\n\n### Common live-region patterns\n\n- **Toast notifications** — `role=\"status\"` for success, info, warning; `role=\"alert\"` for error.\n- **Search results count** — `\u003Cdiv role=\"status\">Showing 24 results\u003C\u002Fdiv>` updates as the user filters.\n- **Form validation summary** — after a failed submit, populate `\u003Cdiv role=\"alert\">` with the error count and let screen reader read it.\n- **Auto-saving indicator** — `\u003Cdiv role=\"status\">Saving... Saved at 3:42 PM\u003C\u002Fdiv>` updates during background saves.\n- **Real-time data updates** — chat messages, stock prices: `aria-live=\"polite\"` so the user hears them when convenient.\n\n### Don't overdo announcements\n\nEvery announcement steals attention. Frequent live-region updates make the UI noisy for screen reader users. Rules of thumb:\n\n- Don't announce hover state changes.\n- Don't announce loading spinners (unless the load is unusually long).\n- Don't announce purely cosmetic transitions.\n- Aggregate where possible: instead of \"Filter applied,\" \"24 results loaded,\" \"Filter applied,\" \"12 results loaded\" with each filter change, debounce and announce only the final state.\n\n### `aria-atomic` and `aria-relevant`\n\nFine-tuning live region behavior:\n\n- `aria-atomic=\"true\"` — read the entire region content when any part changes (default for `role=\"alert\"`; useful for counts that should always be read in context: \"24 results\" changing to \"12 results\").\n- `aria-relevant` — control which mutation types announce (default is `additions text`). Rarely needed.\n\n## Worked examples\n\n### Example 1: a custom slider built right\n\n```html\n\u003Clabel id=\"volume-label\">Volume: \u003Cspan id=\"volume-value\">50\u003C\u002Fspan>%\u003C\u002Flabel>\n\u003Cdiv role=\"slider\"\n     aria-labelledby=\"volume-label\"\n     aria-valuemin=\"0\"\n     aria-valuemax=\"100\"\n     aria-valuenow=\"50\"\n     tabindex=\"0\"\n     id=\"volume-slider\"\n     class=\"slider-track\">\n  \u003Cdiv class=\"slider-thumb\" style=\"left: 50%;\">\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nPlus JavaScript:\n\n- `ArrowLeft`\u002F`ArrowRight` and `Home`\u002F`End` adjust value.\n- On adjustment, update `aria-valuenow` *and* the visible text (`#volume-value`).\n\nThe native `\u003Cinput type=\"range\">` does all of this automatically — strongly prefer that. Custom sliders are justified only when range can't meet your needs (multi-handle range, custom geometry, color picker).\n\n### Example 2: a search results announcement\n\n```html\n\u003Cform>\n  \u003Clabel for=\"search\">Search\u003C\u002Flabel>\n  \u003Cinput id=\"search\" oninput=\"runSearch(this.value)\" \u002F>\n\u003C\u002Fform>\n\n\u003Cdiv id=\"results\">…rendered results…\u003C\u002Fdiv>\n\u003Cdiv id=\"results-status\" class=\"sr-only\" role=\"status\">\u003C\u002Fdiv>\n\n\u003Cscript>\n  function runSearch(q) {\n    const results = doSearch(q);\n    renderResults(results);\n    document.getElementById('results-status').textContent =\n      `${results.length} results for \"${q}\"`;\n  }\n\u003C\u002Fscript>\n```\n\nSighted users see results below the input; screen reader users hear \"24 results for 'invoice'\" without focus moving.\n\n### Example 3: a toast that announces\n\n```html\n\u003Cdiv id=\"toast-region\" aria-live=\"polite\" aria-atomic=\"true\" class=\"sr-only\">\u003C\u002Fdiv>\n\n\u003Cscript>\n  function showToast(message) {\n    const region = document.getElementById('toast-region');\n    region.textContent = message;\n    showVisualToast(message); \u002F\u002F separate visible UI\n    setTimeout(() => region.textContent = '', 5000);\n  }\n\u003C\u002Fscript>\n```\n\nThe visible toast is rendered however your design library does it. The hidden live region is what assistive tech uses.\n\n## Anti-patterns\n\n- **`\u003Cdiv>` for everything.** A UI built without semantic elements is opaque to assistive tech and requires comprehensive ARIA to recover.\n- **`role=\"button\"` on a `\u003Cbutton>`.** Redundant; sometimes interferes with native behavior.\n- **`aria-label` that contradicts visible text.** Voice control breaks; user says \"click [visible text]\" and nothing happens.\n- **Live regions added at announcement time.** `\u003Cdiv aria-live=\"polite\">` must be in the DOM at page load to be reliably observed; adding it dynamically often misses the announcement.\n- **Aria-live on too much content.** Page-wide `aria-live` regions are constantly chattering. Scope to just the announcement element.\n- **Custom dropdowns missing keyboard.** ARIA roles applied to a div but no `Tab`, `Esc`, or arrow-key handlers. The screen reader hears \"menu\" but the user can't operate it.\n- **`role=\"presentation\"` on tables of data.** Strips the semantics that make the table navigable. Reserve for genuinely-decorative table-shaped layouts.\n\n## Heuristics\n\n1. **The \"is there a native element for this?\" check.** Before reaching for ARIA, ask if HTML provides what you need. Almost always.\n2. **The accessibility tree audit.** Chrome DevTools → Accessibility tab. Inspect any custom component. Does it have a name, role, and (where applicable) value? If \"name: empty\" or \"role: generic,\" the component is invisible to assistive tech.\n3. **The screen-reader walkthrough.** Open VoiceOver \u002F NVDA \u002F TalkBack and walk a critical flow. Listen for: unlabeled controls, components with no role, changes that aren't announced, \"blank\" or \"press button to\" without context.\n4. **The HTML validator.** Run your most-complex pages through validator.w3.org. Duplicate IDs, nested interactive elements, and missing labels often surface here first.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-perceivable`**, **`accessibility-operable`**, **`accessibility-understandable`** — siblings.\n- **`feedback-loop`** (interaction) — live regions are accessibility's version of feedback.\n- **`structural-forms`** (process) — semantic HTML is the structural-forms answer for accessibility.\n- **`affordance`** (interaction) — semantic elements come with default affordances.\n","# Accessibility — Robust\n\nWCAG Principle 4: content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.\n\nThe two sub-criteria, simplified:\n\n1. **Compatible** — markup is parsed correctly; name, role, and value are programmatically determinable for every UI component.\n2. **Status messages** — programmatically-conveyed status updates without focus shifts.\n\nRobustness is the layer most often broken by frameworks that abstract away HTML semantics. A `\u003Cdiv>`-based UI may be visually identical to a semantic one and entirely opaque to assistive tech.\n\n## 1. Compatible\n\n### Semantic HTML first\n\nUse the right HTML element for the job. Browsers and assistive tech understand semantic elements without further annotation.\n\n| Use this… | …not this |\n|---|---|\n| `\u003Cbutton>` | `\u003Cdiv>` with click handler |\n| `\u003Ca href>` | `\u003Cspan>` with click handler |\n| `\u003Cinput type=\"checkbox\">` | `\u003Cdiv>` with custom toggle |\n| `\u003Cnav>` | `\u003Cdiv class=\"nav\">` |\n| `\u003Cmain>` | `\u003Cdiv class=\"main\">` |\n| `\u003Cform>` | `\u003Cdiv>` with submit button |\n| `\u003Clabel for=\"id\">` | `\u003Cdiv>` next to an input |\n| `\u003Ctable>` for tabular data | nested divs styled as a grid |\n\nThe reason isn't aesthetic; semantic elements come with built-in:\n\n- Keyboard handling (`\u003Cbutton>` activates on Enter\u002FSpace).\n- Focus management (`\u003Ca href>` is in tab order).\n- Accessibility tree role (`\u003Cnav>` is announced as \"navigation landmark\").\n- Default styling that can be overridden but indicates affordance.\n- Form submission, validation, and serialization.\n\nA `\u003Cdiv role=\"button\" tabindex=\"0\" onclick onKeyDown>` is *almost* a button — and you've rebuilt 80% of what `\u003Cbutton>` provides for free, often imperfectly.\n\n### Name, Role, Value\n\nEvery interactive component must have:\n\n- **Name** — what is it? (\"Save,\" \"Email field,\" \"Open menu\")\n- **Role** — what kind of thing is it? (\"button,\" \"textbox,\" \"menu\")\n- **Value** — what's its current state? (\"checked,\" \"expanded,\" \"disabled,\" current text)\n\nNative HTML elements provide all three for free. For custom components, you provide them via ARIA.\n\n```html\n\u003C!-- Native: name from text, role from \u003Cbutton>, value from disabled state -->\n\u003Cbutton disabled>Save\u003C\u002Fbutton>\n\n\u003C!-- Custom: must declare all three -->\n\u003Cdiv role=\"button\"\n     tabindex=\"0\"\n     aria-disabled=\"true\">\n  Save\n\u003C\u002Fdiv>\n```\n\n### When to use ARIA\n\nThe first rule of ARIA: don't use ARIA. The second rule: don't use ARIA when a native element will do. The third rule: when you must use ARIA, use it correctly.\n\n**Use ARIA when:**\n\n- Building a custom component for which no native element exists (combobox, tablist, treegrid, slider) — use the appropriate WAI-ARIA pattern.\n- Adding state to a component that has no native attribute (`aria-expanded`, `aria-current`, `aria-pressed`, `aria-selected`).\n- Providing an accessible name when no visible label exists (`aria-label`, `aria-labelledby`).\n- Associating descriptions or errors with controls (`aria-describedby`).\n- Marking dynamic content for announcement (`aria-live`).\n\n**Don't use ARIA to:**\n\n- Reinvent native semantics (`role=\"button\"` on `\u003Cbutton>`).\n- Override semantics that work (`role=\"presentation\"` on a `\u003Ctable>` of tabular data).\n- \"Fix\" inaccessible custom components without also adding keyboard support and state management.\n\n### ARIA roles, properties, states\n\nA few of the most-used:\n\n| Attribute | Purpose | Example |\n|---|---|---|\n| `role` | Declare what kind of widget | `role=\"dialog\"` |\n| `aria-label` | Accessible name when no visible label | `\u003Cbutton aria-label=\"Close\">×\u003C\u002Fbutton>` |\n| `aria-labelledby` | Accessible name from another element | `\u003Cdialog aria-labelledby=\"title\">` |\n| `aria-describedby` | Description \u002F error \u002F hint | `\u003Cinput aria-describedby=\"hint\">` |\n| `aria-expanded` | Disclosure state | `\u003Cbutton aria-expanded=\"false\">` |\n| `aria-current` | Current item in a set | `\u003Ca aria-current=\"page\">` |\n| `aria-pressed` | Toggle button state | `\u003Cbutton aria-pressed=\"true\">` |\n| `aria-checked` | Custom checkbox\u002Fradio state | `\u003Cdiv role=\"checkbox\" aria-checked=\"true\">` |\n| `aria-selected` | Selected item in a listbox | `\u003Cdiv role=\"option\" aria-selected=\"true\">` |\n| `aria-disabled` | Disabled (when `disabled` attr unavailable) | `\u003Cdiv aria-disabled=\"true\">` |\n| `aria-invalid` | Error state | `\u003Cinput aria-invalid=\"true\">` |\n| `aria-required` | Required field | `\u003Cinput aria-required=\"true\">` |\n| `aria-hidden` | Hide from accessibility tree | `\u003Csvg aria-hidden=\"true\">` |\n| `aria-live` | Announce changes | `\u003Cdiv aria-live=\"polite\">` |\n| `role=\"alert\"` | Important announcement | `\u003Cdiv role=\"alert\">` |\n\nThe WAI-ARIA Authoring Practices Guide documents complete patterns for: combobox, dialog, disclosure, feed, grid, listbox, menu, menubar, radiogroup, slider, tablist, treeview, and more. Reach for these patterns rather than inventing.\n\n### Don't break native semantics\n\nA common mistake: applying ARIA roles that *conflict* with the underlying element.\n\n```html\n\u003C!-- Wrong: \u003Ca href> is already a link; role=\"button\" overrides -->\n\u003Ca href=\"\u002Fsave\" role=\"button\">Save\u003C\u002Fa>\n\n\u003C!-- Wrong: \u003Cul> already has list semantics; role=\"navigation\" doesn't help -->\n\u003Cul role=\"navigation\">...\u003C\u002Ful>\n\n\u003C!-- Wrong: \u003Ctable> for tabular data with role=\"presentation\" strips semantics -->\n\u003Ctable role=\"presentation\">...\u003C\u002Ftable>\n```\n\nIf you must override semantics (rare), you almost always have the wrong base element.\n\n### Validate your HTML\n\nInvalid HTML can cascade in unpredictable ways through accessibility tree construction. Validate occasionally with the W3C HTML Validator.\n\nCommon offenders:\n\n- Duplicate IDs (breaks `aria-labelledby` and `aria-describedby`).\n- Nested interactive elements (`\u003Cbutton>` inside `\u003Ca>`, `\u003Ca>` inside `\u003Cbutton>`).\n- `\u003Cbutton>` inside `\u003Cbutton>`.\n- Form controls not associated with `\u003Clabel>`.\n\n## 2. Status messages\n\nDynamic content updates that don't shift focus need to be announced to screen readers via live regions.\n\n### Live regions\n\n```html\n\u003C!-- Polite: announce when convenient (after current speech) -->\n\u003Cdiv aria-live=\"polite\" id=\"search-results-status\">\u003C\u002Fdiv>\n\n\u003C!-- Assertive: interrupt; for critical messages only -->\n\u003Cdiv aria-live=\"assertive\" id=\"error-status\">\u003C\u002Fdiv>\n```\n\nWhen you populate the live region, the screen reader reads the new content. The region must:\n\n- Be present in the DOM *before* content is added (live regions don't announce content present at page load).\n- Have only the new message inside it, replacing previous content.\n- Be visible to assistive tech (don't `display: none`; use `sr-only` if you don't want it visible).\n\n### `role=\"status\"` and `role=\"alert\"`\n\nConvenience roles with built-in `aria-live` settings:\n\n- `role=\"status\"` ≈ `aria-live=\"polite\"`. For non-critical updates (\"Saved,\" \"Loaded 24 results\").\n- `role=\"alert\"` ≈ `aria-live=\"assertive\"` plus `aria-atomic=\"true\"`. For urgent updates (\"Connection lost,\" \"Form has 3 errors\").\n\n```html\n\u003C!-- Toast notification (status) -->\n\u003Cdiv role=\"status\">Changes saved\u003C\u002Fdiv>\n\n\u003C!-- Form error summary (alert) -->\n\u003Cdiv role=\"alert\">\n  Please fix the following: Email is invalid; Password is too short.\n\u003C\u002Fdiv>\n```\n\nUse `role=\"alert\"` sparingly — it interrupts whatever the screen reader is doing. Reserve for genuine emergencies.\n\n### Common live-region patterns\n\n- **Toast notifications** — `role=\"status\"` for success, info, warning; `role=\"alert\"` for error.\n- **Search results count** — `\u003Cdiv role=\"status\">Showing 24 results\u003C\u002Fdiv>` updates as the user filters.\n- **Form validation summary** — after a failed submit, populate `\u003Cdiv role=\"alert\">` with the error count and let screen reader read it.\n- **Auto-saving indicator** — `\u003Cdiv role=\"status\">Saving... Saved at 3:42 PM\u003C\u002Fdiv>` updates during background saves.\n- **Real-time data updates** — chat messages, stock prices: `aria-live=\"polite\"` so the user hears them when convenient.\n\n### Don't overdo announcements\n\nEvery announcement steals attention. Frequent live-region updates make the UI noisy for screen reader users. Rules of thumb:\n\n- Don't announce hover state changes.\n- Don't announce loading spinners (unless the load is unusually long).\n- Don't announce purely cosmetic transitions.\n- Aggregate where possible: instead of \"Filter applied,\" \"24 results loaded,\" \"Filter applied,\" \"12 results loaded\" with each filter change, debounce and announce only the final state.\n\n### `aria-atomic` and `aria-relevant`\n\nFine-tuning live region behavior:\n\n- `aria-atomic=\"true\"` — read the entire region content when any part changes (default for `role=\"alert\"`; useful for counts that should always be read in context: \"24 results\" changing to \"12 results\").\n- `aria-relevant` — control which mutation types announce (default is `additions text`). Rarely needed.\n\n## Worked examples\n\n### Example 1: a custom slider built right\n\n```html\n\u003Clabel id=\"volume-label\">Volume: \u003Cspan id=\"volume-value\">50\u003C\u002Fspan>%\u003C\u002Flabel>\n\u003Cdiv role=\"slider\"\n     aria-labelledby=\"volume-label\"\n     aria-valuemin=\"0\"\n     aria-valuemax=\"100\"\n     aria-valuenow=\"50\"\n     tabindex=\"0\"\n     id=\"volume-slider\"\n     class=\"slider-track\">\n  \u003Cdiv class=\"slider-thumb\" style=\"left: 50%;\">\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nPlus JavaScript:\n\n- `ArrowLeft`\u002F`ArrowRight` and `Home`\u002F`End` adjust value.\n- On adjustment, update `aria-valuenow` *and* the visible text (`#volume-value`).\n\nThe native `\u003Cinput type=\"range\">` does all of this automatically — strongly prefer that. Custom sliders are justified only when range can't meet your needs (multi-handle range, custom geometry, color picker).\n\n### Example 2: a search results announcement\n\n```html\n\u003Cform>\n  \u003Clabel for=\"search\">Search\u003C\u002Flabel>\n  \u003Cinput id=\"search\" oninput=\"runSearch(this.value)\" \u002F>\n\u003C\u002Fform>\n\n\u003Cdiv id=\"results\">…rendered results…\u003C\u002Fdiv>\n\u003Cdiv id=\"results-status\" class=\"sr-only\" role=\"status\">\u003C\u002Fdiv>\n\n\u003Cscript>\n  function runSearch(q) {\n    const results = doSearch(q);\n    renderResults(results);\n    document.getElementById('results-status').textContent =\n      `${results.length} results for \"${q}\"`;\n  }\n\u003C\u002Fscript>\n```\n\nSighted users see results below the input; screen reader users hear \"24 results for 'invoice'\" without focus moving.\n\n### Example 3: a toast that announces\n\n```html\n\u003Cdiv id=\"toast-region\" aria-live=\"polite\" aria-atomic=\"true\" class=\"sr-only\">\u003C\u002Fdiv>\n\n\u003Cscript>\n  function showToast(message) {\n    const region = document.getElementById('toast-region');\n    region.textContent = message;\n    showVisualToast(message); \u002F\u002F separate visible UI\n    setTimeout(() => region.textContent = '', 5000);\n  }\n\u003C\u002Fscript>\n```\n\nThe visible toast is rendered however your design library does it. The hidden live region is what assistive tech uses.\n\n## Anti-patterns\n\n- **`\u003Cdiv>` for everything.** A UI built without semantic elements is opaque to assistive tech and requires comprehensive ARIA to recover.\n- **`role=\"button\"` on a `\u003Cbutton>`.** Redundant; sometimes interferes with native behavior.\n- **`aria-label` that contradicts visible text.** Voice control breaks; user says \"click [visible text]\" and nothing happens.\n- **Live regions added at announcement time.** `\u003Cdiv aria-live=\"polite\">` must be in the DOM at page load to be reliably observed; adding it dynamically often misses the announcement.\n- **Aria-live on too much content.** Page-wide `aria-live` regions are constantly chattering. Scope to just the announcement element.\n- **Custom dropdowns missing keyboard.** ARIA roles applied to a div but no `Tab`, `Esc`, or arrow-key handlers. The screen reader hears \"menu\" but the user can't operate it.\n- **`role=\"presentation\"` on tables of data.** Strips the semantics that make the table navigable. Reserve for genuinely-decorative table-shaped layouts.\n\n## Heuristics\n\n1. **The \"is there a native element for this?\" check.** Before reaching for ARIA, ask if HTML provides what you need. Almost always.\n2. **The accessibility tree audit.** Chrome DevTools → Accessibility tab. Inspect any custom component. Does it have a name, role, and (where applicable) value? If \"name: empty\" or \"role: generic,\" the component is invisible to assistive tech.\n3. **The screen-reader walkthrough.** Open VoiceOver \u002F NVDA \u002F TalkBack and walk a critical flow. Listen for: unlabeled controls, components with no role, changes that aren't announced, \"blank\" or \"press button to\" without context.\n4. **The HTML validator.** Run your most-complex pages through validator.w3.org. Duplicate IDs, nested interactive elements, and missing labels often surface here first.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-perceivable`**, **`accessibility-operable`**, **`accessibility-understandable`** — siblings.\n- **`feedback-loop`** (interaction) — live regions are accessibility's version of feedback.\n- **`structural-forms`** (process) — semantic HTML is the structural-forms answer for accessibility.\n- **`affordance`** (interaction) — semantic elements come with default affordances.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-robust",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-robust",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-robust",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-robust","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-robust\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Frobust-deep-dive.md","REFERENCE","参考文档",6377,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-robust\u002Freferences\u002Frobust-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",[],[]]