Gumroad Accessibility Checklist 2026 | WCAG 2.1 AA & EAA Compliance

When uploading a cover or gallery image in the Gumroad product editor, fill the alt text or description field with a concise sentence describing the image's purpose, for example what the product is or what the screenshot shows. For images you insert into the rich-text description, use the editor's image dialog to add alternative text. If the cover image is purely decorative and duplicates the product name, keep the description short and factual rather than leaving it blank, since a blank field is often exposed as an unlabeled image.

Before saving your accent color, test the foreground and background combination in the WebAIM Contrast Checker. For button text and links you need at least 4.5 to 1 for normal text, or 3 to 1 for large text. Pick a darker, more saturated accent so white text on the button stays readable, then re-check both the button state and any colored link text in descriptions. If Gumroad's generated text color on your accent cannot be made to pass, choose a different accent rather than keeping a brand color that fails.

In the description editor, use the actual heading styles in logical order and do not skip levels, so a major section is one level and its subsections are the next level down. Reserve bold for emphasis within a paragraph, never as a substitute for a heading. Keep each heading short and descriptive. You cannot control what heading level Gumroad assigns to the product title in the page template, so structure your own content consistently beneath it and verify the resulting outline with a heading-list tool.

Write descriptive link text that names the destination, for example View the live demo or Download the sample chapter PDF. Avoid bare URLs as link text, since a screen reader reads them character by character. You fully control this inside the description editor: select the meaningful words and apply the link, rather than linking the words click here. Keep link text reasonably short while still conveying where the link goes.

Do not rely on color alone for the sale message. In your description, pair any colored sale text with explicit words such as Sale price, was 49 now 29, or Limited-time discount. The strikethrough that Gumroad renders on the original price is a structural element you do not control, but you can always add a clear textual statement of the discount in the description and product name so the saving is conveyed in text, not just visually.

The rating widget is part of Gumroad's template, so the realistic action is to report any missing text alternative to Gumroad support and note it in your accessibility statement. What you can control is restating the social proof in plain text in your description, for example Rated 4.6 out of 5 across 120 verified reviews, so screen reader users still get the information. Verify with NVDA whether the live star rating is announced, and document the result.

You cannot edit the checkout markup, so the correct remediation is to test the checkout with NVDA and the keyboard, document any unlabeled fields, and report them to Gumroad support with specifics. For any custom checkout fields you do add, give each a clear, self-explanatory name rather than relying on placeholder hints. Record the platform-level limitations in your accessibility statement so buyers and auditors know which gaps are Gumroad's responsibility versus yours.

Error handling on the core checkout is Gumroad's markup, so test the failure cases yourself with a screen reader, note whether errors are announced and described in text, and report shortcomings to Gumroad support. For your own custom fields, write helper text that states the format up front so buyers avoid errors. Add a line in your accessibility statement describing the checkout testing you performed and any unresolved platform issues.

Test by tabbing through your product page and the buy overlay with the keyboard only, watching whether a visible focus indicator moves predictably through every control. Where the indicator is missing or too faint, report it to Gumroad support, since the overlay markup and styles are theirs. Avoid choosing accent or background colors that wash out the default focus ring. Document the focus behavior in your accessibility statement, noting which elements you verified.

If you control the page where you paste the embed code, you can add a descriptive title attribute to the iframe element in the snippet, for example Buy this product on Gumroad, which immediately gives the frame an accessible name. If you are using a no-code site builder that hides the iframe markup, request the title from Gumroad or your builder, and note the limitation in your accessibility statement. On a hosted Gumroad page itself, this is platform markup outside your control.

Gumroad's primary buy button is generally a large target, but in your descriptions avoid tiny, tightly packed links and do not place multiple links immediately adjacent on one line. Give linked phrases enough surrounding text so taps land reliably. Test your product page on an actual phone, trying every control with your thumb. Where a platform control is too small or cramped, report it to Gumroad support, since you cannot resize their buttons.

Provide captions for any prerecorded video preview, either by uploading a caption file to the host such as YouTube or Vimeo before embedding, or by choosing a host that supports captions. For audio samples, paste a short transcript or summary into the description beneath the player. Make sure captions are accurate and synchronized rather than relying on raw auto-captions. Because you supply the media and the description text, you can fully resolve this without involving Gumroad support.