Skip to content

forcedotcom/sf-skills / 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.mdmarkdown4.5 KB
references/reviewers/sc-1-3-1-i-lists.mdmarkdown3.6 KB
references/reviewers/sc-1-3-1-ii-tables.mdmarkdown3.2 KB
references/reviewers/sc-1-3-1-iii-form-labels.mdmarkdown4.5 KB
references/reviewers/sc-1-3-1-iv-regions.mdmarkdown1.7 KB
references/reviewers/sc-1-3-1-v-groups.mdmarkdown6.8 KB
references/reviewers/sc-1-3-5-identify-input.mdmarkdown5.3 KB
references/reviewers/sc-1-4-3-contrast.mdmarkdown7.6 KB
references/reviewers/sc-2-1-1-keyboard.mdmarkdown5.8 KB
references/reviewers/sc-2-4-4-link-purpose.mdmarkdown2.7 KB
references/reviewers/sc-2-4-6-headings-labels.mdmarkdown4.6 KB
references/reviewers/sc-2-5-1-pointer-gestures.mdmarkdown3.1 KB
references/reviewers/sc-2-5-2-pointer-cancellation.mdmarkdown4.1 KB
references/reviewers/sc-2-5-3-label-in-name.mdmarkdown6.5 KB
references/reviewers/sc-2-5-7-dragging-movement.mdmarkdown3.6 KB
references/reviewers/sc-3-2-1-on-focus.mdmarkdown3.7 KB
references/reviewers/sc-3-2-2-on-input.mdmarkdown5.1 KB
references/reviewers/sc-3-3-1-error-identification.mdmarkdown8.9 KB
references/reviewers/sc-3-3-2-labels-instructions.mdmarkdown3.3 KB
references/reviewers/sc-3-3-3-error-suggestion.mdmarkdown5.4 KB
references/reviewers/sc-4-1-2-i-name.mdmarkdown14.0 KB
references/reviewers/sc-4-1-2-ii-role.mdmarkdown5.7 KB
references/reviewers/sc-4-1-2-iii-value.mdmarkdown6.0 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

references/reviewers/sc-1-3-1-iv-regions.md

View on GitHub
## SC 1.3.1 - Info and Relationships (Level A)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

## SC: 1.3.1 (iv) - Info And Relationships - Regions (A)

Review the provided HTML and JS files for accessibility violations per WCAG 2.2 SC 1.3.1 (iv), 'Info and Relationships'
(Only regions from this rule should be considered). For all regions on the page, ensure that any information conveyed through presentation is programmatically determinable in order to determine if they meet SC 1.3.1 (iv).
If they do not meet this success criterion, flag it as a violation.

Rules to follow:

- Find all violations of SC 1.3.1 'Info and Relationships - Regions' in the provided HTML and JS files.
- Do not worry about violations of SC 1.3.1 that are not specific to regions. These will be handled by other reviewers.
- Use semantic HTML elements (`<header>`, `<nav>`, `<main>`, `<aside>`, `<footer>`, `<section>`) to mark up regions. There cannot be more than one `<main>` element that does not have a hidden attribute specified.
- When semantic elements cannot be used, use ARIA landmark roles (`role="banner"`, `role="navigation"`, `role="main"`, `role="complementary"`, `role="contentinfo"`, `role="region"`).
- Each region should have a descriptive label or heading that identifies its purpose.
- Regions should be properly nested and not overlap.
  - For each issue found, provide a separate, detailed report.
- Keep issues concise, avoid duplicated issues or unnecessary or non-applicable problems.
- Assume that any imported functionality works as expected and was already analyzed.
- Components do not supplement or provide global functionalities.
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: 323kUpdated 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