Pixieset Accessibility Checklist 2026 | WCAG 2.1 AA & EAA Compliance
Last updated: 2026-04-29
Pixieset is the platform of choice for tens of thousands of wedding, portrait, and family photographers who need to deliver client galleries, run a public marketing website, sell prints, and capture inquiry-form leads from one tool. Each of those surfaces has its own accessibility profile: the client gallery is image-heavy and password-gated, the website builder produces a public marketing site that search engines and accessibility complainants both crawl, the store handles real e-commerce with the European Accessibility Act fully in scope, and the contact form is often the first interaction a hard-of-hearing or vision-impaired client has with the photographer. Pixieset gives photographers a polished visual editor and a curated set of templates, but the price of that simplicity is that several accessibility settings live behind toggles photographers do not always know to look for, or are not exposed at all. With the European Accessibility Act enforceable since 28 June 2025 against any e-commerce service offered to EU residents, and ADA web-accessibility complaints continuing to reach photographers across the United States, this checklist walks through the issues a photographer can actually fix today, organized by Pixieset surface and mapped to the specific WCAG 2.1 success criterion each one violates.
Common Accessibility Issues
Pixieset client galleries display dozens or hundreds of photos with empty alt attributes. Galleries are typically password-gated, but the gallery is still served as a public web page, the EAA scopes private e-commerce flows where prints are sold from the gallery, and clients increasingly forward links to family members who may use screen readers. A blind grandparent receiving a wedding gallery link currently hears only image counts and filenames.
Pixieset does not yet expose a per-image alt text field in the gallery, but two mitigations work. First, name your exported files descriptively before upload (smith-wedding-first-look-001.jpg) so the filename fallback carries some meaning. Second, on the gallery cover page, add a short paragraph in the description field that summarizes what the gallery contains: 'Sarah and Marcus's wedding at Greenfield Estate, with 240 photos covering the ceremony, portraits, and reception.' File a feature request with Pixieset support asking for per-image alt text in client galleries; their public roadmap accepts this category of request.
<!-- 240 images, every alt empty, screen reader announces 'graphic' 240 times -->
<img src="/galleries/smith/IMG_2847.jpg" alt=""><!-- gallery cover description carries the context the per-image alt cannot -->
<p>Sarah and Marcus's wedding at Greenfield Estate. 240 photos covering the ceremony, family portraits, and reception.</p>Many Pixieset photographer-website templates ship with body text in a soft gray (often #a8a8a8 or lighter) over white. The aesthetic feels editorial, but it falls below 4.5:1 against the white background, failing WCAG 1.4.3. Service descriptions, pricing, and 'About' copy become hard to read for low-vision visitors and effectively invisible to anyone reading on a sunlit phone screen.
Open Website > Design > Typography and change the body text color to a darker gray (use #595959 or darker on white, which gives roughly 7:1) or to true black for the strongest contrast. Test the result by copying the hex code into the WebAIM Contrast Checker against your background color. Repeat for any subhead, caption, or footer text. Avoid using the same gray for both decorative section labels and actual reading copy.
Pixieset's inquiry and contact form blocks default to placeholder text inside each input with no persistent visible label. As soon as a prospective client begins typing their wedding date, name, or email, 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.
In the form block editor, select each field and enable the 'Show field label' toggle (available on most templates as of April 2026). For fields the toggle does not cover, edit the field copy so the label is part of the visible page above the input rather than only inside it. If you use the standalone Pixieset Contact form on a separate page, prefer the Long version of the template, which renders persistent labels by default.
The Pixieset Store renders print-size selectors as colored swatches and indicates sold-out or unavailable sizes with a strikethrough or muted shade only. Color-blind clients and screen-reader users cannot tell which size is selected or which are unavailable, and the strikethrough is not always exposed to assistive technology as a state.
In the Store template, choose the variant of the size selector that includes text labels next to each swatch (Settings > Store > Layout). For sold-out sizes, ensure the option is communicated as 'Sold out' in text rather than only via styling. If the template you are using does not support a text-labeled selector, switch to a different store template that does, or document the limitation in your accessibility statement and provide an email path for clients to confirm sizes.
Many Pixieset photographer-website templates open with a hero slideshow that auto-advances every three to five seconds and offers no visible pause, stop, or hide control. WCAG 2.2.2 requires that any moving content lasting longer than five seconds be pauseable. Vestibular-disorder visitors and cognitive-disability users can experience nausea, distraction, or dropped reading focus.
In Website > Pages > Home, open the hero slideshow block and either disable auto-advance entirely (recommended: a single static hero image is more accessible and often converts better) or extend the interval to 10+ seconds and ensure the block exposes a pause control. On templates where pause controls cannot be enabled, switch to the static hero block. Also enable the 'respect prefers-reduced-motion' toggle if your template exposes it.
On many Pixieset gallery templates, the per-image download button renders as a small icon (a downward arrow) with no visible text and no aria-label. Screen readers announce 'button' with no further context, leaving blind clients unable to download their own photos. The same pattern appears on share, favorite, and add-to-cart icon buttons.
Pixieset has been progressively adding aria-labels to gallery icon buttons, but coverage is uneven across templates. On Premium and Ultimate plans, paste a short script into Custom CSS / Custom Code that adds aria-label attributes to the affected buttons; the platform exposes consistent class names per icon. On lower plans, file a support ticket asking for the gallery template you are using to be patched, and meanwhile add a sentence to the gallery cover page explaining how to download photos in bulk via the email or USB option you offer.
EU accessibility-statement requirements under the European Accessibility Act and a growing number of U.S. state-level rules expect public-facing services to publish a discoverable accessibility statement. Photographers selling prints to EU residents through Pixieset are squarely in scope, but Pixieset does not generate this page automatically and most photographer websites do not have one.
Create a new page in Website > Pages titled 'Accessibility', state the WCAG version you are working toward (typically 2.1 AA), name the platform (Pixieset), list the known limitations honestly (for example, per-image alt text in galleries is not currently exposed), and include an email address that you read at least weekly. Link the page from the site footer (Website > Design > Footer Links). Update the page when Pixieset ships new accessibility features so your statement does not drift out of date.
Pixieset-Specific Tips
- Treat the public marketing website as the strictest accessibility surface; if it passes WCAG 2.1 AA, the client galleries and store inherit most of the wins.
- Name exported files descriptively before upload (smith-wedding-portraits-014.jpg) so the filename fallback carries meaning when alt text is empty.
- Avoid third-party widgets and chat embeds inside Pixieset; most do not respect keyboard navigation or prefers-reduced-motion and they are difficult to debug from the editor.
- When a client asks how to download all their photos, link them to a written guide on your site rather than relying on the icon-only download button alone.
- Run the published website URL (not the editor preview) through the WAVE extension at least once per quarter and after every template change.
Recommended Tools
axe DevTools
Browser extension that scans Pixieset photographer websites, client galleries, and store pages for WCAG violations and explains how to fix each one.
WebAIM Contrast Checker
Free contrast ratio calculator for testing the gray body text and accent colors used in Pixieset photographer-website templates.
WAVE Browser Extension
Visual accessibility checker that overlays icons on the page to highlight missing alt text, empty links, contrast failures, and structural issues without leaving Pixieset.
Further Reading
Other CMS Checklists
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.