• Success Criterion 2.1.4
  • Conformance level A

Library’s Default Hotkeys Shipped With No Settings Toggle

2.1.4 — Character Key Shortcuts

Scenario

Setting

A recipe site's ingredient list

What’s wrong

Library defaults (hotkeys in players/mail apps) shipped enabled with no settings toggle.

Example 

// third-party video library initialized with defaults
videoPlayer.init({ hotkeys: true }); // 'f', 'm', 'k' bound globally by the library, no opt-out exposed by the site

Why it matters

A cook dictating a shopping-list note near the embedded recipe video accidentally mutes or fullscreens it whenever they say a word starting with "m" or "f."

How to test

Check the app/player's settings for a hotkeys toggle: if shortcuts are enabled by default with no visible settings option, it fails.

How to fix

Check whether a bundled player or library ships single-key shortcuts by default, and wire its own enable/disable option into a visible site setting.

videoPlayer.init({ hotkeys: false });
document.getElementById('shortcuts-toggle').addEventListener('change', (e) => {
  videoPlayer.setHotkeys(e.target.checked);
});

Outcome

A cook dictates their note near the video without it muting or jumping to fullscreen.

Who is affected

Speech-input users and users with involuntary key presses can't opt out of shortcuts baked into a third-party library the site never surfaced controls for.

Learn more

Related scenarios