Skip to content
Back to skills

Ztx14 Curated Keyboard Parity Radix

ASecurity

Audit isometric primitives and custom figures so hover and pointer behavior has a complete keyboard, focus and semantic counterpart.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
designtestingapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill ztx14-curated-keyboard-parity-radix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ztx14 Curated Keyboard Parity Radix?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ztx14 Curated Keyboard Parity Radix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-ztx14-curated-keyboard-parity-radix/badge)](https://www.skillsdirectory.com/skills/realjustawall-ztx14-curated-keyboard-parity-radix)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ztx14-curated-keyboard-parity-radix
description: Audit isometric primitives and custom figures so hover and pointer behavior has a complete keyboard, focus and semantic counterpart.
---

# Preserve keyboard and screen-reader behavior in isometric controls

> Curated implementation skill. Inspect the installed project and actual component source before changing behavior. Do not assume latest APIs are installed. Preserve unrelated files and existing component ownership.

## Principle
The site's primitives are documented as Radix-based, but custom additions can still break accessible behavior. Verify the actual installed component rather than assuming a visual control is accessible.

## Review steps
1. Use native button/input semantics or preserve the existing Radix primitive instead of inventing clickable `div` controls.
2. Ensure visible focus follows keyboard movement and does not disappear under isometric depth/outline styling.
3. For custom canvas/SVG figures, provide a semantic DOM control or a keyboard-operable selection model, with accessible name and state.
4. Mirror every essential pointer-only action with keyboard activation and a touch-friendly path. Dragging must have a non-drag alternative when needed.
5. Keep `aria-pressed`, `aria-selected`, `aria-expanded`, and disabled state synchronized with actual behavior.
6. Avoid noisy screen-reader announcements for continuous motion; announce meaningful state transitions only.

## Validate
Tab order, Enter/Space, arrow navigation where appropriate, focus-visible styling, zoom/reflow and screen-reader smoke tests. Use automated audit as a first pass, not as proof of full compliance.

## Primary references
- [storybook-a11y](https://storybook.js.org/docs/writing-tests/accessibility-testing)
- [storybook-interactions](https://storybook.js.org/docs/writing-tests/interaction-testing)
- [wcag22](https://www.w3.org/TR/WCAG22/)
- [isometric](https://isometric.buildlab.in/llms.txt)

## Completion evidence
- State what was inspected, what changed, and which checks actually ran. Never report unrun tests or unverified browser behavior as passing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.