📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "antigravity-bundle-aas-web-app-builder",
|
||||
"version": "13.5.0",
|
||||
"version": "13.6.1",
|
||||
"description": "Editorial \"AAS Web App Builder\" bundle for Claude Code from Antigravity Awesome Skills.",
|
||||
"author": {
|
||||
"name": "sickn33 and contributors",
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "agyb-aas-web-app-builder",
|
||||
"version": "13.5.0",
|
||||
"version": "13.6.1",
|
||||
"description": "Install the \"AAS Web App Builder\" workflow plugin from Antigravity Awesome Skills.",
|
||||
"author": {
|
||||
"name": "sickn33 and contributors",
|
||||
|
||||
+68
-60
@@ -1,81 +1,89 @@
|
||||
---
|
||||
name: ui-a11y
|
||||
description: "Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe."
|
||||
category: design
|
||||
risk: safe
|
||||
source: community
|
||||
description: Audit a component or page for accessibility issues and fix them
|
||||
risk: unknown
|
||||
source: https://github.com/bitjaru/styleseed/tree/main/engine/.claude/skills/ss-a11y
|
||||
source_repo: bitjaru/styleseed
|
||||
source_type: community
|
||||
date_added: "2026-04-08"
|
||||
author: bitjaru
|
||||
tags: [ui, accessibility, wcag, audit, styleseed]
|
||||
tools: [claude, cursor, codex, gemini]
|
||||
date_added: 2026-07-01
|
||||
license: MIT
|
||||
license_source: https://github.com/bitjaru/styleseed/blob/main/LICENSE
|
||||
---
|
||||
|
||||
# UI Accessibility Audit
|
||||
|
||||
## Overview
|
||||
|
||||
Part of [StyleSeed](https://github.com/bitjaru/styleseed), this skill audits components and pages for accessibility issues with an emphasis on the Toss seed's mobile UI patterns. It combines WCAG 2.2 AA checks with practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.
|
||||
|
||||
# Accessibility Audit
|
||||
## When to Use
|
||||
- Use when reviewing a page or component for accessibility regressions
|
||||
- Use when a StyleSeed UI looks polished but has uncertain keyboard or contrast behavior
|
||||
- Use when adding new interactive controls to a mobile-first screen
|
||||
- Use when you want a prioritized list of issues and fixable items
|
||||
|
||||
## Audit Areas
|
||||
Use this skill when you need audit a component or page for accessibility issues and fix them.
|
||||
|
||||
### Perceivable
|
||||
|
||||
- text contrast
|
||||
- non-text contrast for controls and graphics
|
||||
- alt text for images
|
||||
- labels for meaningful icons
|
||||
- no information conveyed by color alone
|
||||
## When NOT to use
|
||||
|
||||
### Operable
|
||||
- For general design system compliance review → use `/ss-review`
|
||||
- For Nielsen UX heuristics → use `/ss-audit`
|
||||
- For non-StyleSeed code (no `data-slot`, no semantic tokens) — assumes StyleSeed conventions
|
||||
- For runtime testing — this is a static code audit, not a screen-reader simulation
|
||||
|
||||
- touch targets at least 44x44px
|
||||
- keyboard reachability for all interactive controls
|
||||
- logical tab order
|
||||
- visible focus indicators
|
||||
- reduced-motion support for nonessential animation
|
||||
Target: **$ARGUMENTS**
|
||||
|
||||
### Understandable
|
||||
## Audit Criteria
|
||||
|
||||
- visible labels or `aria-label` on inputs
|
||||
- error text associated with the correct field
|
||||
- clear wording for errors and validation
|
||||
- document language set appropriately
|
||||
### WCAG 2.2 AA Compliance
|
||||
|
||||
### Robust
|
||||
#### 1. Perceivable
|
||||
- **Color contrast**: Text must meet 4.5:1 (normal) or 3:1 (large/bold text)
|
||||
- Check `text-muted-foreground` (#717182) on `bg-background` (#FFFFFF) = 4.6:1 (passes)
|
||||
- Check `text-brand` on white (verify contrast with your skin's brand color)
|
||||
- Flag any custom colors that don't meet ratio
|
||||
- **Non-text contrast**: UI controls/graphics must meet 3:1
|
||||
- **Text alternatives**: All `<img>` need `alt`, icons need `aria-label` when meaningful
|
||||
- **Color independence**: Don't convey info by color alone (add icons/text)
|
||||
|
||||
- semantic HTML where possible
|
||||
- correct use of ARIA when semantics alone are insufficient
|
||||
- no faux buttons or links without the right roles and behavior
|
||||
#### 2. Operable
|
||||
- **Touch targets**: Minimum 44x44px (`min-h-11 min-w-11`)
|
||||
- Common violation: `h-9` (36px) buttons — should be `h-11`
|
||||
- Icon buttons need explicit size: `w-11 h-11`
|
||||
- **Keyboard navigation**: All interactive elements must be keyboard-accessible
|
||||
- Tab order should be logical
|
||||
- `focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2`
|
||||
- **Motion**: Animations must respect `prefers-reduced-motion`
|
||||
```css
|
||||
@media (prefers-reduced-motion: reduce) {
|
||||
*, *::before, *::after {
|
||||
animation-duration: 0.01ms !important;
|
||||
transition-duration: 0.01ms !important;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
#### 3. Understandable
|
||||
- **Labels**: Form inputs must have visible labels or `aria-label`
|
||||
- **Error messages**: Form errors must be programmatically associated (`aria-describedby`)
|
||||
- **Language**: `<html lang="en">` (or appropriate language code for your project)
|
||||
|
||||
#### 4. Robust
|
||||
- **Semantic HTML**: Use appropriate elements (`<button>`, `<nav>`, `<main>`, `<header>`)
|
||||
- **ARIA**: Use Radix UI components (they handle ARIA automatically)
|
||||
- **Roles**: Custom interactive elements need proper `role` attributes
|
||||
|
||||
## Design System Token Reference
|
||||
|
||||
| Token | Minimum Contrast | Note |
|
||||
|-------|-----------------|------|
|
||||
| `--foreground` | 7:1+ | Body text — verify with your skin |
|
||||
| `--muted-foreground` | 4.5:1+ | Secondary text — verify with your skin |
|
||||
| `--brand` | 4.5:1+ | Accent — verify with your skin's brand color |
|
||||
| `--destructive` | 4.5:1+ | Error — verify with your skin |
|
||||
| `--success` | 3:1+ | Large text/icons only — verify with your skin |
|
||||
| `--warning` | 4.5:1+ | Warning text — some skins need a darker variant |
|
||||
|
||||
## Output
|
||||
|
||||
Return:
|
||||
1. Issues found, grouped by severity
|
||||
2. Safe autofixes that can be applied directly
|
||||
3. Items that need manual review or product judgment
|
||||
4. A short summary of the accessibility risk level
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Fix semantics before layering on ARIA
|
||||
- Use the design system tokens only if they still meet contrast requirements
|
||||
- Treat touch target failures as real usability defects, not polish issues
|
||||
- Prefer partial, verified fixes over speculative accessibility changes
|
||||
|
||||
## Additional Resources
|
||||
|
||||
- [StyleSeed repository](https://github.com/bitjaru/styleseed)
|
||||
- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-a11y/SKILL.md)
|
||||
1. **Issues found**: List with severity (Critical/Major/Minor)
|
||||
2. **Auto-fixes**: Apply fixes directly where possible
|
||||
3. **Manual review needed**: Flag items that need human judgment
|
||||
|
||||
## Limitations
|
||||
- Use this skill only when the task clearly matches the scope described above.
|
||||
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
||||
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|
||||
|
||||
- Use this skill only when the task clearly matches its upstream source and local project context.
|
||||
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
|
||||
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
|
||||
|
||||
Reference in New Issue
Block a user