On June 26, 2026, we shipped an update meant to make the Quran player work better with the JAWS screen reader on Windows. It did. It also, without us noticing, switched off the player's single key keyboard shortcuts for anyone whose focus was on the player's own controls, and they stayed off for seven weeks. Accessibility is the reason this organization exists, so when we get it wrong in the very act of trying to get it right, you deserve the full story. No data was affected and playback itself never stopped working. This is the account of a quiet bug, why our safeguards could not hear it, and what it taught us.
What listeners experienced
From June 26, 2026, to August 16, 2026, pressing the player's single-key shortcuts, K to play or pause, J and L to skip backward and forward, N and P to change surah, M to mute, did nothing while keyboard focus was on the player's control bar. Because the control bar is exactly where focus rests while operating the player, for practical purposes the shortcuts were gone. Everything else worked: the on-screen buttons, moving between controls with the arrow keys, and playback itself were normal the whole time, which is a large part of why nothing looked broken.
How one accessibility improvement broke another
The June update turned the player's row of controls into a proper toolbar, the pattern recommended by the web accessibility standards: you press Tab once to reach it, and the arrow keys move you between the buttons inside it. This is a real improvement, especially for Windows screen reader users, and it remains in place today.
The player also has a long-standing safety rule: shortcuts stand down while you are inside a form control, so that typing in a dropdown or adjusting the volume slider never accidentally skips the audio. That rule was written broadly, and it included buttons. The new toolbar is made entirely of buttons, and it is where keyboard focus lives while you use the player. Put those two sensible decisions together and the result is that the shortcuts stood down precisely in the place they were needed most. Neither decision was wrong on its own. Together they were.
Why it took seven weeks to notice
A broken shortcut is silent. It does not show an error, it does not announce anything to a screen reader, it simply does nothing. Our automated accessibility scans passed throughout, and honestly so: they examine the structure of the page, and the structure was correct, arguably better than before. A scanner cannot press K and listen for the pause. And because the player stayed fully usable through its buttons, day-to-day use gave no alarm. The bug waited for the one thing that could catch it: a person who relies on those shortcuts.
How it was found and fixed
On August 16 a listener who uses VoiceOver on a Mac every day reported that the letter keys did nothing. The cause was identified within minutes, the fix was live within twenty, and it was verified by pressing the keys in a real browser with focus on the control bar, not by re-running a scan. The shortcuts now work from the control bar on every platform, and the toolbar improvements from June are untouched. The timeline is published as incident 84 on our status page.
What we learned
- Screen readers are not interchangeable. An improvement verified with one can quietly regress the experience in another. Changes to keyboard behavior now get checked against the combinations our visitors actually use: VoiceOver on Mac and iPhone, JAWS and NVDA on Windows, and a keyboard with no screen reader at all.
- A clean scan is not a working feature. Automated checks score what a page is, not what it does. Our verification for player changes now includes pressing the actual shortcuts in a real browser and confirming the player responds.
- Safety rules deserve narrow edges. A rule written as "shortcuts stand down inside any control" felt safe and was too broad. The rewritten rule stands down only for the keys a control genuinely needs.
- The best accessibility monitoring we have is people. Seven weeks of automation missed what one listener caught in a day. If something on this site does not work with your hands or your screen reader, please tell us at [email protected]. Reports like that are how this site gets better.