[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWH8CMDRWATCEA96HH85NP":3,"skill-same:01M6JWH8CMDRWATCEA96HH85NP":81},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6JWH8CMDRWATCEA96HH85NP","accessibility-perceivable",null,"Use this skill when the question is whether users can *perceive* the content — see it, hear it, or feel it — regardless of impairment. Trigger when designing color systems, picking text sizes, building image-heavy surfaces, working with video\u002Faudio, designing for low-vision users, or running an accessibility audit. Covers WCAG Principle 1 (Perceivable). 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-perceivable\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"accessibility","accessibility perceivable","running","image","when","for","can","you","color","users","trigger","surfaces","vision","use","read","question","text","WCAG","Audio","Video","accessibility audit","audit","2026-11-10 10:12:30",false,"---\nname: accessibility-perceivable\ndescription: 'Use this skill when the question is whether users can *perceive* the content — see it, hear it, or feel it — regardless of impairment. Trigger when designing color systems, picking text sizes, building image-heavy surfaces, working with video\u002Faudio, designing for low-vision users, or running an accessibility audit. Covers WCAG Principle 1 (Perceivable). Sub-aspect of `accessibility`; read that first if you haven''t already.'\n---\n\n# Accessibility — Perceivable\n\nWCAG Principle 1: information and user-interface components must be presentable to users in ways they can perceive.\n\nThe four sub-criteria, simplified:\n\n1. **Text alternatives** for non-text content.\n2. **Time-based media** (audio\u002Fvideo) has alternatives.\n3. **Adaptable** content can be presented in different ways without losing structure.\n4. **Distinguishable** — color contrast, audio control, text resizing.\n\nThis skill covers each in practical detail.\n\n## 1. Text alternatives\n\n### Images\n\nEvery image gets alternative text describing what's relevant about it. The right alt text depends on the image's role:\n\n```html\n\u003C!-- Informative: describe what the user needs to know -->\n\u003Cimg src=\"\u002Fdashboard-screenshot.png\"\n     alt=\"Dashboard showing $48,200 monthly revenue, up 12% from last month.\" \u002F>\n\n\u003C!-- Functional (image as link \u002F button): describe the action -->\n\u003Ca href=\"\u002Fprofile\">\n  \u003Cimg src=\"\u002Favatar.png\" alt=\"Open your profile\" \u002F>\n\u003C\u002Fa>\n\n\u003C!-- Decorative: empty alt so screen readers skip -->\n\u003Cimg src=\"\u002Fdecorative-pattern.svg\" alt=\"\" aria-hidden=\"true\" \u002F>\n\n\u003C!-- Complex (chart, infographic): brief alt + linked long description -->\n\u003Cfigure>\n  \u003Cimg src=\"\u002Fsales-chart.png\"\n       alt=\"Quarterly sales chart, see description below.\"\n       aria-describedby=\"chart-desc\" \u002F>\n  \u003Cfigcaption id=\"chart-desc\">\n    Sales rose from $12k in Q1 to $58k in Q4, with a dip to $31k in Q3 caused\n    by a supply chain interruption.\n  \u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n```\n\n**Common mistakes:**\n- `alt=\"image\"` or `alt=\"photo of woman\"` — describes the file type, not the meaning.\n- Decorative images with non-empty alt — screen reader users hear \"decorative-pattern-3-svg\" announced as content.\n- Long alt text on simple images — alt should be ≤ 125 characters; longer goes in `\u003Cfigcaption>` or linked description.\n\n### Icons\n\nIcon-only buttons need an accessible name. Two patterns:\n\n```html\n\u003C!-- Pattern A: aria-label on the button -->\n\u003Cbutton aria-label=\"Close\">\n  \u003Csvg aria-hidden=\"true\">...\u003C\u002Fsvg>\n\u003C\u002Fbutton>\n\n\u003C!-- Pattern B: visually-hidden text -->\n\u003Cbutton>\n  \u003Csvg aria-hidden=\"true\">...\u003C\u002Fsvg>\n  \u003Cspan class=\"sr-only\">Close\u003C\u002Fspan>\n\u003C\u002Fbutton>\n```\n\nEither is fine; pattern B can be more reliable across screen readers. The `sr-only` class:\n\n```css\n.sr-only {\n  position: absolute;\n  width: 1px; height: 1px;\n  padding: 0; margin: -1px;\n  overflow: hidden;\n  clip: rect(0,0,0,0);\n  white-space: nowrap;\n  border: 0;\n}\n```\n\n### Decorative SVG\n\n```html\n\u003Csvg aria-hidden=\"true\" focusable=\"false\">...\u003C\u002Fsvg>\n```\n\n`aria-hidden` removes from accessibility tree; `focusable=\"false\"` prevents keyboard focus on the SVG (some browsers focus SVGs by default).\n\n## 2. Time-based media\n\n### Video\n\n- **Captions** for all spoken content. Auto-generated captions are a starting point; review for accuracy.\n- **Audio descriptions** for visual content not conveyed by audio (a chart appearing on screen, a character action shown but not narrated).\n- **Transcripts** as text alternatives for anyone who can't watch.\n\n### Audio\n\n- **Transcripts** for podcasts, interviews, voicemails.\n- **Captions or transcripts** for any audio-only message in the UI.\n\n### Auto-playing media\n\nDon't autoplay video or audio with sound. WCAG 1.4.2 requires that audio playing for more than 3 seconds either:\n\n- Has a pause\u002Fstop control, or\n- Has a volume control independent of system volume.\n\nBetter: don't autoplay sound at all. It's hostile to users with hearing aids, in public spaces, or sharing audio output.\n\n## 3. Adaptable\n\n### Semantic structure\n\nUse HTML elements for what they're for. Heading order matters; landmarks matter; lists matter.\n\n```html\n\u003C!-- Right -->\n\u003Cmain>\n  \u003Ch1>Dashboard\u003C\u002Fh1>\n  \u003Csection aria-labelledby=\"kpi-heading\">\n    \u003Ch2 id=\"kpi-heading\">This month\u003C\u002Fh2>\n    \u003Cul>\n      \u003Cli>Revenue: $48k\u003C\u002Fli>\n      \u003Cli>Users: 12,481\u003C\u002Fli>\n    \u003C\u002Ful>\n  \u003C\u002Fsection>\n\u003C\u002Fmain>\n\n\u003C!-- Wrong: divs everywhere, no structure -->\n\u003Cdiv>\n  \u003Cdiv>Dashboard\u003C\u002Fdiv>\n  \u003Cdiv>This month\u003C\u002Fdiv>\n  \u003Cdiv>Revenue: $48k\u003C\u002Fdiv>\n  \u003Cdiv>Users: 12,481\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nScreen readers navigate by headings (`H` key in NVDA), landmarks (`R` key), lists, links. Without semantic structure, navigation falls apart.\n\n### Heading order\n\nDon't skip heading levels. Page structure:\n\n```\n\u003Ch1>Page title (one per page)\n  \u003Ch2>Section\n    \u003Ch3>Subsection\n      \u003Ch4>Sub-subsection\n```\n\nGoing from `\u003Ch1>` to `\u003Ch3>` confuses assistive tech. If the visual size you want for an `\u003Ch2>` is too large, restyle the `\u003Ch2>` — don't reach for `\u003Ch3>` to get smaller text.\n\n### Reading order\n\nSource order in HTML should match visual reading order. CSS Grid and Flexbox can rearrange visually, but screen readers follow source order.\n\n```html\n\u003C!-- Source order matches visual order: title, then summary, then details -->\n\u003Carticle>\n  \u003Ch2>Article title\u003C\u002Fh2>\n  \u003Cp class=\"summary\">Brief summary.\u003C\u002Fp>\n  \u003Cp>Detailed body...\u003C\u002Fp>\n\u003C\u002Farticle>\n\n\u003C!-- Wrong: visually rearranged but source order is now confusing -->\n\u003Carticle style=\"display: flex; flex-direction: column-reverse;\">\n  \u003Cp>Detailed body...\u003C\u002Fp>\n  \u003Cp>Summary.\u003C\u002Fp>\n  \u003Ch2>Title\u003C\u002Fh2>\n\u003C\u002Farticle>\n```\n\n### Programmatic relationships\n\nUse `\u003Clabel for>`, `aria-labelledby`, `aria-describedby` to expose visual relationships to assistive tech.\n\n```html\n\u003Cdiv>\n  \u003Clabel for=\"email\">Email\u003C\u002Flabel>\n  \u003Cinput id=\"email\" aria-describedby=\"email-help\" \u002F>\n  \u003Cp id=\"email-help\">We'll never share this.\u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\nThe label is associated; the help text is associated. A screen reader announces all three together.\n\n## 4. Distinguishable\n\n### Color contrast\n\nWCAG ratios:\n\n| Content | Level AA | Level AAA |\n|---|---|---|\n| Body text (\u003C 18pt regular or \u003C 14pt bold) | 4.5:1 | 7:1 |\n| Large text (≥ 18pt regular or ≥ 14pt bold) | 3:1 | 4.5:1 |\n| UI components and graphical objects | 3:1 | (no AAA) |\n| Disabled \u002F inactive elements | (exempt) | (exempt) |\n\nTest every text-on-background combination. Common failures:\n\n- Light grey body text (`#999` on white = 2.85:1, fails AA).\n- Brand-color body links (`#1e90ff` on white = 3.4:1, fails AA for body text).\n- Placeholder text in inputs (often muted to look \"less important,\" ends up unreadable).\n\nTools: WebAIM Contrast Checker, Stark plugin, Chrome DevTools' contrast inspector.\n\n### Color not the only signal\n\nWCAG 1.4.1: don't use color alone to convey information. Pair with icon, text, pattern, or position.\n\n```html\n\u003C!-- Wrong: red border = error, but if red isn't perceivable, no signal -->\n\u003Cinput style=\"border: 2px solid red\" \u002F>\n\n\u003C!-- Right: red border + icon + descriptive text -->\n\u003Cdiv class=\"field\" data-state=\"error\">\n  \u003Clabel for=\"email\">Email\u003C\u002Flabel>\n  \u003Cinput id=\"email\" aria-invalid=\"true\" aria-describedby=\"email-error\" \u002F>\n  \u003Cp id=\"email-error\">\n    \u003CAlertIcon aria-hidden=\"true\" \u002F> Please enter a valid email.\n  \u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\n### Text resize\n\nWCAG 1.4.4: text must be resizable up to 200% without loss of content or functionality. Test:\n\n- Browser zoom at 200% — does content reflow without horizontal scroll?\n- Text size only at 200% (Firefox supports text-only zoom) — does the layout survive?\n\nUse relative units (`rem`, `em`, `%`) for type sizes; avoid `px` for body text. Use `vw`\u002F`vh` cautiously — they don't scale with text size.\n\n### Reflow\n\nWCAG 1.4.10 (Level AA): content reflows to a 320 CSS-pixel-wide viewport without requiring horizontal scrolling. Equivalent to 400% zoom on a 1280px viewport.\n\nPractical test: open the design in DevTools at 320px wide and 1280px wide. Anything that requires sideways scroll for primary content fails.\n\n### Images of text\n\nAvoid embedding text in images (which can't be resized, restyled, or read by screen readers). Render text as text wherever possible. SVG with `\u003Ctext>` elements is OK because it scales and can be read; raster images of text aren't.\n\n### Non-color content\n\nPatterns, textures, position, shape — non-color signals carry meaning for color-blind users:\n\n```html\n\u003C!-- Chart series with color + pattern -->\n\u003Csvg>\n  \u003Crect fill=\"url(#solid-blue)\" \u002F>     \u003C!-- Series A: solid blue -->\n  \u003Crect fill=\"url(#striped-blue)\" \u002F>   \u003C!-- Series B: striped blue -->\n  \u003Crect fill=\"url(#dotted-blue)\" \u002F>    \u003C!-- Series C: dotted blue -->\n\u003C\u002Fsvg>\n```\n\nEven users who can perceive color benefit from redundant signals.\n\n## Worked example: an accessible status badge system\n\n```html\n\u003Cstyle>\n  .badge { display: inline-flex; align-items: center; gap: 4px;\n           padding: 2px 8px; border-radius: 9999px;\n           font-size: 12px; font-weight: 500; }\n  .badge--success { background: hsl(142 70% 95%); color: hsl(142 70% 22%); }\n  .badge--warning { background: hsl(38 95% 95%); color: hsl(38 90% 25%); }\n  .badge--error   { background: hsl(0 80% 95%); color: hsl(0 75% 32%); }\n\u003C\u002Fstyle>\n\n\u003Cspan class=\"badge badge--success\">\n  \u003CCheckIcon aria-hidden=\"true\" \u002F> Paid\n\u003C\u002Fspan>\n\u003Cspan class=\"badge badge--warning\">\n  \u003CClockIcon aria-hidden=\"true\" \u002F> Pending\n\u003C\u002Fspan>\n\u003Cspan class=\"badge badge--error\">\n  \u003CAlertIcon aria-hidden=\"true\" \u002F> Overdue\n\u003C\u002Fspan>\n```\n\nWhat's working:\n\n- Color + icon + text — three signals.\n- Contrast ratios above 7:1 for both color combinations (verified in a contrast checker).\n- Icons have `aria-hidden` since the text already conveys meaning.\n- Background color tinted, foreground darkened, both relative to a hue rather than using full saturation (preserves AA contrast).\n\n## Anti-patterns\n\n- **`alt=\"image\"` or `alt=\"\"` on informative images.** Screen reader users get nothing.\n- **Color-only error states.** A red border with no text or icon. Color-blind users perceive no error.\n- **Pale-grey body text for elegance.** Below 4.5:1 contrast — looks polished, fails AA, exhausts users with low vision.\n- **Auto-playing video with sound.** Hostile to users in shared spaces, with hearing aids, on subway commutes.\n- **Heading shenanigans.** Using `\u003Ch2>` for \"I want this size\" rather than for structural meaning. Leaves `\u003Ch1>` missing or `\u003Ch2>` skipped.\n\n## Heuristics\n\n1. **The contrast checker pass.** Every text-on-background pair, every UI-element-against-background pair. Body must clear 4.5:1; large text and UI 3:1.\n2. **The grayscale pass.** Take a screenshot, convert to grayscale. Do all status indicators still parse?\n3. **The 200% zoom test.** Browser zoom to 200%. Layout survives? Buttons still hittable? No content lost?\n4. **The screen-reader pass.** With VoiceOver \u002F NVDA \u002F TalkBack, walk a critical flow. Listen for unlabeled controls, announced as \"blank,\" missing state.\n5. **The image audit.** Every `\u003Cimg>`. Alt text describes what the user needs to know. Decorative images have empty alt.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-operable`** — keyboard reach and target size.\n- **`accessibility-understandable`** — labels, copy, predictability.\n- **`accessibility-robust`** — semantic markup and ARIA.\n- **`color`** and **`hierarchy-color-and-tone`** (perception) — color decisions that respect contrast.\n- **`legibility`** and **`readability`** (perception) — type decisions that aid perception.\n","# Accessibility — Perceivable\n\nWCAG Principle 1: information and user-interface components must be presentable to users in ways they can perceive.\n\nThe four sub-criteria, simplified:\n\n1. **Text alternatives** for non-text content.\n2. **Time-based media** (audio\u002Fvideo) has alternatives.\n3. **Adaptable** content can be presented in different ways without losing structure.\n4. **Distinguishable** — color contrast, audio control, text resizing.\n\nThis skill covers each in practical detail.\n\n## 1. Text alternatives\n\n### Images\n\nEvery image gets alternative text describing what's relevant about it. The right alt text depends on the image's role:\n\n```html\n\u003C!-- Informative: describe what the user needs to know -->\n\u003Cimg src=\"\u002Fdashboard-screenshot.png\"\n     alt=\"Dashboard showing $48,200 monthly revenue, up 12% from last month.\" \u002F>\n\n\u003C!-- Functional (image as link \u002F button): describe the action -->\n\u003Ca href=\"\u002Fprofile\">\n  \u003Cimg src=\"\u002Favatar.png\" alt=\"Open your profile\" \u002F>\n\u003C\u002Fa>\n\n\u003C!-- Decorative: empty alt so screen readers skip -->\n\u003Cimg src=\"\u002Fdecorative-pattern.svg\" alt=\"\" aria-hidden=\"true\" \u002F>\n\n\u003C!-- Complex (chart, infographic): brief alt + linked long description -->\n\u003Cfigure>\n  \u003Cimg src=\"\u002Fsales-chart.png\"\n       alt=\"Quarterly sales chart, see description below.\"\n       aria-describedby=\"chart-desc\" \u002F>\n  \u003Cfigcaption id=\"chart-desc\">\n    Sales rose from $12k in Q1 to $58k in Q4, with a dip to $31k in Q3 caused\n    by a supply chain interruption.\n  \u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n```\n\n**Common mistakes:**\n- `alt=\"image\"` or `alt=\"photo of woman\"` — describes the file type, not the meaning.\n- Decorative images with non-empty alt — screen reader users hear \"decorative-pattern-3-svg\" announced as content.\n- Long alt text on simple images — alt should be ≤ 125 characters; longer goes in `\u003Cfigcaption>` or linked description.\n\n### Icons\n\nIcon-only buttons need an accessible name. Two patterns:\n\n```html\n\u003C!-- Pattern A: aria-label on the button -->\n\u003Cbutton aria-label=\"Close\">\n  \u003Csvg aria-hidden=\"true\">...\u003C\u002Fsvg>\n\u003C\u002Fbutton>\n\n\u003C!-- Pattern B: visually-hidden text -->\n\u003Cbutton>\n  \u003Csvg aria-hidden=\"true\">...\u003C\u002Fsvg>\n  \u003Cspan class=\"sr-only\">Close\u003C\u002Fspan>\n\u003C\u002Fbutton>\n```\n\nEither is fine; pattern B can be more reliable across screen readers. The `sr-only` class:\n\n```css\n.sr-only {\n  position: absolute;\n  width: 1px; height: 1px;\n  padding: 0; margin: -1px;\n  overflow: hidden;\n  clip: rect(0,0,0,0);\n  white-space: nowrap;\n  border: 0;\n}\n```\n\n### Decorative SVG\n\n```html\n\u003Csvg aria-hidden=\"true\" focusable=\"false\">...\u003C\u002Fsvg>\n```\n\n`aria-hidden` removes from accessibility tree; `focusable=\"false\"` prevents keyboard focus on the SVG (some browsers focus SVGs by default).\n\n## 2. Time-based media\n\n### Video\n\n- **Captions** for all spoken content. Auto-generated captions are a starting point; review for accuracy.\n- **Audio descriptions** for visual content not conveyed by audio (a chart appearing on screen, a character action shown but not narrated).\n- **Transcripts** as text alternatives for anyone who can't watch.\n\n### Audio\n\n- **Transcripts** for podcasts, interviews, voicemails.\n- **Captions or transcripts** for any audio-only message in the UI.\n\n### Auto-playing media\n\nDon't autoplay video or audio with sound. WCAG 1.4.2 requires that audio playing for more than 3 seconds either:\n\n- Has a pause\u002Fstop control, or\n- Has a volume control independent of system volume.\n\nBetter: don't autoplay sound at all. It's hostile to users with hearing aids, in public spaces, or sharing audio output.\n\n## 3. Adaptable\n\n### Semantic structure\n\nUse HTML elements for what they're for. Heading order matters; landmarks matter; lists matter.\n\n```html\n\u003C!-- Right -->\n\u003Cmain>\n  \u003Ch1>Dashboard\u003C\u002Fh1>\n  \u003Csection aria-labelledby=\"kpi-heading\">\n    \u003Ch2 id=\"kpi-heading\">This month\u003C\u002Fh2>\n    \u003Cul>\n      \u003Cli>Revenue: $48k\u003C\u002Fli>\n      \u003Cli>Users: 12,481\u003C\u002Fli>\n    \u003C\u002Ful>\n  \u003C\u002Fsection>\n\u003C\u002Fmain>\n\n\u003C!-- Wrong: divs everywhere, no structure -->\n\u003Cdiv>\n  \u003Cdiv>Dashboard\u003C\u002Fdiv>\n  \u003Cdiv>This month\u003C\u002Fdiv>\n  \u003Cdiv>Revenue: $48k\u003C\u002Fdiv>\n  \u003Cdiv>Users: 12,481\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nScreen readers navigate by headings (`H` key in NVDA), landmarks (`R` key), lists, links. Without semantic structure, navigation falls apart.\n\n### Heading order\n\nDon't skip heading levels. Page structure:\n\n```\n\u003Ch1>Page title (one per page)\n  \u003Ch2>Section\n    \u003Ch3>Subsection\n      \u003Ch4>Sub-subsection\n```\n\nGoing from `\u003Ch1>` to `\u003Ch3>` confuses assistive tech. If the visual size you want for an `\u003Ch2>` is too large, restyle the `\u003Ch2>` — don't reach for `\u003Ch3>` to get smaller text.\n\n### Reading order\n\nSource order in HTML should match visual reading order. CSS Grid and Flexbox can rearrange visually, but screen readers follow source order.\n\n```html\n\u003C!-- Source order matches visual order: title, then summary, then details -->\n\u003Carticle>\n  \u003Ch2>Article title\u003C\u002Fh2>\n  \u003Cp class=\"summary\">Brief summary.\u003C\u002Fp>\n  \u003Cp>Detailed body...\u003C\u002Fp>\n\u003C\u002Farticle>\n\n\u003C!-- Wrong: visually rearranged but source order is now confusing -->\n\u003Carticle style=\"display: flex; flex-direction: column-reverse;\">\n  \u003Cp>Detailed body...\u003C\u002Fp>\n  \u003Cp>Summary.\u003C\u002Fp>\n  \u003Ch2>Title\u003C\u002Fh2>\n\u003C\u002Farticle>\n```\n\n### Programmatic relationships\n\nUse `\u003Clabel for>`, `aria-labelledby`, `aria-describedby` to expose visual relationships to assistive tech.\n\n```html\n\u003Cdiv>\n  \u003Clabel for=\"email\">Email\u003C\u002Flabel>\n  \u003Cinput id=\"email\" aria-describedby=\"email-help\" \u002F>\n  \u003Cp id=\"email-help\">We'll never share this.\u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\nThe label is associated; the help text is associated. A screen reader announces all three together.\n\n## 4. Distinguishable\n\n### Color contrast\n\nWCAG ratios:\n\n| Content | Level AA | Level AAA |\n|---|---|---|\n| Body text (\u003C 18pt regular or \u003C 14pt bold) | 4.5:1 | 7:1 |\n| Large text (≥ 18pt regular or ≥ 14pt bold) | 3:1 | 4.5:1 |\n| UI components and graphical objects | 3:1 | (no AAA) |\n| Disabled \u002F inactive elements | (exempt) | (exempt) |\n\nTest every text-on-background combination. Common failures:\n\n- Light grey body text (`#999` on white = 2.85:1, fails AA).\n- Brand-color body links (`#1e90ff` on white = 3.4:1, fails AA for body text).\n- Placeholder text in inputs (often muted to look \"less important,\" ends up unreadable).\n\nTools: WebAIM Contrast Checker, Stark plugin, Chrome DevTools' contrast inspector.\n\n### Color not the only signal\n\nWCAG 1.4.1: don't use color alone to convey information. Pair with icon, text, pattern, or position.\n\n```html\n\u003C!-- Wrong: red border = error, but if red isn't perceivable, no signal -->\n\u003Cinput style=\"border: 2px solid red\" \u002F>\n\n\u003C!-- Right: red border + icon + descriptive text -->\n\u003Cdiv class=\"field\" data-state=\"error\">\n  \u003Clabel for=\"email\">Email\u003C\u002Flabel>\n  \u003Cinput id=\"email\" aria-invalid=\"true\" aria-describedby=\"email-error\" \u002F>\n  \u003Cp id=\"email-error\">\n    \u003CAlertIcon aria-hidden=\"true\" \u002F> Please enter a valid email.\n  \u003C\u002Fp>\n\u003C\u002Fdiv>\n```\n\n### Text resize\n\nWCAG 1.4.4: text must be resizable up to 200% without loss of content or functionality. Test:\n\n- Browser zoom at 200% — does content reflow without horizontal scroll?\n- Text size only at 200% (Firefox supports text-only zoom) — does the layout survive?\n\nUse relative units (`rem`, `em`, `%`) for type sizes; avoid `px` for body text. Use `vw`\u002F`vh` cautiously — they don't scale with text size.\n\n### Reflow\n\nWCAG 1.4.10 (Level AA): content reflows to a 320 CSS-pixel-wide viewport without requiring horizontal scrolling. Equivalent to 400% zoom on a 1280px viewport.\n\nPractical test: open the design in DevTools at 320px wide and 1280px wide. Anything that requires sideways scroll for primary content fails.\n\n### Images of text\n\nAvoid embedding text in images (which can't be resized, restyled, or read by screen readers). Render text as text wherever possible. SVG with `\u003Ctext>` elements is OK because it scales and can be read; raster images of text aren't.\n\n### Non-color content\n\nPatterns, textures, position, shape — non-color signals carry meaning for color-blind users:\n\n```html\n\u003C!-- Chart series with color + pattern -->\n\u003Csvg>\n  \u003Crect fill=\"url(#solid-blue)\" \u002F>     \u003C!-- Series A: solid blue -->\n  \u003Crect fill=\"url(#striped-blue)\" \u002F>   \u003C!-- Series B: striped blue -->\n  \u003Crect fill=\"url(#dotted-blue)\" \u002F>    \u003C!-- Series C: dotted blue -->\n\u003C\u002Fsvg>\n```\n\nEven users who can perceive color benefit from redundant signals.\n\n## Worked example: an accessible status badge system\n\n```html\n\u003Cstyle>\n  .badge { display: inline-flex; align-items: center; gap: 4px;\n           padding: 2px 8px; border-radius: 9999px;\n           font-size: 12px; font-weight: 500; }\n  .badge--success { background: hsl(142 70% 95%); color: hsl(142 70% 22%); }\n  .badge--warning { background: hsl(38 95% 95%); color: hsl(38 90% 25%); }\n  .badge--error   { background: hsl(0 80% 95%); color: hsl(0 75% 32%); }\n\u003C\u002Fstyle>\n\n\u003Cspan class=\"badge badge--success\">\n  \u003CCheckIcon aria-hidden=\"true\" \u002F> Paid\n\u003C\u002Fspan>\n\u003Cspan class=\"badge badge--warning\">\n  \u003CClockIcon aria-hidden=\"true\" \u002F> Pending\n\u003C\u002Fspan>\n\u003Cspan class=\"badge badge--error\">\n  \u003CAlertIcon aria-hidden=\"true\" \u002F> Overdue\n\u003C\u002Fspan>\n```\n\nWhat's working:\n\n- Color + icon + text — three signals.\n- Contrast ratios above 7:1 for both color combinations (verified in a contrast checker).\n- Icons have `aria-hidden` since the text already conveys meaning.\n- Background color tinted, foreground darkened, both relative to a hue rather than using full saturation (preserves AA contrast).\n\n## Anti-patterns\n\n- **`alt=\"image\"` or `alt=\"\"` on informative images.** Screen reader users get nothing.\n- **Color-only error states.** A red border with no text or icon. Color-blind users perceive no error.\n- **Pale-grey body text for elegance.** Below 4.5:1 contrast — looks polished, fails AA, exhausts users with low vision.\n- **Auto-playing video with sound.** Hostile to users in shared spaces, with hearing aids, on subway commutes.\n- **Heading shenanigans.** Using `\u003Ch2>` for \"I want this size\" rather than for structural meaning. Leaves `\u003Ch1>` missing or `\u003Ch2>` skipped.\n\n## Heuristics\n\n1. **The contrast checker pass.** Every text-on-background pair, every UI-element-against-background pair. Body must clear 4.5:1; large text and UI 3:1.\n2. **The grayscale pass.** Take a screenshot, convert to grayscale. Do all status indicators still parse?\n3. **The 200% zoom test.** Browser zoom to 200%. Layout survives? Buttons still hittable? No content lost?\n4. **The screen-reader pass.** With VoiceOver \u002F NVDA \u002F TalkBack, walk a critical flow. Listen for unlabeled controls, announced as \"blank,\" missing state.\n5. **The image audit.** Every `\u003Cimg>`. Alt text describes what the user needs to know. Decorative images have empty alt.\n\n## Related skills\n\n- **`accessibility`** (parent).\n- **`accessibility-operable`** — keyboard reach and target size.\n- **`accessibility-understandable`** — labels, copy, predictability.\n- **`accessibility-robust`** — semantic markup and ARIA.\n- **`color`** and **`hierarchy-color-and-tone`** (perception) — color decisions that respect contrast.\n- **`legibility`** and **`readability`** (perception) — type decisions that aid perception.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-perceivable",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-perceivable",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-perceivable",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill accessibility-perceivable","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-perceivable\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fperceivable-deep-dive.md","REFERENCE","参考文档",5304,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Faccessibility-perceivable\u002Freferences\u002Fperceivable-deep-dive.md",[82,92,100,108,116,124],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":91},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":91},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":91},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":91},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":91},"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",[],[]]