pixijs-accessibility

Add screen-reader and keyboard accessibility to PixiJS v8 canvas interfaces.

Updated Mar 13, 2022
One-click install
npx skills add https://github.com/alexkafer/alexkafer-web --skill pixijs-accessibility-alexkafer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pixijs-accessibility
Source: https://github.com/alexkafer/alexkafer-web/tree/main/.agents/skills/pixijs-accessibility
Command: npx skills add https://github.com/alexkafer/alexkafer-web --skill pixijs-accessibility-alexkafer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PixiJS canvas-based UIs can be difficult to use with screen readers and keyboard-only navigation, because interactive content may not be discoverable or reachable through a semantic DOM.

Core Features & Use Cases

  • Keyboard navigation and focus: Enables tab order via tabIndex and controls when accessibility becomes active (for example, on Tab key press or immediately).
  • Screen reader labeling: Provides accessible names and hints using accessibleTitle, accessibleHint, and accessibleText for each interactive container.
  • Shadow DOM overlay activation: Creates an invisible overlay layer positioned over accessible containers so assistive technologies can discover and activate them.
  • Mobile activation behavior: Supports a hidden touch-hook approach where screen-reader focus activates the session.
  • Common use case: Use it when building a game UI or interactive visualization in PixiJS and you need accessible buttons, dialogs, and navigational controls to be operable without a mouse.

Quick Start

Enable the PixiJS AccessibilitySystem, then mark a Sprite as accessible with an accessibleTitle, set eventMode and tabIndex for keyboard order, and handle pointertap to run your action.

Frequently Asked Questions about pixijs-accessibility

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

FAQPage Schema
How do I make PixiJS canvas content accessible to screen readers?▼

Making PixiJS canvas content accessible requires an accessibility overlay layer positioned over interactive containers so assistive technologies can discover and activate them via shadow DOM focus.

How do I add keyboard navigation and tab order to a PixiJS game UI?▼

Adding keyboard navigation to a PixiJS game UI involves setting `tabIndex` on interactive containers and configuring eventMode to handle pointertap events, enabling tab-ordered interactions inside canvas scenes.

Can screen readers discover interactive buttons inside a PixiJS canvas?▼

Screen readers can discover interactive PixiJS buttons when each container is marked with `accessibleTitle`, `accessibleHint`, and `accessibleText` metadata to provide semantic labeling for assistive technology.

Does PixiJS v8 support mobile screen reader activation for canvas apps?▼

PixiJS v8 supports mobile screen reader activation through a hidden touch-hook approach where focusing the hidden overlay activates the accessibility session for touch-based assistive technology.

What is the best way to configure accessible metadata for PixiJS dialogs and menus?▼

Configuring accessible metadata for PixiJS dialogs and menus involves setting per-container properties like `accessibleTitle` and `accessibleType` through the AccessibilitySystem options to ensure proper semantic discovery.

Why is my PixiJS canvas not keyboard accessible without a mouse?▼

PixiJS canvas interfaces lack keyboard accessibility because interactive content is not discoverable through semantic DOM without an accessibility overlay layer providing shadow DOM focus and dispatched pointer events.