Big Cartel positions itself as the storefront for independent artists, illustrators, ceramicists, screen-printers, and small-batch makers, and that audience is the reason its accessibility footprint is distinct from Shopify or BigCommerce. The platform offers a small library of designer-built themes, a limited but deliberate set of customization controls, and a hosted checkout that handles payment compliance for the seller. That simplicity is what attracts non-developers; it is also what makes accessibility shortcuts easy to lock in. A single low-contrast accent color picked in the theme editor can fail every product page on the site, and a single missing alt text habit can compound across hundreds of inventory photos. With the European Accessibility Act enforceable since 28 June 2025 against any e-commerce service offered to EU residents, and ADA web-accessibility demand letters increasingly reaching independent online sellers in the United States, Big Cartel shop owners need a checklist that accepts the platform's limitations and works inside them. This guide focuses on what a non-developer can change today: the theme controls Big Cartel exposes, the product fields every shop owner edits, the form choices on contact and newsletter pages, and the small custom HTML and CSS window available on paid plans. Each issue maps to the specific WCAG 2.1 success criterion it violates so you can document remediation in your accessibility statement.

Common Accessibility Issues

critical

Theme Accent Color Fails 4.5:1 Contrast Against Background

WCAG 1.4.3

Big Cartel's theme editor lets shop owners pick a single accent color that is applied to product titles, links, the Add to Cart button, sale badges, and form focus rings. Because the editor shows no contrast warning, makers commonly pick a brand color like soft pink, pastel green, or beige that drops well below 4.5:1 against the white or off-white page background. Every product page, navigation menu, and cart summary then fails WCAG 1.4.3 in dozens of places at once.

How to fix:

Open Customize Design > Colors and copy the accent color hex value into the WebAIM Contrast Checker (webaim.org/resources/contrastchecker). Test it against your main background color and against any secondary background. If either combination is below 4.5:1 for normal text or 3:1 for large text, darken or saturate the accent until it passes. Keep your brand color for hero imagery and product photos where decorative use does not need to meet contrast ratios; reserve a compliant variant for text and interactive elements.

Before
<!-- accent #f7c8d9 on #ffffff = 1.6:1 contrast, fails 1.4.3 -->
<a href="/product/print" style="color: #f7c8d9">Sunset Print</a>
After
<!-- accent #b14e74 on #ffffff = 5.6:1 contrast, passes 1.4.3 -->
<a href="/product/print" style="color: #b14e74">Sunset Print</a>
critical

Product Photos Inherit Filename as Alt Text

WCAG 1.1.1

When a shop owner uploads a product image to Big Cartel, the platform stores the filename as the default alt attribute. Most makers upload directly from a phone or DSLR with names like IMG_2847.jpg or DSC00481.JPG, which leaves screen-reader buyers hearing meaningless filenames or, worse, the same filename announced for every variant of a product. Multiply that across a hundred inventory items and the entire shop becomes unusable for blind buyers.

How to fix:

Edit each product, scroll to the image upload area, and hover or click the photo to expose the Alt Text field. Write a short, specific description of what the image shows in roughly 8 to 16 words: a phrase like 'Hand-printed cotton tea towel with mustard yellow citrus pattern' is enough. For variant photos that show the same product in a different colour, lead the alt text with the differentiator: 'Same towel in deep blue.' Avoid starting with phrases like 'Image of' or 'Photo of' since assistive technology already announces it as an image.

Before
<img src="/products/IMG_2847.jpg" alt="IMG_2847.jpg">
After
<img src="/products/lemon-tea-towel.jpg" alt="Hand-printed cotton tea towel with mustard yellow citrus pattern">
serious

Contact and Newsletter Forms Use Placeholder-Only Labels

WCAG 3.3.2

Big Cartel themes commonly render the contact form and the newsletter signup form with placeholder text inside each input and no persistent visible label. As soon as a buyer or interested visitor begins typing, the placeholder disappears and the field has no name. Cognitive-disability users lose the prompt, screen-magnification users cannot scroll back to recover it, and many screen readers do not announce placeholders reliably across browsers.

How to fix:

On paid plans, open Customize Design > Custom Code and inject CSS that floats the placeholder above the input as a persistent label, or replace the placeholder with a real <label for="email"> via the theme HTML. On the free plan, where custom code is unavailable, choose a theme variant whose contact form already shows persistent labels (the Sandbox and Snowflake themes both do as of April 2026). Avoid relying on the placeholder for any field that handles a name, email address, or shipping detail.

Before
<input type="email" placeholder="Email address" name="email">
After
<label for="newsletter-email">Email address</label>
<input id="newsletter-email" type="email" name="email" autocomplete="email">
serious

Add to Cart and Buy Now Buttons Render Without Visible Focus Ring

WCAG 2.4.7

Several stock Big Cartel themes apply outline: none to all buttons in their reset CSS, then never restore a visible focus indicator on :focus or :focus-visible. Keyboard-only buyers tabbing through a product page see no signal when their focus reaches the Add to Cart button. The button still works on Enter, but a buyer with a motor disability or anyone using switch navigation cannot tell where they are in the page.

How to fix:

On paid plans, paste the following into Customize Design > Custom Code (CSS): button:focus-visible, .btn:focus-visible, a.btn:focus-visible { outline: 3px solid #b14e74; outline-offset: 2px; } using your compliant accent color. Test by pressing Tab repeatedly from the top of any product page and confirming the ring appears around every interactive element. On the free plan, ask Big Cartel support which themes ship with a visible focus ring by default; the Birthday and Foundry themes have stronger focus styles than the older Anchor or Snow themes.

Before
button { outline: none; }
After
button:focus-visible {
  outline: 3px solid #b14e74;
  outline-offset: 2px;
}
serious

Cart and Checkout Use Color Alone to Indicate Errors

WCAG 1.4.1

When a buyer enters an invalid shipping ZIP, an unsupported country, or a sold-out variant in the Big Cartel cart, the platform surfaces the failure by tinting the relevant field in red. There is no icon, no error text near the field, and on some themes the colored border is the only signal. Color-blind buyers and screen-reader users have no way to discover what went wrong and may abandon the order assuming the site is broken.

How to fix:

Big Cartel's hosted cart and checkout do not expose the error template directly, but two mitigations work. First, in the Cart Notes field on the Settings page, write a short note such as 'If a field turns red after Place Order, it usually means the country is unsupported or stock has changed. Email [email protected] and we will fix it.' Second, on product pages, add inline copy under the variant selector explaining which countries you ship to and any minimum-quantity rules so most buyers never reach the silent error state. File a feature request with Big Cartel support asking for text-based error messaging in the hosted cart.

moderate

Sale Banner Animations Cannot Be Paused

WCAG 2.2.2

Several Big Cartel themes ship with a marquee-style announcement bar that scrolls promotional text horizontally across the top of every page. The animation runs continuously and offers no pause, stop, or hide control. WCAG 2.2.2 requires that any moving content lasting longer than five seconds can be paused; vestibular-disorder users and people with cognitive disabilities can experience nausea or distraction from continuous motion.

How to fix:

Disable the scrolling announcement bar in Customize Design > Theme Settings and replace it with a static, full-width announcement using a single line of theme HTML. If you need to rotate multiple messages, switch them on a daily basis manually rather than via animation. On paid plans, you can also paste a short script that respects the prefers-reduced-motion media query so the animation only runs for visitors who have not asked their operating system to reduce motion.

moderate

Accessibility Statement Page Is Missing or Templated

WCAG n/a

The European Accessibility Act and several U.S. state laws now expect e-commerce services to publish a public accessibility statement that names the WCAG version targeted, lists known limitations, and provides a contact for accessibility complaints. Big Cartel does not generate this page automatically, and most shops either omit it or paste a generic template that does not match what is actually true on their site.

How to fix:

Create a new Page in your Big Cartel admin titled 'Accessibility' and link to it from the footer of every page (Customize Design > Footer Links). State the WCAG version you are working toward (typically 2.1 AA), name the platform (Big Cartel), list the known limitations honestly (for example, the hosted cart and checkout are controlled by Big Cartel and may have separate behavior), and include an email address that is monitored at least once per business week. Update the page whenever you change theme or add a third-party widget.

Big Cartel-Specific Tips

  • Stick to one or two of the better-tested themes (Birthday, Foundry, Sandbox as of April 2026) rather than older themes with weaker default focus styles and color tokens.
  • Document every custom CSS or HTML change in a notes file so future theme upgrades do not silently overwrite your accessibility fixes.
  • Use a single, descriptive product image filename per upload (lemon-tea-towel-mustard.jpg) so even if alt text is briefly missing, the fallback signal carries some meaning.
  • Avoid third-party Big Cartel apps that inject pop-ups, exit-intent overlays, or chat widgets without keyboard support; if you need one, test it with Tab navigation before publishing.
  • Run the published shop URL (not the preview) through axe DevTools and the WAVE extension at least once per quarter; the preview environment does not always render the same scripts.

WebAIM Contrast Checker

Free contrast ratio calculator for testing your Big Cartel accent color against background and text colors before you save the theme.

axe DevTools

Browser extension that scans the published Big Cartel storefront, product pages, and cart for WCAG violations and explains how to fix each one.

WAVE Browser Extension

Visual accessibility checker that overlays icons on the page to show missing alt text, empty links, contrast failures, and structural issues without leaving Big Cartel.

Further Reading

Other CMS Checklists