Pixijs accessibility
Skill Xopoko/plug-n-skills/plugins/pixijs/skills/pixijs-accessibility
Ready-to-install skills and plugins for Codex, Claude Code, and AI coding agents: practical workflows for app delivery, architecture, research, design, and agent tooling.
npx -y skills add Xopoko/plug-n-skills --skill pixijs-accessibilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use for PixiJS v8 accessibility: AccessibilitySystem, screen reader overlays, keyboard navigation, accessibleTitle, accessibleHint, tabIndex, roles, activation settings.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.2 KB, as published. Nobody here has run it
Use this when PixiJS content needs screen reader, keyboard, role, or focus support.
Rules
- Enable and configure the
AccessibilitySystemat the application/renderer level when needed. - Add per-object accessibility metadata such as title, hint, role, and tab index.
- Keep keyboard focus order intentional; do not mirror every decorative object into accessibility overlays.
- Pair accessible canvas objects with equivalent semantic HTML when complex interaction exceeds Pixi's accessibility layer.
- Test with keyboard and a screen reader, not only visual inspection.
Deep Reads
- Full accessibility options and per-container examples: references/details.md
- DOM overlays for semantic UI:
pixijs-scene-dom-container - Input handling:
pixijs-events
Common Fixes
- Screen reader sees noise: mark only meaningful interactive or informative objects.
- Keyboard focus order is wrong: set tab order deliberately.
- Overlay position wrong: check scene transforms and renderer resize behavior.