Home Help Center Knowledge Base Submit Ticket Check Status System Status
Back to System Status

Quran player: Mute control displayed out of order on the playback toolbar

  • Incident
  • minor
  • Resolved

Since the Mute control was added to the Quran player, it was displayed at the far left of the playback toolbar while keyboard focus and screen reader reading order reached it last, after Skip forward 30 seconds. Sighted keyboard users saw Mute first but had to Tab past every other control to reach it, and people using a screen reader with sight heard the controls in a different order from the one on screen. Every control worked normally throughout, playback was unaffected, and no data was affected. The toolbar now displays the controls in the same order they are reached by keyboard and screen reader: Skip back 30, Skip back 10, Play or Pause, Skip forward 10, Skip forward 30, Mute.

Affected Services

  • Quran Player
  • Posted: Aug 29, 2026, 08:50 UTC
  • Resolved: Aug 30, 2026, 06:47 UTC
  • Duration: 21h 56m

Timeline

  1. resolved

    Aug 30, 2026, 06:47 UTC

    This incident has been resolved. The Mute control now appears last on the toolbar, matching the keyboard and screen reader order on all devices. The mismatch had been present since the control was introduced; it affected the order of the controls only, never their function.

  2. monitoring

    06:44 UTC

    A fix has been implemented and we are monitoring the results. Visitors who still see Mute at the left of the toolbar can reload the page.

  3. identified

    Aug 29, 2026, 08:51 UTC

    The issue has been identified as a display ordering setting on the playback toolbar that placed the Mute control first on screen while it remains last in the keyboard and reading order. A fix is being implemented.

  4. investigating

    08:50 UTC

    During a routine screen reader review of gablvm.org we noticed that the Quran player's Mute control appeared in a different position on screen than the position it is reached in by keyboard and screen reader. We are investigating.

Permalink: /incident/85

View all systems