Last updated: May 21, 2026
Current approach
The current site uses semantic page structure, labeled controls, visible focus styles through browser and Tailwind defaults, and responsive layouts.
Audio tools should remain usable without creating an account or navigating complex project screens.
SoundSlicr tries to keep pages focused: one route for one task, with clear headings and predictable navigation so visitors can find the tool they came for.
Known limitations
Some audio workflows depend on browser-native file pickers, audio playback controls, and microphone permission dialogs.
Waveform-based workflows may require additional accessibility review before launch.
Assistive technology support can vary by browser and device, especially for media controls and permission prompts that are implemented by the browser.
How to report an accessibility issue
Send accessibility feedback via /contact with the route, device, browser, and assistive technology you were using.
Include what you expected to happen, what happened instead, and whether the issue is blocking or merely inconvenient. If possible, include steps to reproduce using a non-sensitive file.
Feedback
Accessibility issues can be sent through the contact page with the route, device, browser, assistive technology, and a short description of the issue.