Accessibility
String Warrior is built to work for every string player — including those who navigate by keyboard, use a screen reader, or need visual, low-audio, or high-contrast alternatives. This page describes what we've done and how to reach us if something gets in your way.
Our commitment
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the site. Accessibility is part of how every page and tool is built and tested, not an afterthought — and the whole site works with no account, no app, and no paywall, in any modern browser.
We know we won't get everything right. If any part of String Warrior is hard to use with your assistive technology, tell us and we'll fix it — see how to reach us below.
What's built in
- Keyboard navigation — every interactive control is reachable and operable with the keyboard, each page opens with a “Skip to main content” link, and focus is always visible.
- Screen-reader support — semantic headings and landmarks, descriptive labels on controls, and plain-language descriptions of every chord voicing (for example, “E muted, A 3rd fret, D 2nd fret, G open, B 1st fret, E open”) so diagrams are not image-only.
- A spoken, live-announcing tuner — the tuner announces the detected note and whether you're sharp or flat through an ARIA live region, so you don't have to watch the needle.
- A visual metronome — the metronome flashes in time with the beat, so the tempo is visible, not only audible.
- Contrast-checked themes — every colour theme (including the default) is validated in our build so text and interface colours meet WCAG contrast thresholds; more than twenty themes let you pick what reads best for you.
- Left-handed diagrams — a single toggle mirrors every chord and fretboard diagram for left-handed players.
- Respecting your system settings — the site honours reduced-motion and light/dark preferences, and text reflows and scales rather than breaking when you zoom.
- Works without JavaScript — core reference content (chords, scales, theory) is present in the page for readers and crawlers even before any script runs.
Standards & testing
Every page is checked in continuous integration for common accessibility problems — using automated axe-core audits, colour-contrast validation of each theme, and checks for a single main heading, labelled controls, and stable layout (no unexpected shifts). Automated testing can't catch everything, so we also review by keyboard and screen reader.
This statement applies to stringwarrior.com and is reviewed as the site changes.
Tell us about a barrier
If you hit an accessibility barrier — a control you can't reach, a diagram your screen reader can't read, text that's hard to see — please let us know what happened and what you were using, and we'll work to fix it. You can reach us through the details on our About page. We treat accessibility issues as bugs, not feature requests.