sounds-on-the-web_skill

This skill helps reviewers audit audio feedback in UI for accessibility and UX, outputting file:line findings to guide improvements.
  • TypeScript

253

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill raphaelsalaja/userinterface-wiki --skill sounds-on-the-web

  • SKILL.md7.3 KB

Overview

This skill audits TypeScript UI code for audio feedback best practices and accessibility. It flags issues like missing visual equivalents, absent user controls for sounds, improper implementation details, and inappropriate or mismatched sound usage. The tool reports findings in file:line format with rule IDs and produces a concise summary of counts and severities.

How this skill works

I scan the supplied files or file patterns and check each audio-related site against a curated rule set: accessibility, appropriateness, implementation, and weight-matching. For every violation I emit a file:line entry with a rule identifier and a short description. After listing findings I generate a summary table showing rule counts and severity to prioritize fixes.

When to use it

  • Code review for UI changes that introduce or modify sounds
  • Accessibility audits focused on non-visual feedback
  • Pre-release checks for new audio assets or sound logic
  • Design reviews to validate whether an interaction should have sound
  • Audits of preference/settings and user controls for media

Best practices

  • Always provide a visual equivalent for any auditory cue and never rely on sound as the sole feedback
  • Expose a clear user preference to enable/disable sounds and honor reduced-motion/media preferences
  • Preload and reuse audio objects, reset currentTime before play, and keep default volume subtle
  • Avoid sounds on high-frequency interactions (typing, hover, scrolling); reserve sound for confirmations, errors, and important notifications
  • Match sound weight and duration to the action’s importance and duration; choose gentle, informative tones over punitive or excessively loud cues

Example use cases

  • Scan a components/ directory to find keystroke or hover sounds and flag high-frequency violations
  • Audit sound player utilities for missing preload, volume control, or currentTime reset implementations
  • Inspect settings and providers to ensure a user toggle for sound and respect for prefers-reduced-motion
  • Review checkout or upload flows to confirm appropriate confirmation sounds with visual indicators
  • Evaluate new sound assets to ensure duration and intensity match the corresponding action

FAQ

Findings are emitted as file:line - [rule-id] description entries, followed by a summary table of counts and severities.

Can this tool detect runtime preference checks like prefers-reduced-motion?

Yes. It flags missing checks for prefers-reduced-motion or missing user-controlled sound toggles as accessibility issues.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational