[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWHKV415FXM9R86TSMY8F4":3,"skill-same:01M6JWHKV415FXM9R86TSMY8F4":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},"01M6JWHKV415FXM9R86TSMY8F4","accessibility-understandable",null,"Use this skill when the question is whether users can *understand* the UI — predict its behavior, recover from errors, comprehend its labels and copy. Trigger when writing form labels and error messages, when designing flows with surprising state changes, when picking microcopy for the destructive moments, or when reviewing a UI that \"works correctly but confuses people.\" Covers WCAG Principle 3 (Understandable). 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-understandable\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 understandable","when","writing","labels","for","errors","you","moments","flows","microcopy","error","form","people","trigger","but","read","question","messages","error messages","ui","2026-11-10 10:12:30",false,"---\nname: accessibility-understandable\ndescription: 'Use this skill when the question is whether users can *understand* the UI — predict its behavior, recover from errors, comprehend its labels and copy. Trigger when writing form labels and error messages, when designing flows with surprising state changes, when picking microcopy for the destructive moments, or when reviewing a UI that \"works correctly but confuses people.\" Covers WCAG Principle 3 (Understandable). Sub-aspect of `accessibility`; read that first if you haven''t already.'\n---\n\n# Accessibility — Understandable\n\nWCAG Principle 3: information and the operation of the user interface must be understandable.\n\nThe three sub-criteria, simplified:\n\n1. **Readable** — language is identified, jargon is explained, abbreviations are expanded.\n2. **Predictable** — the UI behaves consistently and changes context only when the user expects.\n3. **Input assistance** — labels, instructions, error messages, and prevention of mistakes.\n\nThis sub-principle is where accessibility most overlaps with general usability — but the consequences fall hardest on users with cognitive impairments, learning disabilities, low literacy, or unfamiliarity with the language.\n\n## 1. Readable\n\n### Language identified\n\nSet the document language so screen readers pronounce correctly:\n\n```html\n\u003Chtml lang=\"en\">\n```\n\nFor mixed-language content, mark the exception:\n\n```html\n\u003Cp>The French word for \"dog\" is \u003Cspan lang=\"fr\">chien\u003C\u002Fspan>.\u003C\u002Fp>\n```\n\nA screen reader switches voice\u002Fpronunciation for the marked span.\n\n### Plain language\n\nWrite at a reading level appropriate to your audience. For consumer products, that's typically grade 8 or below. Tools (Hemingway Editor, Readable, Microsoft Word's readability stats) measure this.\n\nPractices that improve readability:\n\n- Short sentences (\u003C25 words).\n- Active voice (\"Click Save\" not \"Save can be clicked\").\n- Familiar words (use \"buy\" not \"procure\").\n- One idea per sentence.\n- Paragraphs ≤ 5 sentences.\n\n### Jargon and abbreviations\n\nIf you must use jargon or abbreviations, expand them on first use:\n\n```html\n\u003Cp>\n  Single sign-on (\u003Cabbr title=\"Single Sign-On\">SSO\u003C\u002Fabbr>) lets your team\n  use one login across all tools.\n\u003C\u002Fp>\n```\n\nScreen readers can announce the expansion via `\u003Cabbr title>`. Sighted users see the expansion on hover.\n\nFor specialized terms, link to a definition or glossary the first time.\n\n### Pronunciation (rare but worth knowing)\n\nFor content where pronunciation determines meaning (poetry, languages, certain proper nouns), provide pronunciation hints. Most apps don't need this; mention it for completeness.\n\n## 2. Predictable\n\n### Behavior on focus and input\n\nWCAG 3.2.1 and 3.2.2: changing the value of an input or moving focus to an element should NOT trigger an unexpected context change.\n\nSpecifically:\n\n- A `\u003Cselect>` should not auto-submit a form when a value changes.\n- Focusing an input should not open a popup or navigate.\n- Typing into a search field should not navigate to a result page on every keystroke.\n\nIf a context change *is* the intended behavior (typeahead search, live filter), make it expected: label the field as \"Search (results filter as you type),\" show results below the input, don't yank focus.\n\n```html\n\u003C!-- Wrong: select auto-submits on change -->\n\u003Cselect onchange=\"this.form.submit()\">\n  \u003Coption>Country A\u003C\u002Foption>\n  \u003Coption>Country B\u003C\u002Foption>\n\u003C\u002Fselect>\n\n\u003C!-- Right: select waits for explicit submit -->\n\u003Cselect name=\"country\">\n  \u003Coption>Country A\u003C\u002Foption>\n  \u003Coption>Country B\u003C\u002Foption>\n\u003C\u002Fselect>\n\u003Cbutton type=\"submit\">Continue\u003C\u002Fbutton>\n```\n\n### Consistent navigation\n\nSame navigation in the same place across pages. The \"Help\" link in the top-right on page A is in the top-right on page B too. Users (especially those with cognitive impairments or who navigate by spatial memory) rely on this.\n\nIf a sub-section needs additional nav, place it in a consistent location (e.g., a left sidebar that always appears in left-sidebar slot).\n\n### Consistent identification\n\nSame component does the same thing across the app. A button labeled \"Save\" always saves; doesn't sometimes mean \"save and close\" and sometimes mean \"save and continue.\" If two different actions are needed, two different labels: \"Save\" and \"Save and continue.\"\n\nSame icon across the app should mean the same thing. A trash icon on one page meaning \"delete,\" another page meaning \"filter,\" is incoherent.\n\n## 3. Input assistance\n\n### Error identification\n\nWCAG 3.3.1: when an error is detected, identify the item in error and describe the error in text.\n\n```html\n\u003Cdiv class=\"field\" data-state=\"error\">\n  \u003Clabel for=\"email\">Email address\u003C\u002Flabel>\n  \u003Cinput id=\"email\"\n         type=\"email\"\n         aria-invalid=\"true\"\n         aria-describedby=\"email-error\" \u002F>\n  \u003Cp id=\"email-error\" class=\"field-error\">\n    \u003CAlertIcon aria-hidden=\"true\" \u002F>\n    Please enter a valid email address (e.g., name@example.com).\n  \u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\nThree things are happening:\n\n- `aria-invalid=\"true\"` flags the input as in error (assistive tech may announce).\n- `aria-describedby` ties the message to the input (screen readers announce both).\n- The message text is specific (says what's wrong) and actionable (offers an example).\n\n### Labels and instructions\n\nEvery input has a programmatically associated label. The label is descriptive (not just \"Field 1\"). If the input requires specific format, instructions are provided alongside.\n\n```html\n\u003C!-- Right: label, format hint, and example -->\n\u003Cdiv class=\"field\">\n  \u003Clabel for=\"phone\">Phone number\u003C\u002Flabel>\n  \u003Cinput id=\"phone\"\n         type=\"tel\"\n         aria-describedby=\"phone-help\"\n         placeholder=\"555-123-4567\" \u002F>\n  \u003Cp id=\"phone-help\" class=\"field-help\">\n    Format: 555-123-4567. We use this only for delivery questions.\n  \u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\nNotes:\n\n- `placeholder` is *not* a label — it disappears when the user starts typing. Use a real `\u003Clabel>`.\n- Format hints belong in adjacent text (`aria-describedby`), not just placeholder.\n- Required fields should be marked both visually (asterisk) and programmatically (`required` attribute or `aria-required`).\n\n### Error suggestion\n\nWCAG 3.3.3 (Level AA): when the user makes an input error and the system can suggest a correction, do so.\n\n```html\n\u003C!-- User typed \"gmial.com\" -->\n\u003Cp class=\"field-error\">\n  Did you mean \u003Cbutton type=\"button\" onclick=\"acceptSuggestion('gmail.com')\">name@gmail.com\u003C\u002Fbutton>?\n\u003C\u002Fp>\n```\n\nDon't auto-correct silently — that's a context change without consent. Suggest, let the user accept.\n\n### Error prevention\n\nWCAG 3.3.4 (Level AA, for legal\u002Ffinancial\u002Fdata submissions): the user must be able to:\n\n- **Reverse** the submission (a \"Cancel my order\" period), OR\n- **Check** the submission for errors before final commit (a confirmation page), OR\n- **Confirm** explicitly before final commit (a confirm dialog).\n\nFor destructive irreversible actions in product UIs (delete account, transfer ownership), this is the strong reason for `AlertDialog` confirmation, type-to-confirm patterns, and 30-day \"soft delete\" recovery windows.\n\n### Help\n\nWCAG 3.3.5 (Level AAA): context-sensitive help is available. Tooltips, inline help, \"What's this?\" links.\n\nIn product UIs, this lands in:\n\n- `\u003CFieldDescription>` next to inputs that need explanation.\n- `?` icons next to settings whose function isn't obvious.\n- A persistent help link or chat in chrome.\n\n### Consistent help\n\nWCAG 3.2.6 (Level A, 2.2): if help mechanisms are present (contact info, FAQ link, chat widget), they appear in the same location across pages.\n\n## Worked examples\n\n### Example 1: a credit-card form with full input assistance\n\n```html\n\u003Cform>\n  \u003Cdiv class=\"field\">\n    \u003Clabel for=\"cc-number\">Card number\u003C\u002Flabel>\n    \u003Cinput id=\"cc-number\"\n           type=\"text\"\n           inputmode=\"numeric\"\n           autocomplete=\"cc-number\"\n           aria-describedby=\"cc-help\"\n           required\n           aria-required=\"true\" \u002F>\n    \u003Cp id=\"cc-help\" class=\"field-help\">\n      16 digits, no spaces or dashes\n    \u003C\u002Fp>\n  \u003C\u002Fdiv>\n\n  \u003Cdiv class=\"field\">\n    \u003Clabel for=\"cc-exp\">Expiration (MM\u002FYY)\u003C\u002Flabel>\n    \u003Cinput id=\"cc-exp\"\n           type=\"text\"\n           inputmode=\"numeric\"\n           autocomplete=\"cc-exp\"\n           placeholder=\"MM\u002FYY\"\n           required\n           aria-required=\"true\" \u002F>\n  \u003C\u002Fdiv>\n\n  \u003Cdiv class=\"field\">\n    \u003Clabel for=\"cc-cvc\">CVC\u003C\u002Flabel>\n    \u003Cinput id=\"cc-cvc\"\n           type=\"text\"\n           inputmode=\"numeric\"\n           autocomplete=\"cc-csc\"\n           aria-describedby=\"cvc-help\"\n           required\n           aria-required=\"true\" \u002F>\n    \u003Cp id=\"cvc-help\" class=\"field-help\">\n      3-digit code on the back of your card (4 on Amex)\n    \u003C\u002Fp>\n  \u003C\u002Fdiv>\n\n  \u003Cbutton type=\"submit\">Review order\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nWhat's happening:\n\n- Each field has a real label (associated via `for`\u002F`id`).\n- `inputmode=\"numeric\"` prompts the right keyboard on mobile.\n- `autocomplete` attributes let password managers and autofill help.\n- Help text is associated via `aria-describedby`.\n- Required is both visual (probably an asterisk from CSS) and programmatic (`required` + `aria-required`).\n- Submit goes to a \"Review order\" page (error prevention via review step).\n\n### Example 2: a destructive action with prevention layers\n\n```html\n\u003Cbutton onclick=\"openDeleteDialog()\">Delete account\u003C\u002Fbutton>\n\n\u003C!-- Dialog: -->\n\u003Cdialog open\n        role=\"dialog\"\n        aria-labelledby=\"confirm-title\"\n        aria-describedby=\"confirm-desc\">\n  \u003Ch2 id=\"confirm-title\">Delete your account?\u003C\u002Fh2>\n  \u003Cp id=\"confirm-desc\">\n    This permanently removes your account, all your projects (12), and your\n    team's access (38 members). This cannot be undone.\n  \u003C\u002Fp>\n  \u003Cp>To confirm, type your account email below:\u003C\u002Fp>\n  \u003Cinput type=\"text\" placeholder=\"you@example.com\" id=\"confirm-input\" \u002F>\n  \u003Cbutton type=\"button\">Cancel\u003C\u002Fbutton>\n  \u003Cbutton type=\"button\"\n          class=\"destructive\"\n          disabled\n          id=\"confirm-button\">\n    Delete account permanently\n  \u003C\u002Fbutton>\n\u003C\u002Fdialog>\n```\n\nThe user must:\n\n1. Click \"Delete account\" (intent).\n2. Read the dialog (consequences laid out).\n3. Type their email (active confirmation, error prevention).\n4. Click \"Delete account permanently\" (final commit).\n\nEach step is a deliberate barrier against accidental destruction.\n\n## Anti-patterns\n\n- **Placeholders as labels.** \"Email\" in placeholder text only — disappears on type, breaks for screen readers, fails on autofill.\n- **Generic error messages.** \"Validation failed.\" Doesn't say which field, doesn't say what's wrong, doesn't say how to fix.\n- **Surprise context changes.** Selecting an option auto-navigates; typing in a field auto-submits. The user loses control.\n- **Inconsistent labels for the same action.** \"Save\" here, \"Submit\" there, \"Confirm\" elsewhere.\n- **No undo and no confirm for destructive actions.** Click-and-it's-gone with no recovery.\n- **Jargon without explanation.** \"API token rotation period\" with no hover or link to explain. The technical user knows; the casual user is lost.\n\n## Heuristics\n\n1. **The five-error test.** Trigger 5 different validation errors. Are all of them named, located near the field, and offered a fix?\n2. **The label audit.** Every form input has a `\u003Clabel>` associated by `for`\u002F`id`. No placeholder-as-label.\n3. **The unexpected-change test.** Walk through a form. Does any change of input value or focus trigger a navigation, popup, or auto-submit? Each is a violation.\n4. **The \"stranger\" test.** Show your form to someone unfamiliar with your product. Can they tell what each field wants without help text? If not, label or instruction is wrong.\n5. **The grade-level check.** Run your microcopy through a readability tool. Above grade 10 for consumer? Simplify.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-perceivable`**, **`accessibility-operable`**, **`accessibility-robust`** — siblings.\n- **`errors`** and **`forgiveness`** (interaction) — error UX is shared between accessibility and general interaction design.\n- **`feedback-loop`** (interaction) — feedback that the system received a change is part of predictability.\n- **`framing`** (cognition) — error copy framing affects whether the user feels blamed or helped.\n- **`mental-model`** (cognition) — predictable behavior aligns with the user's model.\n","# Accessibility — Understandable\n\nWCAG Principle 3: information and the operation of the user interface must be understandable.\n\nThe three sub-criteria, simplified:\n\n1. **Readable** — language is identified, jargon is explained, abbreviations are expanded.\n2. **Predictable** — the UI behaves consistently and changes context only when the user expects.\n3. **Input assistance** — labels, instructions, error messages, and prevention of mistakes.\n\nThis sub-principle is where accessibility most overlaps with general usability — but the consequences fall hardest on users with cognitive impairments, learning disabilities, low literacy, or unfamiliarity with the language.\n\n## 1. Readable\n\n### Language identified\n\nSet the document language so screen readers pronounce correctly:\n\n```html\n\u003Chtml lang=\"en\">\n```\n\nFor mixed-language content, mark the exception:\n\n```html\n\u003Cp>The French word for \"dog\" is \u003Cspan lang=\"fr\">chien\u003C\u002Fspan>.\u003C\u002Fp>\n```\n\nA screen reader switches voice\u002Fpronunciation for the marked span.\n\n### Plain language\n\nWrite at a reading level appropriate to your audience. For consumer products, that's typically grade 8 or below. Tools (Hemingway Editor, Readable, Microsoft Word's readability stats) measure this.\n\nPractices that improve readability:\n\n- Short sentences (\u003C25 words).\n- Active voice (\"Click Save\" not \"Save can be clicked\").\n- Familiar words (use \"buy\" not \"procure\").\n- One idea per sentence.\n- Paragraphs ≤ 5 sentences.\n\n### Jargon and abbreviations\n\nIf you must use jargon or abbreviations, expand them on first use:\n\n```html\n\u003Cp>\n  Single sign-on (\u003Cabbr title=\"Single Sign-On\">SSO\u003C\u002Fabbr>) lets your team\n  use one login across all tools.\n\u003C\u002Fp>\n```\n\nScreen readers can announce the expansion via `\u003Cabbr title>`. Sighted users see the expansion on hover.\n\nFor specialized terms, link to a definition or glossary the first time.\n\n### Pronunciation (rare but worth knowing)\n\nFor content where pronunciation determines meaning (poetry, languages, certain proper nouns), provide pronunciation hints. Most apps don't need this; mention it for completeness.\n\n## 2. Predictable\n\n### Behavior on focus and input\n\nWCAG 3.2.1 and 3.2.2: changing the value of an input or moving focus to an element should NOT trigger an unexpected context change.\n\nSpecifically:\n\n- A `\u003Cselect>` should not auto-submit a form when a value changes.\n- Focusing an input should not open a popup or navigate.\n- Typing into a search field should not navigate to a result page on every keystroke.\n\nIf a context change *is* the intended behavior (typeahead search, live filter), make it expected: label the field as \"Search (results filter as you type),\" show results below the input, don't yank focus.\n\n```html\n\u003C!-- Wrong: select auto-submits on change -->\n\u003Cselect onchange=\"this.form.submit()\">\n  \u003Coption>Country A\u003C\u002Foption>\n  \u003Coption>Country B\u003C\u002Foption>\n\u003C\u002Fselect>\n\n\u003C!-- Right: select waits for explicit submit -->\n\u003Cselect name=\"country\">\n  \u003Coption>Country A\u003C\u002Foption>\n  \u003Coption>Country B\u003C\u002Foption>\n\u003C\u002Fselect>\n\u003Cbutton type=\"submit\">Continue\u003C\u002Fbutton>\n```\n\n### Consistent navigation\n\nSame navigation in the same place across pages. The \"Help\" link in the top-right on page A is in the top-right on page B too. Users (especially those with cognitive impairments or who navigate by spatial memory) rely on this.\n\nIf a sub-section needs additional nav, place it in a consistent location (e.g., a left sidebar that always appears in left-sidebar slot).\n\n### Consistent identification\n\nSame component does the same thing across the app. A button labeled \"Save\" always saves; doesn't sometimes mean \"save and close\" and sometimes mean \"save and continue.\" If two different actions are needed, two different labels: \"Save\" and \"Save and continue.\"\n\nSame icon across the app should mean the same thing. A trash icon on one page meaning \"delete,\" another page meaning \"filter,\" is incoherent.\n\n## 3. Input assistance\n\n### Error identification\n\nWCAG 3.3.1: when an error is detected, identify the item in error and describe the error in text.\n\n```html\n\u003Cdiv class=\"field\" data-state=\"error\">\n  \u003Clabel for=\"email\">Email address\u003C\u002Flabel>\n  \u003Cinput id=\"email\"\n         type=\"email\"\n         aria-invalid=\"true\"\n         aria-describedby=\"email-error\" \u002F>\n  \u003Cp id=\"email-error\" class=\"field-error\">\n    \u003CAlertIcon aria-hidden=\"true\" \u002F>\n    Please enter a valid email address (e.g., name@example.com).\n  \u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\nThree things are happening:\n\n- `aria-invalid=\"true\"` flags the input as in error (assistive tech may announce).\n- `aria-describedby` ties the message to the input (screen readers announce both).\n- The message text is specific (says what's wrong) and actionable (offers an example).\n\n### Labels and instructions\n\nEvery input has a programmatically associated label. The label is descriptive (not just \"Field 1\"). If the input requires specific format, instructions are provided alongside.\n\n```html\n\u003C!-- Right: label, format hint, and example -->\n\u003Cdiv class=\"field\">\n  \u003Clabel for=\"phone\">Phone number\u003C\u002Flabel>\n  \u003Cinput id=\"phone\"\n         type=\"tel\"\n         aria-describedby=\"phone-help\"\n         placeholder=\"555-123-4567\" \u002F>\n  \u003Cp id=\"phone-help\" class=\"field-help\">\n    Format: 555-123-4567. We use this only for delivery questions.\n  \u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\nNotes:\n\n- `placeholder` is *not* a label — it disappears when the user starts typing. Use a real `\u003Clabel>`.\n- Format hints belong in adjacent text (`aria-describedby`), not just placeholder.\n- Required fields should be marked both visually (asterisk) and programmatically (`required` attribute or `aria-required`).\n\n### Error suggestion\n\nWCAG 3.3.3 (Level AA): when the user makes an input error and the system can suggest a correction, do so.\n\n```html\n\u003C!-- User typed \"gmial.com\" -->\n\u003Cp class=\"field-error\">\n  Did you mean \u003Cbutton type=\"button\" onclick=\"acceptSuggestion('gmail.com')\">name@gmail.com\u003C\u002Fbutton>?\n\u003C\u002Fp>\n```\n\nDon't auto-correct silently — that's a context change without consent. Suggest, let the user accept.\n\n### Error prevention\n\nWCAG 3.3.4 (Level AA, for legal\u002Ffinancial\u002Fdata submissions): the user must be able to:\n\n- **Reverse** the submission (a \"Cancel my order\" period), OR\n- **Check** the submission for errors before final commit (a confirmation page), OR\n- **Confirm** explicitly before final commit (a confirm dialog).\n\nFor destructive irreversible actions in product UIs (delete account, transfer ownership), this is the strong reason for `AlertDialog` confirmation, type-to-confirm patterns, and 30-day \"soft delete\" recovery windows.\n\n### Help\n\nWCAG 3.3.5 (Level AAA): context-sensitive help is available. Tooltips, inline help, \"What's this?\" links.\n\nIn product UIs, this lands in:\n\n- `\u003CFieldDescription>` next to inputs that need explanation.\n- `?` icons next to settings whose function isn't obvious.\n- A persistent help link or chat in chrome.\n\n### Consistent help\n\nWCAG 3.2.6 (Level A, 2.2): if help mechanisms are present (contact info, FAQ link, chat widget), they appear in the same location across pages.\n\n## Worked examples\n\n### Example 1: a credit-card form with full input assistance\n\n```html\n\u003Cform>\n  \u003Cdiv class=\"field\">\n    \u003Clabel for=\"cc-number\">Card number\u003C\u002Flabel>\n    \u003Cinput id=\"cc-number\"\n           type=\"text\"\n           inputmode=\"numeric\"\n           autocomplete=\"cc-number\"\n           aria-describedby=\"cc-help\"\n           required\n           aria-required=\"true\" \u002F>\n    \u003Cp id=\"cc-help\" class=\"field-help\">\n      16 digits, no spaces or dashes\n    \u003C\u002Fp>\n  \u003C\u002Fdiv>\n\n  \u003Cdiv class=\"field\">\n    \u003Clabel for=\"cc-exp\">Expiration (MM\u002FYY)\u003C\u002Flabel>\n    \u003Cinput id=\"cc-exp\"\n           type=\"text\"\n           inputmode=\"numeric\"\n           autocomplete=\"cc-exp\"\n           placeholder=\"MM\u002FYY\"\n           required\n           aria-required=\"true\" \u002F>\n  \u003C\u002Fdiv>\n\n  \u003Cdiv class=\"field\">\n    \u003Clabel for=\"cc-cvc\">CVC\u003C\u002Flabel>\n    \u003Cinput id=\"cc-cvc\"\n           type=\"text\"\n           inputmode=\"numeric\"\n           autocomplete=\"cc-csc\"\n           aria-describedby=\"cvc-help\"\n           required\n           aria-required=\"true\" \u002F>\n    \u003Cp id=\"cvc-help\" class=\"field-help\">\n      3-digit code on the back of your card (4 on Amex)\n    \u003C\u002Fp>\n  \u003C\u002Fdiv>\n\n  \u003Cbutton type=\"submit\">Review order\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nWhat's happening:\n\n- Each field has a real label (associated via `for`\u002F`id`).\n- `inputmode=\"numeric\"` prompts the right keyboard on mobile.\n- `autocomplete` attributes let password managers and autofill help.\n- Help text is associated via `aria-describedby`.\n- Required is both visual (probably an asterisk from CSS) and programmatic (`required` + `aria-required`).\n- Submit goes to a \"Review order\" page (error prevention via review step).\n\n### Example 2: a destructive action with prevention layers\n\n```html\n\u003Cbutton onclick=\"openDeleteDialog()\">Delete account\u003C\u002Fbutton>\n\n\u003C!-- Dialog: -->\n\u003Cdialog open\n        role=\"dialog\"\n        aria-labelledby=\"confirm-title\"\n        aria-describedby=\"confirm-desc\">\n  \u003Ch2 id=\"confirm-title\">Delete your account?\u003C\u002Fh2>\n  \u003Cp id=\"confirm-desc\">\n    This permanently removes your account, all your projects (12), and your\n    team's access (38 members). This cannot be undone.\n  \u003C\u002Fp>\n  \u003Cp>To confirm, type your account email below:\u003C\u002Fp>\n  \u003Cinput type=\"text\" placeholder=\"you@example.com\" id=\"confirm-input\" \u002F>\n  \u003Cbutton type=\"button\">Cancel\u003C\u002Fbutton>\n  \u003Cbutton type=\"button\"\n          class=\"destructive\"\n          disabled\n          id=\"confirm-button\">\n    Delete account permanently\n  \u003C\u002Fbutton>\n\u003C\u002Fdialog>\n```\n\nThe user must:\n\n1. Click \"Delete account\" (intent).\n2. Read the dialog (consequences laid out).\n3. Type their email (active confirmation, error prevention).\n4. Click \"Delete account permanently\" (final commit).\n\nEach step is a deliberate barrier against accidental destruction.\n\n## Anti-patterns\n\n- **Placeholders as labels.** \"Email\" in placeholder text only — disappears on type, breaks for screen readers, fails on autofill.\n- **Generic error messages.** \"Validation failed.\" Doesn't say which field, doesn't say what's wrong, doesn't say how to fix.\n- **Surprise context changes.** Selecting an option auto-navigates; typing in a field auto-submits. The user loses control.\n- **Inconsistent labels for the same action.** \"Save\" here, \"Submit\" there, \"Confirm\" elsewhere.\n- **No undo and no confirm for destructive actions.** Click-and-it's-gone with no recovery.\n- **Jargon without explanation.** \"API token rotation period\" with no hover or link to explain. The technical user knows; the casual user is lost.\n\n## Heuristics\n\n1. **The five-error test.** Trigger 5 different validation errors. Are all of them named, located near the field, and offered a fix?\n2. **The label audit.** Every form input has a `\u003Clabel>` associated by `for`\u002F`id`. No placeholder-as-label.\n3. **The unexpected-change test.** Walk through a form. Does any change of input value or focus trigger a navigation, popup, or auto-submit? Each is a violation.\n4. **The \"stranger\" test.** Show your form to someone unfamiliar with your product. Can they tell what each field wants without help text? If not, label or instruction is wrong.\n5. **The grade-level check.** Run your microcopy through a readability tool. Above grade 10 for consumer? Simplify.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-perceivable`**, **`accessibility-operable`**, **`accessibility-robust`** — siblings.\n- **`errors`** and **`forgiveness`** (interaction) — error UX is shared between accessibility and general interaction design.\n- **`feedback-loop`** (interaction) — feedback that the system received a change is part of predictability.\n- **`framing`** (cognition) — error copy framing affects whether the user feels blamed or helped.\n- **`mental-model`** (cognition) — predictable behavior aligns with the user's model.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-understandable",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-understandable",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-understandable",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-understandable","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-understandable\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Funderstandable-deep-dive.md","REFERENCE","参考文档",4593,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-understandable\u002Freferences\u002Funderstandable-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",[],[]]