BPMKeyFinder.com is committed to making its tools and educational content accessible to the widest possible range of users, including people with disabilities. This statement explains our current accessibility status, what we have implemented, known limitations, and how to contact us if you encounter a barrier.
Our Commitment
We believe that anyone who works with music — DJs, producers, remixers, songwriters, music educators — deserves access to audio analysis tools and educational content regardless of disability, device, or technical setup.
BPMKeyFinder.com aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — the internationally recognised standard for web accessibility published by the World Wide Web Consortium (W3C).
Accessibility is an ongoing commitment. Identified barriers are addressed through our own review or user feedback.
Current Accessibility Status
BPMKeyFinder.com is partially conformant with WCAG 2.1 Level AA. Known gaps are disclosed below.
What We Have Implemented
Keyboard navigation. Core site navigation — menus, links, and page structure — is fully accessible via keyboard. Tab to navigate, Enter to activate links and buttons.
File upload accessibility. The file upload control is a standard HTML file input element with an associated label, accessible via keyboard and compatible with screen readers. Users who cannot use a mouse can activate the file upload control using Tab and Enter or spacebar.
Result accessibility. All analysis results — BPM value, key name (e.g. “A minor”), and Camelot Wheel notation (e.g. “8A”) — are returned as text. These results are fully accessible to screen readers. Users who are deaf or hard of hearing can use the tool and read the results without any hearing required.
Text readability. Body text at minimum 16px with sufficient line spacing. Heading levels (H1, H2, H3) follow correct hierarchical order throughout, allowing screen readers to navigate content structure logically.
Colour contrast. Text and background colour combinations meet or exceed WCAG 2.1 Level AA minimum ratios — 4.5:1 for normal text, 3:1 for large text.
Descriptive link text. Links describe their destination — no generic “click here” or “read more.”
Alt text on images. Meaningful images include descriptive alt text. Decorative images use empty alt attributes.
Responsive design. The site adapts to all screen sizes without horizontal scrolling at 200% zoom.
No auto-playing media. No audio plays automatically without user action.
Page titles. Every page has a unique, descriptive title tag.
Skip navigation link. A “Skip to content” link is available at the top of every page.
A Note on Deafness and Hard of Hearing Users
The BPM Key Finder tool accepts an uploaded audio file and returns text results. This means:
Deaf and hard of hearing users can fully use the core tool. The BPM value, musical key, and Camelot Wheel notation are all returned as text on screen. No audio playback is required to receive the analysis results. A deaf music producer, DJ, or educator can upload a file and read the BPM, key, and Camelot code without any audio interaction.
Key verification by ear requires hearing. The tool documentation recommends verifying key detection results by ear — particularly for music with key changes or modal content where algorithmic accuracy may be lower. Users who cannot hear cannot perform this ear verification. For critical professional use (live DJ set transitions, studio mashup work), deaf users should use additional verification methods such as visual pitch analysis tools or consultation with a hearing colleague.
Camelot Wheel and harmonic mixing content is fully accessible. All educational content about the Camelot Wheel, harmonic mixing rules, and music theory is text-based and fully accessible to screen readers and keyboard navigation.
Known Limitations
Analysis Progress Indicator
During file analysis, a progress indicator updates to reflect the current stage of processing. This dynamic update may not be consistently announced by screen readers during active analysis. The final result display — BPM, key, and Camelot code — is the accessible output and is fully readable by screen readers. We are working to improve ARIA live region announcements for the progress indicator.
Camelot Wheel Visual Diagram
If the site includes a visual circular diagram of the Camelot Wheel, this is a visual-only representation. Text equivalents listing all 24 key-to-Camelot mappings are available in the How It Works page and the BPM Key Finder FAQ page, providing equivalent reference information for screen reader users.
Third-Party Content
If advertising or third-party content is added to this site in future, the accessibility of those elements will depend in part on third-party providers. Any such addition will be reviewed for accessibility impact before implementation.
Assistive Technology Compatibility
Tested with:
- Screen readers: NVDA with Chrome (Windows), VoiceOver with Safari (macOS and iOS)
- Keyboard-only navigation: Chrome and Firefox on Windows
- Browser zoom: Content tested at 200% zoom without loss of functionality
- High contrast mode: Core content remains readable in Windows High Contrast mode
We recommend Chrome or Firefox with your preferred assistive technology.
Feedback and Contact
If you experience a barrier on any page or tool — a field that cannot be reached by keyboard, a result not accessible to your screen reader, a file upload control that is not functioning with your assistive technology, or any other accessibility issue — please contact us.
Contact: bpmkeyfinder.com/contact
Include the page or tool, the assistive technology and browser, and what you expected versus what happened. We respond to all accessibility feedback personally within 7 business days.
Formal Complaints
If you are not satisfied with our response, you may contact the relevant national enforcement body in your country.
Review Schedule
This statement is reviewed and updated at least once per year, or whenever significant changes are made to the site’s tools or structure.
Related Pages
- How It Works — how the tool analyses files and produces results
- BPM Key Finder FAQ — common questions including Camelot Wheel reference table
- Contact — report an accessibility barrier
This Accessibility Statement is written and maintained by Charlotte Hayes, founder of BPMKeyFinder.com. Last updated: June 2026.