gaia-validate-design-a11y

You can validate design accessibility by running the skill with your Figma target URL to check color contrast, semantic structure, and ARIA landmarks against WCAG 2.1 standards. It outputs a clear verdict to guide next steps.

WCAG 2.1 design validation checks color contrast, semantic structure, keyboard navigation, and ARIA landmark planning. It ensures design artifacts meet accessibility standards before development to reduce costly retrofits and improve user experience.

Yes, you need Figma API access and a WCAG 2.1 rubric to validate wireframes or UX documents. The skill uses these dependencies to analyze design artifacts and produce an accessibility verdict.

Yes, you can validate design accessibility using Figma, wireframes, or UX documents. The skill evaluates these artifacts against WCAG 2.1 standards and returns a verdict of APPROVE, REQUEST_CHANGES, or BLOCKED.

The best way to catch accessibility issues early is to validate design artifacts against WCAG 2.1 standards before implementation. This process checks contrast and navigation, producing a verdict to prevent costly retrofits.

Design-time accessibility validation focuses on design artifacts and produces verdicts like APPROVE, REQUEST_CHANGES, or BLOCKED. It addresses design-time concerns but requires Figma API access and a WCAG 2.1 rubric to function properly.