threejs-accessibility — Claude Code skill for accessible 3D
The threejs-accessibility Claude Code skill makes Three.js interactions usable with keyboards and assistive technology. It applies when adding accessibility to 3D scenes and controls.
MIT 644 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a claude-codeWhat threejs-accessibility does
The skill guides changes to Three.js scenes so keyboard users and assistive technology can access their content. It calls for meaningful actions to use HTML controls and for essential scene information to have a text alternative. Charts need a table or summary; configurators need their options and selected values outside the canvas.
Its guidance covers focus order, keyboard controls for rotating and zooming, reduced-motion preferences, and announcements for significant state changes. It also addresses loading errors and devices without WebGL. Testing includes keyboard-only use, browser zoom, reduced motion, and a screen reader; untested assistive technology should be reported.
What it helps with
- add keyboard controls for rotating and zooming a 3D scene
- show configurator options outside the canvas
- provide a text alternative for chart data
- reduce nonessential motion when prefers-reduced-motion is active
Example prompts for the agent
- Make the controls in this Three.js scene usable with a keyboard.
- Add a text summary and data table for the chart rendered in canvas.
- Account for prefers-reduced-motion and devices without WebGL.
How to install threejs-accessibility
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-accessibility/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-accessibility/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a codex2Manually: put the files in place
.agents/skills/threejs-accessibility/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a cursor2Manually: put the files in place
.cursor/skills/threejs-accessibility/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-accessibility2Manually: put the files in place
.github/skills/threejs-accessibility/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-accessibilityManually: put the files in place
.devin/skills/threejs-accessibility/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about threejs-accessibility
How do I install threejs-accessibility in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-accessibility -a claude-code. The skill file is at ~/.claude/skills/threejs-accessibility/SKILL.md.
What does threejs-accessibility do?
It guides changes that make Three.js interactions accessible to keyboard users and assistive technology, including text alternatives and reduced-motion support.
How does the skill suggest testing a 3D scene?
Test keyboard-only use, browser zoom, reduced motion, and a screen reader. Also check the scene with WebGL unavailable.
Source text
SKILL.md · MIT
--- name: threejs-accessibility description: "Make Three.js interactions usable with keyboards, assistive technology, reduced motion, and non-3D fallbacks." --- # Accessible 3D Experiences Use the project's installed versions and existing architecture. These instructions supplement the user's task; they do not authorize unrelated changes or external actions. Identify what information and actions the 3D view communicates. Decorative scenes can be hidden from assistive technology; meaningful scenes need an accessible name/description and an equivalent way to obtain essential information. Expose meaningful actions as native HTML buttons, inputs, lists, and status text synchronized with the same application state. A canvas label alone does not make individual 3D objects accessible. For configurators, expose options and selected values outside the canvas; for charts, provide a table or textual summary. Implement visible focus, logical tab order, keyboard alternatives for rotate/zoom/reset/select, and an escape from captured interaction. Avoid hijacking page keys when focus is outside the viewer. Pointer-only drag should have an alternative when needed to accomplish the task. Respect prefers-reduced-motion and changes to that preference. Remove nonessential camera travel, parallax, auto-rotation, and flashing; offer stable states and pause controls. Use contrast, text labels, and shape in addition to color. Provide useful loading, failure, and unsupported-device HTML. Announce significant state changes without announcing every frame or hover. Test with keyboard alone, browser zoom, reduced motion, a screen reader where available, and WebGL unavailable. Report untested assistive technology explicitly. ## API reference Consult the [official documentation](https://www.w3.org/WAI/WCAG22/quickref/) for exact signatures and revision-specific behavior. If documentation access is unavailable, inspect installed types/source and state any remaining uncertainty.
© cesartevisual · MIT · cesartevisual/threejs-skills