forcedotcom/sf-skills / skills/experience-accessibility-validate
experience-accessibility-validate
VerifiedUse 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`).
references/reviewers/sc-1-3-5-identify-input.md
View on GitHub## SC 1.3.5 - Identify Input Purpose (Level AA)
The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the Input Purposes for User Interface Components section, and the content is implemented using technologies with support for identifying the expected meaning for form input data.
## SC: 1.3.5 - Identify Input Purpose Only
Analyze the given file using the following framework:
Review the provided HTML and JS files for accessibility violations per WCAG 2.2 SC 1.3.5, 'Identify Input Purpose'.
Specific guidance on `autocomplete` for certain input fields:
- **Non-personal information fields** (e.g., search, quantity selectors): These fields should EITHER have no `autocomplete` attribute OR use `autocomplete="off"`. Using any other specific `autocomplete` token on these fields is a violation.
- **Security-sensitive fields** (e.g., security questions): These fields MUST use `autocomplete="off"`. If the `autocomplete` attribute is missing or has any other value, it is a violation.
- **Fields for non-primary users** (e.g., spouse\'s name, emergency contact information such as emergency contact name, emergency contact phone etc):
- The ABSENCE of an `autocomplete` attribute on these fields is PERMISSIBLE and IS NOT a violation.
- IMPORTANT Instruction: DO NOT suggest adding an `autocomplete` attribute (such as `autocomplete="off"` or any other token) if it is missing for these fields simply because they pertain to a non-primary user.
- A violation should only be flagged for these fields if an `autocomplete` attribute is EXPLICITLY PRESENT AND uses an incorrect token (i.e., a token not from the H98Procedure list that doesn\'t match the input\'s apparent purpose, and is not `off`).
Common violations to check:
- Missing `autocomplete` attributes on personal information fields
- Using generic "on/off" instead of specific tokens
- Using invalid or non-standard `autocomplete` tokens. `Autocomplete` tokens must exactly match the standardized values listed in the H98Procedure (e.g., `given-name`, `email`, `tel`). Combinations of tokens (e.g., "email home") or more specific, non-standard variations (e.g., "tel mobile" instead of `tel`) are incorrect.
- Using incorrect capitalization in `autocomplete` values
- Using invalid formats (like "email, home")
- Missing `autocomplete` on dynamic/conditional fields
Following are some sufficient techniques that a user can use to meet this success criterion:
- The objective of this technique is to programmatically link a pre-defined and published taxonomic term to the input, so that the inputs can also be machine-interpreted.
The technique works by adding the appropriate `autocomplete` token to each form field on the form to make the identified inputs programmatically determinable. This will help people with cognitive disabilities who may not immediately know the purpose of the field because the label used by the author is not familiar to them. When inputs have been programmatically assigned, third party plugins and software can manipulate these form fields to make them more accessible to people with cognitive disabilities.
For each form field that collects information about the primary user and corresponds to an autocomplete field, check the following:
- The form field has a valid and well-formed `autocomplete` attribute and value pair
- The purpose of the form field indicated by the label corresponds with the `autocomplete` token on the input
- The `autocomplete` token matches the standardized values:
- For name: `name`
- For first-name: `given-name`
- For last-name: `family-name`
- For email: `email`
- For phone number: `tel`, `tel-national`
- For birthdays: `bday`
- For addresses: `street-address`(for the full street address, potentially across multiple lines), `address-line1`(for the first line of the address, example "123, main st"), `address-level2`(for the city), `country`
- For credentials: `username`(for username), `current-password`(for the password ), `new-password` (for signing up)
- Non-personal information fields such as search, quantity selectors should omit `autocomplete` or use `off`
- Security-sensitive fields such as security questions should use `autocomplete="off"`
For each form field that collects information about the other users, check the following:
- Please disregard the absence of an `autocomplete` attribute for fields that collect information about individuals other than the primary user such as spouse's name, emergency contact name, emergency contact phone no etc. and do not flag this as a violation.
If they do not meet this success criterion, then flag this as a violation.
Rules to follow:
- Find all violations of SC 1.3.5 'Identify Input Purpose' in the provided HTML and JS files
- Focus on form inputs that collect user information
- If no changes or action are needed, then produce an empty list.
- Critically evaluate each field against the specific guidance above. Do not conclude 'no action is needed' or 'correctly implemented' if no violations found.
- 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |