Skip to content

forcedotcom/sf-skills / plugins/builder/experience-lwc/skills/experience-accessibility-validate

experience-accessibility-validate

Verified

Use this skill to determine whether a Lightning Web Component (LWC) is accessible and meets WCAG accessibility guidelines. TRIGGER when the user asks "is my component accessible?", "does my LWC meet accessibility guidelines?", "is this component WCAG compliant?", "find accessibility problems in this LWC", "is this LWC keyboard accessible?", "does this component work with a screen reader?", "does this component have sufficient color contrast?", "check ARIA usage in this LWC", or "WCAG 2.2 accessibility check". Also TRIGGER when the user wants to fix or improve accessibility (a11y, WCAG, ARIA) in an LWC's HTML, JS, or CSS — semantic markup, focus, keyboard nav, contrast, screen-reader labels, WCAG 2.2 SC. Produces `a11y-review.md` with WCAG-cited findings. DO NOT TRIGGER for general LWC generation (use `experience-lwc-generate`) or SLDS visual/design review not focused on accessibility (use `design-systems-slds-validate`).

FileKindSize
SKILL.mdskill md9.5 KB
references/reviewers/sc-1-1-1-non-text-content.mdmarkdown7.5 KB
references/reviewers/sc-1-3-1-i-lists.mdmarkdown7.0 KB
references/reviewers/sc-1-3-1-ii-tables.mdmarkdown11.9 KB
references/reviewers/sc-1-3-1-iii-form-labels.mdmarkdown6.2 KB
references/reviewers/sc-1-3-1-iv-regions.mdmarkdown5.1 KB
references/reviewers/sc-1-3-1-v-groups.mdmarkdown9.4 KB
references/reviewers/sc-1-3-5-identify-input.mdmarkdown8.7 KB
references/reviewers/sc-1-4-3-contrast.mdmarkdown12.0 KB
references/reviewers/sc-2-1-1-keyboard.mdmarkdown7.7 KB
references/reviewers/sc-2-4-4-link-purpose.mdmarkdown5.8 KB
references/reviewers/sc-2-4-6-headings-labels.mdmarkdown8.0 KB
references/reviewers/sc-2-5-1-pointer-gestures.mdmarkdown6.4 KB
references/reviewers/sc-2-5-2-pointer-cancellation.mdmarkdown7.5 KB
references/reviewers/sc-2-5-3-label-in-name.mdmarkdown9.9 KB
references/reviewers/sc-2-5-7-dragging-movement.mdmarkdown7.0 KB
references/reviewers/sc-3-2-1-on-focus.mdmarkdown7.1 KB
references/reviewers/sc-3-2-2-on-input.mdmarkdown8.1 KB
references/reviewers/sc-3-3-1-error-identification.mdmarkdown11.8 KB
references/reviewers/sc-3-3-2-labels-instructions.mdmarkdown6.3 KB
references/reviewers/sc-3-3-3-error-suggestion.mdmarkdown8.4 KB
references/reviewers/sc-4-1-2-i-name.mdmarkdown15.4 KB
references/reviewers/sc-4-1-2-ii-role.mdmarkdown8.7 KB
references/reviewers/sc-4-1-2-iii-value.mdmarkdown9.4 KB
references/vision/sc-1-1-1-non-text-content.mdmarkdown4.2 KB
references/vision/sc-1-4-1-use-of-color.mdmarkdown5.2 KB
references/vision/sc-1-4-10-resize-reflow.mdmarkdown1022 B
references/vision/sc-1-4-11-non-text-contrast.mdmarkdown2.8 KB
references/vision/sc-1-4-3-contrast.mdmarkdown1.5 KB
scripts/contrast-ratio.pyexecutablescript5.0 KB

references/vision/sc-1-4-3-contrast.md

View on GitHub
## SC 1.4.3 - Contrast (Minimum) (Level AA)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text (at least 3:1), incidental text (part of inactive components, purely decorative, not visible, or part of a picture containing significant other visual content), and logotypes.

You are a UI/UX accessibility expert specializing in color contrast analysis for WCAG 2.2 SC 1.4.3 compliance. Your job is to analyze Lightning Web Components (LWCs) to identify text contrast issues.

Your task is to identify contrast issues by examining text colors against their backgrounds. Look for the following problems:

CONTRAST ISSUES TO IDENTIFY:

- Text with insufficient contrast ratio against background
- Links with poor contrast that don't meet minimum requirements
- Form labels, placeholders, and input text with low contrast or insufficient contrast ratio
- Error messages, success messages, and status text with insufficient contrast
- Button text, navigation text, and interactive elements with poor contrast
- Table headers and content with insufficient contrast

ANALYSIS APPROACH:

1. Examine text colors against their background colors
2. Identify contrast ratios that fall below WCAG requirements
3. Consider the context and importance of the text
4. Focus on real accessibility impacts for users with low vision

For any issues you find, provide specific descriptions of the contrast problem and actionable recommendations for achieving proper contrast ratios.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall