skills.rest
pglejzer
pglejzerCOMMUNITY
Explore all skills by this author →
GitHub

a11y

Audits and improves accessibility of timepicker-ui app/src components per WCAG 22 AA and WAI-ARIA Authoring Practices with an approval-gated workflow.

95|20|Updated Oct 27, 2020
Search Tags:#workflow#accessibility#a11y#audit#aria#keyboard-navigation
One-click install
npx skills add https://github.com/pglejzer/timepicker-ui --skill a11y-pglejzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y
Source: https://github.com/pglejzer/timepicker-ui/tree/main/.claude/skills/a11y
Command: npx skills add https://github.com/pglejzer/timepicker-ui --skill a11y-pglejzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure the timepicker-ui picker is fully usable by keyboard and assistive technology by providing a structured audit-and-apply workflow and an approval gate. It explicitly scopes work to app/src and clarifies that docs-a11y is out of scope.

Core Features & Use Cases

  • WCAG 2.2 AA and WAI-ARIA Authoring Practices compliant audits for the timepicker-ui components (clock, wheel, modal, inputs).
  • Per-area audit scope (clock, wheel, range, timezone, modal, keyboard) with an approval-driven apply flow.
  • Gatekeeping for accessibility changes to ensure safe, reviewable improvements before deployment.

Quick Start

Run an accessibility audit on the timepicker-ui app/src and apply approved fixes to improve keyboard operability and ARIA labeling.

Frequently Asked Questions about a11y

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit timepicker-ui components for WCAG 2.2 AA compliance?▼

Audit timepicker-ui components for WCAG 2.2 AA compliance by scoping work to app/src and evaluating clock, wheel, and modal areas against WAI-ARIA Authoring Practices. An approval gate ensures changes are reviewed before deployment.

What is the audit-approve-apply workflow for accessibility improvements?▼

The audit-approve-apply workflow is a structured process where timepicker-ui components are audited, changes are held at an approval gate for review, and approved fixes are applied to ensure safe, reviewable modifications.

Can I use this to fix keyboard navigation and ARIA labeling in a timepicker?▼

Yes, you can fix keyboard navigation and ARIA labeling in a timepicker by applying approved fixes from the accessibility audit. The process includes safety checks for ARIA roles, live regions, and focus management to ensure operability.

Does the timepicker-ui accessibility audit cover documentation?▼

No, the timepicker-ui accessibility audit does not cover documentation. The scope is explicitly limited to the app/src directory, and docs-a11y is out of scope for this workflow.

What are the limitations when improving timepicker-ui accessibility?▼

Limitations when improving timepicker-ui accessibility include a strict scope limitation to the app/src directory, excluding documentation. All changes must also pass an approval gate and safety checks before application.

Related Skills

Explore More Software Engineering Skills→
pglejzerpglejzer
95

docs-a11y

Audit and improve timepicker-ui documentation accessibility against WCAG 2.2 AA.

Community
Advanced
tom-xstom-xs

a11y-playwright-testing

Automate accessibility testing with Playwright and axe-core for WCAG 2.1 AA compliance.

Community
Advanced
zivtechzivtech
1

a11y-critic

Review code accessibility design for ARIA patterns and focus management.

Official
Advanced
thiagoooo34252thiagoooo34252
1

engineer-accessibility

Scan web applications for WCAG 2.2 violations using axe-core.

Community
Advanced