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-ii-tables.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 (ii) - Tables Only

For every `<table>` element in the source, apply the criteria below and produce one fix entry per violation. Other SC 1.3.1 concerns (lists, regions, form-labels, groups) are out of scope — they are owned by sibling reviewers.

### Structural criteria

For each `<table>`, verify:

- Contains at least one `<tr>` element.
- Each `<tr>` contains one or more cells appropriate to its content: `<th>` for headers and `<td>` for data. A header-only row containing only `<th>` cells is valid.
- Header content (if present) is marked up with `<th>` (typically in the first `<tr>` or inside `<thead>`).
- All data content is inside `<td>` cells; all header content is inside `<th>` cells.
- The table is either a recognizable data table (`<tr>`, `<td>`, plus `<th>` when headers exist) or a layout table (no relationships across rows and columns).

### Header-association criteria

- **Simple data tables** with headers in the first row or column: `<th>` without `scope` is sufficient.
- **Simple data tables** with headers NOT in the first row or column: every `<th>` must carry a valid `scope` (`row` / `col` / `rowgroup` / `colgroup`) matching the header's role.
- **Irregular tables** with headers spanning rows or columns may use explicitly defined row or column groups with `scope="rowgroup"` or `scope="colgroup"`. Do not require `id` + `headers` solely because a table uses `rowspan`, `colspan`, or multiple header levels when groups and `scope` express the relationships.
- **Complex tables** whose data-cell relationships are too complex to identify using `<th>` alone or `<th>` with `scope` must provide programmatically determinable header-to-cell associations. Use `id` + `headers` attributes (see H43), or simplify the table so `<th>` and `scope` can express the relationships. Complex cases include tables whose headers repeat or change partway through the table or whose data cells are associated with three or more headers. When `id` + `headers` is used, verify that every `<th>` `id` is unique within the component and every id in a cell's `headers` attribute resolves to an actual `<th>`.

### Accessible-name criterion

Providing an accessible name (via `aria-label`, `aria-labelledby`, or `<caption>`) is a best practice but not a violation when absent. Do not produce a fix entry purely for a missing accessible name.

### Layout-table criterion

When a table's content has no row/column relationships, classify it as a layout table. Layout tables should not use `<th>` or `scope`; emit a fix entry if they do.

### Output contract

For each violation, produce one entry with: file + line number, which criterion above failed, and the corrected markup snippet. If every table satisfies the criteria, produce an empty list.

- 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