Audit and improve timepicker-ui documentation accessibility against WCAG 2.2 AA.
npx skills add https://github.com/pglejzer/timepicker-ui --skill docs-a11y
Please help me install this Agent Skill. Skill: docs-a11y Source: https://github.com/pglejzer/timepicker-ui/tree/main/.claude/skills/docs-a11y Command: npx skills add https://github.com/pglejzer/timepicker-ui --skill docs-a11y
Audit and improve the accessibility of the timepicker-ui documentation site (docs-app/), ensuring keyboard operability, proper landmarking, heading order, skip links, focus management, color contrast, alt text, ARIA on custom components, and adherence to Radix usage and reduced motion, aligned with WCAG 2.2 AA. The skill acts as an approval gate, orchestrating the docs-accessibility subagent rather than performing all fixes itself.
Initiate an audit workflow on the docs-app/ to produce a prioritized plan and apply fixes.
High-intent search queries and answers about installing and using this skill.
You can audit a Next.js documentation site for WCAG 2.2 AA compliance by orchestrating a subagent to evaluate landmarks, keyboard navigation, focus management, color contrast, and ARIA usage, then applying the approved fixes.
Fixing keyboard navigation and focus management issues in docs requires auditing interactive components to ensure proper tab order, visible focus states, and correct Radix UI usage to meet WCAG 2.2 AA standards.
This accessibility audit specifically covers only the docs-app directory and its Next.js documentation site. The underlying component library source code located in the library directory is strictly outside the audit scope.
Yes, you can check ARIA usage and color contrast on documentation pages by running an audit workflow that evaluates names, contrast ratios, content structure, and media alternatives to ensure they meet accessibility standards.
To add skip links and enforce reduced motion preferences in a Next.js docs site, an audit evaluates structural landmarks and motion responsiveness, generating a prioritized plan to apply the necessary accessibility fixes.
The docs accessibility audit requires an approval gate to orchestrate the subagent safely through audit, approve, and apply stages, ensuring you review all proposed structural and WCAG 2.2 AA compliance changes before modification.
jens-wedinAnnotate designs into developer-ready accessibility requirements with a reusable template.
lloydchangAudit multi-cloud security events and generate compliance reports.
boparaiamritAudit frontend UI accessibility against WCAG standards and generate remediation guidance.
hschneAudit web pages for WCAG 2.2 AA violations using axe-core and Lighthouse.
