PixiJS accessibility: screen reader and keyboard navigation for v8 apps
Add screen-reader and keyboard navigation to PixiJS v8 apps — AccessibilitySystem, shadow DOM overlay, tab order, ARIA
- What
- Add screen-reader and keyboard navigation to PixiJS v8 apps — AccessibilitySystem, shadow DOM overlay, tab order, ARIA
- Cost
- Free
- Needs
- a PixiJS v8 app (web or mobile canvas); nothing else — the skill is guidance, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @pixijs's official guide for making PixiJS v8 canvas apps accessible: the AccessibilitySystem creates an invisible shadow-DOM overlay positioned over accessible containers so assistive technology can discover and activate them — per-container properties (`accessible`, `accessibleTitle`, `accessibleHint`, `accessibleText`, `accessibleType`, `tabIndex`, `accessibleChildren`, `accessiblePointerEvents`), init options (`enabledByDefault`, `debug`, `activateOnTab`, `deactivateOnMouseMove`), custom tab order, programmatic control (`setAccessibilityEnabled`, static defaults), and interaction dispatch (shadow-div activation fires `click`/`pointertap`/`tap`; focus fires `mouseover`/`mouseout`). Includes a common-mistakes section: expecting the overlay without a Tab press, `accessible` without `accessibleTitle`, mouse movement deactivating the overlay, and missing the accessibility extension import in custom builds. By @pixijs, listed here with credit to its creator. Honest caveats: the AccessibilitySystem requires the main thread (not available in a Web Worker); on mobile it activates through a hidden touch hook; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
PixiJS accessibility is a free Muse skill and official guide for making PixiJS v8 canvas apps accessible. The AccessibilitySystem creates an invisible shadow-DOM overlay positioned over accessible containers so assistive technology can discover and activate them, with per-container properties for accessible title, hint, tab order and ARIA support.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 83760c6Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a PixiJS v8 app (web or mobile canvas); nothing else — the skill is guidance, no accounts or keys required Install "PixiJS accessibility: screen reader and keyboard navigation for v8 apps" for me. Give my agent @pixijs's pixijs-accessibility skill: screen-reader and keyboard navigation via the AccessibilitySystem — invisible shadow-DOM overlay, per-container accessible properties and tabIndex, init options (enabledByDefault, debug, activateOnTab, deactivateOnMouseMove), programmatic control, interaction dispatch, and the common-mistakes checklist. Repository: https://raw.githubusercontent.com/pixijs/pixijs-skills/83760c6f53462ca9cecd68055041f5a8c94758ce/skills/pixijs-accessibility/SKILL.md Pinned version: install the code at commit 83760c6f53462ca9cecd68055041f5a8c94758ce exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "pixijs-accessibility". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a guide; wire the accessible properties on your containers). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 83760c6 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 11, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.