Maintained by Mayer · Last updated 2026-09-28
OnlinePitchChanger.com aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We have not completed a full audit, so we do not claim that the site conforms. This statement reports what we actually checked on 2026-09-28, what worked, the problems we found and how to tell us about a barrier.
Our target: WCAG 2.2 Level AA
WCAG 2.2 is the current accessibility standard from the World Wide Web Consortium (W3C); you can read it in full at W3C: WCAG 2.2. Level AA covers things like keyboard access, visible focus, text contrast, labels for controls and pages that work on small screens without sideways scrolling. Because of the issues listed below, the pages we tested do not yet fully meet Level AA.
What we checked on 2026-09-28
We tested six live pages: the home page and five tools chosen to cover each kind of control (file tools, a key picker, the YouTube player, a microphone test and a calculator). Each page was opened in Microsoft Edge 152.0.4191.53 in headless mode and checked in four ways:
- Automated rules: axe-core 4.13, limited to the WCAG 2.0, 2.1 and 2.2 Level A and AA rules. Automated tools find only part of the possible problems.
- Keyboard: we pressed Tab until focus had gone through the whole page and back to the top, recording every stop, whether focus became visible and whether it ever got stuck.
- Labels: we listed every button, field, menu and slider in the tool and checked that each has a name a screen reader can announce.
- Small screens: we loaded each page at 360 px and at 320 px wide (the width WCAG uses for its reflow test) and checked for sideways scrolling.
| Page | Keyboard: full Tab cycle, no trap | Every tool control named | Contrast (axe) | Sideways scroll at 360 / 320 px | Other findings |
|---|---|---|---|---|---|
| Home page (Online Pitch Changer) | 81 stops, returned to the top | Yes | None flagged | No | Scrollable table without its own keyboard focus; some text below 14 px at phone width |
| Audio Pitch Changer | 70 stops, returned to the top | Yes (21 controls) | 14 links below 4.5:1 | No | Semitone number field: thin dotted focus outline only |
| Online Key Changer | 78 stops, returned to the top | Yes (34 controls) | 16 links below 4.5:1 | No | – |
| YouTube Pitch Changer | 72 stops, returned to the top | Yes (17 controls) | 14 links below 4.5:1 | No | Link field: thin dotted focus outline only |
| Vocal Range Test | 58 stops, returned to the top | Yes (8 controls) | 15 links below 4.5:1 | No | – |
| Semitone Calculator | 78 stops, returned to the top | Yes (8 controls) | 15 links below 4.5:1 | No | – |
What worked
- On all six pages the first Tab stop is a “Skip to content” link, and Tab went through every link and control to the end of the page and back to the top without getting stuck.
- Every visible control in the five tools has an accessible name, including the −1 / +1 semitone buttons and the waveform, which is announced as a “Playback position” slider with the time as text.
- Tool buttons, menus and links show a visible focus outline when reached with the keyboard.
- No page scrolled sideways at 360 px or 320 px. On the five tool pages, no paragraph, list, label, button or table text was smaller than 14 px at those widths.
Known issues
| Issue | What we found | WCAG 2.2 criterion | Where | Status |
|---|---|---|---|---|
| Link colour contrast | Links in the site theme’s orange-red colour (#f53500) measure 3.6:1 against the light page backgrounds, below the 4.5:1 minimum for normal-size text. | 1.4.3 Contrast (Minimum) | All five tool pages we tested | Open |
| Links shown by colour only | Inside paragraphs, those links are not underlined and differ from the surrounding text by colour alone (2.65:1). | 1.4.1 Use of Color | Same pages | Open |
| Weak focus outline on text fields | Tool buttons show a 3 px outline when reached with the keyboard, but the YouTube link field and the semitone number field show only a thin dotted outline that is hard to see. | 2.4.7 Focus Visible | YouTube Pitch Changer, Audio Pitch Changer | Open |
| Scroll to Top button | The theme’s Scroll to Top button is in the keyboard order but showed no visible change when focused. | 2.4.7 Focus Visible | All six pages | Open |
| Homepage table and small text | One wide table scrolls sideways inside its box but has no keyboard focus of its own. Edge reached it with Tab; other browsers may not. Some text on the page is smaller than 14 px on a phone. | 2.1.1 Keyboard | Home page | Open |
This page itself uses darker, underlined links so it does not repeat the link-contrast problem.
Limits that come from the tools themselves
- Changing pitch and testing a voice are listening and singing tasks. We can make the controls, instructions and results accessible, but the task itself depends on hearing or producing sound.
- Waveforms are drawn pictures of the sound. The playback position they show is also given as time in text through the “Playback position” slider, but the shape of the sound is visual only.
- Permission prompts for the microphone, as used by the Vocal Range Test, and for sharing a tab’s sound are drawn by your browser, not by this site, so their accessibility depends on the browser.
- The YouTube Pitch Changer uses YouTube’s embedded player. Its controls and captions are provided by YouTube. Live pitch change works only in Chrome or Edge on a computer, because phones and other browsers cannot share a tab’s sound with a web page.
- Files are chosen with your system’s own file dialog. In the file tools we tested, such as the Audio Pitch Changer, the file chooser is a standard file field that Tab reaches, so dragging a file with a mouse is not the only way to add one.
What we have not tested yet
We have not yet tested with screen readers (such as NVDA, JAWS, VoiceOver or TalkBack), on real phones and tablets, in Safari or Firefox, or with browser zoom and text spacing settings. We also have not tested the microphone and tab-sharing steps with assistive technology, or the other tool pages and guides. The six pages above are a sample, not the whole site. How the tools were tested for accuracy is described on How it works.
Report a barrier
If something on the site is hard or impossible to use, please email support@vocaltoollab.com. Reports go to Mayer, who runs the site. It helps to include:
- the page or tool address;
- what you were trying to do and what happened instead;
- your browser and device;
- any assistive technology you use, if you are comfortable sharing it.
You do not need to tell us about a disability to report a problem. If a tool does not work for you, tell us what you need and we will try to help another way, for example by explaining the steps or a result in text. Other ways to reach us are on the Contact page, and how your files are handled while you use a tool is on the Data Security page.
Updates to this statement
This statement is updated when pages are retested or issues are fixed. Each update changes the date at the top, and the tables above always show the results of the latest test. The main tool is on the home page.