Accessibility

The standard we work to

We are working toward level AA of the Web Content Accessibility Guidelines (WCAG) 2.2. Gasp has not been audited by anyone outside the company, and we do not claim that it meets that standard today.

What we have done so far: in September 2026 we went through the web app's code against WCAG 2.2 AA. We fixed part of what we found (captions, the keyboard focus indicator, the labels on red buttons, a skip link and one main region per page, studio controls that appeared only on hover, and five form fields that had no name), and what we have not fixed yet is under What does not work yet. We also added automated tests that fail if a page ends up with no main region or two, if the focus indicator or the labels on red buttons fall below the contrast we set, or if a studio control goes back to being hidden until the pointer is over it. We then went through the main pages in Chrome on a desktop computer, looking at the focus indicator, the main region and the red buttons.

What works

• Captions. Episodes get captions made automatically from their audio by speech recognition. On an episode's page they are on when it starts, including while it plays muted; the captions menu in the player's controls turns them off or back on, and Gasp remembers your choice in that browser.
• Sound. On an episode's page, episodes start muted. Sound comes on only when you ask for it, with the “Tap for sound” button, the player's mute button or volume control, or the M key. Once you have turned it on, the next episode you move to on Gasp (when one ends, with the arrow keys or from the episode list) starts with sound, unless your browser stops it, in which case it starts muted and “Tap for sound” comes back. Reloading the page, or opening an episode from a link or the address bar, starts it muted again. The player embedded on other sites plays with sound when you press its Play button.
• Keyboard. Every page except the player embedded on other sites starts with a “Skip to content” link, and every control shows a visible focus indicator when you reach it with the keyboard. On an episode's page, Space plays and pauses, M mutes, the up and down arrows move to the previous and next episode, F turns focus mode on (or, in a narrow or upright window, hides the page around the video) and Escape leaves it; these keys stand aside while you type or while a dialog or menu is open. On an episode's page anything you can do by swiping also has a button, and in the studio episodes can be moved from each row's menu as well as by dragging.
• Structure. Each page has one main region, the language is set to English, and the site header and footer mark their links as navigation. Pictures have text alternatives or are marked as decoration, and buttons that show only an icon have a name.
• Contrast. Gasp's main text colours, including its lighter grey for secondary text, have at least 4.5 to 1 contrast against the backgrounds they sit on, and so do the labels on red buttons. Some smaller text does not (see below).
• Zoom and screens. Zooming is never blocked, and the episode page works in portrait and landscape.
• Time. Nothing you watch, unlock or fill in has a time limit: a season bundle asks you to confirm its price, and waits until you confirm or cancel.

What does not work yet

• Captions are not checked by a person. They can contain mistakes, they cover speech only (no speaker names, and no descriptions of sounds or music), and an episode with no speech, or in a language the recognition does not cover, may have none. Episodes have no audio description and no transcript. A player embedded on another site shows captions but has a captions menu only when that site keeps the player's controls. In the studio, generated clips and the preview of a generated episode play without captions (the preview of an uploaded episode shows them), so a creator first sees a generated episode's captions on its episode page, and no creator can edit or remove them.
• Single-key shortcuts. F and M on an episode's page and / on the help page cannot be turned off or changed, and the studio's image viewer uses letter and number keys too.
• The next episode starts by itself when one ends, and there is no setting to stop that.
• Motion. If your device asks for reduced motion, some parts of Gasp follow it (the homepage's opening animation and drifting embers, the public creator and studio pages, the Idea step of a new series, and pop-up messages), but dialogs, menus and loading animations still move, the studio's loading placeholders and spinners included. So does the glow that circles the buttons in the studio header's wallet while it is open; pointing at a button stops it, keyboard focus does not.
• Short messages. Some confirmations and errors appear as a pop-up message that disappears after about four seconds, and for some actions that message is the only place an error is shown. Pointing at the message keeps it on screen.
• Small grey text. Some small labels and hints have less contrast than we aim for: the footer's column titles and copyright line; labels on the homepage, pricing and creators pages; a series page's next-season line; episodes you have watched in an episode page's list, and the length line of the one playing; the area name (Studio, Account, Admin) beside the Gasp logo once you are signed in; the phone menu's captions; and much of the small grey text in the studio and on your account pages. So do the borders of text fields, the outlines of checkboxes and radio buttons, and the track of a switch that is off.
• Reasons shown only on pointing. In the studio, when a button cannot be used yet, the reason (for example, not enough credits, or a script that needs fixing first) is often shown only as a tooltip when you point at it with a mouse, so keyboard, touch and screen reader users may not find out why.
• In the studio, marking up a picture for an edit (pins, boxes and strokes) needs a mouse or touch; you can describe the change in words instead.
• For screen readers. The Like button on an episode's page does not read out its count, and the full name of a rating mark (for example “Parents strongly cautioned”) appears only as a tooltip you cannot reach with the keyboard; for R and NC-17 series, the 18+ check explains the rating when you start an episode. After you apply as a creator, focus is not moved to the confirmation, and a screen reader may not read it out.
• Headings and forms. A few pages do not start with a main heading: an episode's page in a narrow or upright window and in focus mode, the player embedded on other sites, the pricing pages, some steps of the episode editor and the admin console. Some error messages in forms are not linked to the field they are about.
• Links. In some places a link inside a sentence is told apart from the text around it by colour alone, or not at all, until you point at it: the creator's name under a series title (on the series page and beside an episode on a wide screen), and the support address on some notices (a suspended account, a hidden page).
• Small targets. On wider screens, the short bars on the Watch page that switch the featured series are only 4 pixels tall and close together. Every series they switch to is also in the rows below.
• One theme. Gasp is dark only, with no light or high-contrast theme of its own. With your system's high contrast colours on, Gasp's own focus indicator follows them, but the buttons in the video player's control bar show no focus indicator.
• Untested. We have not yet tested Gasp with screen readers (VoiceOver, NVDA, TalkBack), in Firefox or Safari, on real phones, with a real caption track in the captions menu, or at 400% zoom.

Parts made by others

Some screens come from companies we work with, and we cannot change how they are built: signing up, signing in and your sign-in and security settings (Clerk), the video player's control bar (Mux), the check that you are not a bot when you apply as a creator (Cloudflare), and the pages where you pay, manage your plan, or set up and view your payouts (Stripe). If one of them stops you, tell us: we will look for another way to help, and we can pass the problem on to the company concerned.

Browsers and devices

Gasp is built for current versions of Chrome, Edge, Firefox and Safari on computers and phones. Our own checks so far used Chrome on a desktop computer.

Tell us about a barrier

If something on Gasp gets in your way, write to accessibility@watchgasp.com. Tell us the page you were on (its address helps), what you were trying to do, and the device, browser and any assistive technology you use. A person reads every message. You can also find answers on the help page.