Bakery & Custom Cake Shop Website Accessibility Guide 2026 | ADA, EAA, Allergen Labeling, Online Ordering

Last updated: 2026-05-12

Bakeries, cake shops, custom-pastry studios, wholesale bread producers, gluten-free and allergen-free specialty bakers, and farmers'-market bakers run a business in which the website is increasingly the only channel for catalog browsing, custom-cake quote requests, wedding-and-event-cake tasting bookings, online ordering with same-day pickup or local delivery, and—critically for a category where food-allergen disclosure is regulated—the publication of allergen, ingredient, and cross-contamination information. Following Robles v. Domino's Pizza (9th Cir. 2019), the bakery's website is in scope under the nexus test applied in most U.S. circuits, which ties the website to a physical place of public accommodation; whether a standalone website is itself a place of public accommodation is subject to a circuit split, and bakeries are exposed to the same state civil-rights claims as any other consumer-facing business. We have no sector-level filing or settlement data for this industry and will not invent a figure for it; most such claims settle confidentially. The defect pattern we do see repeatedly is unlabeled product images, image-only allergen tables, inaccessible custom-cake builders, and same-day-pickup scheduling widgets that cannot be operated with a keyboard. Bakeries also operate under a parallel FDA and USDA regime governing the disclosure of allergens (FALCPA's nine major allergens), ingredients, and nutrition information when the bakery makes nutrient-content claims. Those rules govern what must be disclosed and how it is labelled on packaged food; they do not set a web-accessibility standard, and we do not assert that they do. When the same information is published online as an image-only table, the exposure runs through the ADA instead. The customers most affected are disproportionately the customers who matter most: a blind parent ordering a peanut-free birthday cake for a peanut-allergic child, a deaf customer scheduling a wedding-cake tasting, a wheelchair-using customer comparing bakery delivery zones, an elderly customer placing a recurring weekly bread order. Bakeries marketing to EU-resident customers face EAA exposure as of June 28, 2025, with explicit e-commerce provisions for online ordering. This guide covers the legal framework, the bakery-specific failure patterns, and a concrete compliance checklist.

Legal Requirements

Law / Standard Effective Date Summary Penalty
ADA Title III In effect Bakeries, cake shops, and custom-pastry studios are places of public accommodation under ADA Title III in most U.S. circuits. The website is the primary catalog-browsing, custom-cake-quote, tasting-booking, and online-ordering channel, putting it within Title III scope. WCAG 2.1 AA is the de-facto conformance standard, and DOJ has not announced a timetable for moving to WCAG 2.2 AA. Injunctive relief plus attorneys' fees. California Unruh statutory damages of $4,000 per visit. New York State Human Rights Law: compensatory damages plus attorneys' fees, and civil fines payable to the state in Division of Human Rights proceedings. Publicly reported pre-filing demand-letter settlements generally run $5,000-$20,000, and post-filing settlements $30,000-$150,000; no public dataset breaks settlement amounts out by industry.
European Accessibility Act (EAA) 2025-06-28 Bakeries located in the European Union, U.S. specialty bakeries shipping to EU residents (gluten-free, vegan, kosher, and other specialty categories that drive cross-border orders), and international bakery marketplaces with EU storefronts must bring their digital services into conformity with the EAA's Annex I accessibility requirements; conformity with the harmonised standard EN 301 549 (which references WCAG 2.1 AA) gives a presumption of conformity. E-commerce baked-goods purchases, subscription-bread programs, and corporate-gifting flows are independently in scope under the EAA's e-commerce provisions. Set by each EU member state and varies widely. National market-surveillance authorities can order remediation and require withdrawal of non-conforming services from the EU market. No EAA accessibility fine has been publicly reported in any member state to date. This is not legal advice.
FDA Food Allergen Labeling and Consumer Protection Act (FALCPA) and FDA Food Safety Modernization Act (FSMA) In effect FALCPA requires that the nine major food allergens (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame, with sesame added in 2023) be clearly disclosed on packaged baked goods. FALCPA governs labelling on packaged food; it does not set a standard for a bakery's website, and we do not assert that it does. When the bakery publishes allergen, ingredient, or cross-contamination information online, an image-only allergen table or an untagged PDF ingredient list is unreadable to a screen-reader user, and that exposure runs through the ADA and state civil rights law rather than through FALCPA. Nothing here is legal advice. FDA enforcement (including Warning Letters) addresses labelling violations, not website accessibility, and we do not assert that FDA has enforced accessibility. Accessibility exposure for the website itself runs through ADA Title III, which provides injunctive relief plus the plaintiff's attorney's fees, and through state civil rights law.
California Unruh Civil Rights Act, New York State Human Rights Law, Florida Civil Rights Act In effect State civil-rights statutes provide independent causes of action for digital-accessibility failures. California Unruh awards $4,000 per visit. New York State and New York City Human Rights Laws supply further independent grounds. We have no sector-level filing data for this industry and do not assert a trend specific to it. California Unruh: $4,000 per visit. New York: compensatory damages plus attorneys' fees. Florida: compensatory damages plus attorneys' fees.
FTC Act Section 5 / state UDAP statutes (deceptive 'allergen-free' or 'gluten-free' marketing) In effect Where the bakery's website prominently advertises 'gluten-free,' 'nut-free facility,' 'peanut-safe,' or similar allergen-free marketing language but the website itself is not accessible to consumers with food allergies who depend on the disclosure, the gap between the advertising and the site raises an unfair-or-deceptive-practices question. Note that FTC Act Section 5 is enforced by the Commission and gives private plaintiffs no cause of action; a private suit would have to proceed under a state UDAP statute such as California's UCL or New York GBL §349. We are not aware of a reported decision applying either theory to website inaccessibility and do not assert that one exists. This theory is especially common when a celiac or peanut-allergic plaintiff is unable to verify the allergen-handling claim because of an inaccessible allergen table. FTC enforcement (rare for SMBs); state-AG enforcement and private causes of action under state UDAP statutes; restitution and treble damages in some states.

Key Accessibility Issues in Bakeries, Cake Shops & Custom Pastry

Allergen and Ingredient Tables Published as Image-Only Photos or Untagged PDFs

The single most consequential defect on bakery websites is allergen and ingredient information presented as a photograph of a printed binder, a screenshot of a spreadsheet, or a print-design PDF exported without tagging. A blind parent trying to confirm that a children's-birthday cake is actually peanut-free before placing the order has no way to read the disclosure. A celiac customer trying to confirm that the gluten-free pastry case is handled in a dedicated area has no way to verify the cross-contamination statement. This is simultaneously a WCAG 1.1.1 (Non-text Content) violation, an FDA-aligned consumer-protection failure, and the single highest-stakes defect on the site because it can produce actual physical harm to a child with a severe allergy.

How to fix:

Publish allergen, ingredient, and cross-contamination information as semantic HTML tables with proper <th> headers, not as photos or images of text. Each product's detail page must list the nine FALCPA major allergens with clear yes/no/may-contain disclosures, the full ingredient list in descending-weight order, and a plain-English cross-contamination statement ('Made in a facility that also processes tree nuts and peanuts; we do not operate a dedicated nut-free production line'). Provide a structured allergen-filter on the menu page so a customer with a tree-nut allergy can filter the catalog to safe items. If a PDF version is published as a download, generate it from a tagged source (Word or Google Docs) and confirm it passes Acrobat Pro's accessibility checker.

Product Catalogs With Inaccessible Photo-Only Cake Galleries and Empty Alt Text

Bakery product catalogs are dominated by photos of frosted cakes, decorated cookies, plated pastries, and finished wedding-cake tiers, almost universally with empty, filename, or generic alt text ('cake1.jpg', 'IMG_2049', 'wedding cake'). A blind customer comparing wedding-cake styles for their tasting appointment, or a customer with low vision evaluating decorative-cookie options for a corporate event, has no information about the cake's actual decoration, size, color palette, or occasion-fit from the gallery. Product detail pages typically continue the failure with sparse marketing copy ('Beautiful and elegant'), no structured description of cake flavor, filling, frosting type, decoration style, or available sizes.

How to fix:

Write descriptive alt text for every product photo in customer-meaningful terms ('Three-tier white-fondant wedding cake with hand-piped pearl beading on each tier, fresh-flower cascade of blush garden roses and white ranunculus, gold cake-topper monogram, serves 75–100 guests' or 'Dozen sugar cookies decorated with royal icing in pastel-easter palette: yellow chicks, blue robin eggs, white bunnies, pink tulips, packaged in clear-cellophane bag with white ribbon'). Each product detail page must include a structured description with flavor, filling, frosting type, decoration style, available sizes/serving counts, available customization options, lead time, and allergen statement. For tier-based wedding cakes, each tier-count option must have its own alt text describing what scales.

Custom-Cake Builders and Wedding-Cake Configurators That Cannot Be Operated With a Keyboard

Custom-cake builders and wedding-cake configurators are the highest-revenue interaction on most bakery sites: the customer selects tier count, cake flavor, filling flavor, frosting type, decoration style, color palette, cake-topper option, and serving count, with live price calculation. The standard implementation in Shopify cake-builder apps, custom WordPress plugins, and Squarespace configurators is a chain of drag-and-drop tier selectors, color-swatch grids, and dropdown carousels that fail keyboard navigation entirely, do not announce live price changes to screen readers, and do not preserve the configuration state when the customer revisits the page. The result is that a screen-reader user cannot configure a custom cake at all and must phone the bakery, which the bakery is rarely staffed to handle outside of designated tasting hours.

How to fix:

Rebuild the cake configurator as a set of native HTML form controls: tier count as <select> or <input type='number'> with min/max bounds; flavor, filling, frosting, and decoration style as labeled <select> elements or radio-button groups with descriptive text labels; color palette as labeled radio buttons with text labels ('Blush + Champagne + Ivory') not unlabeled color swatches; serving count as <input type='number'> with min/max bounds. Live price updates must be announced via an ARIA live region ('Estimated price: $485'). The configuration state must persist via the URL query string or local storage so the customer can return to it. Provide a phone-and-email fallback for customers who prefer to design over a call, with documented response time.

Same-Day-Pickup and Local-Delivery Scheduling Widgets That Fail Keyboard and Screen-Reader Use

Bakeries with same-day-pickup or local-delivery options depend on a date-and-time-window selector for order scheduling: 'Today by 11 AM,' 'Today after 2 PM,' 'Tomorrow morning,' 'Saturday afternoon.' The standard implementation in Shopify bakery themes, Square Online, Toast Online Ordering, and Clover is a JavaScript-only calendar widget that does not allow keyboard navigation, communicates blocked-out dates by gray-on-light-gray styling alone, and does not announce date selections to screen readers. For Mother's Day, Father's Day, Easter, and seasonal-cake surges, the inability to schedule pickup or delivery is the entire transaction failing.

How to fix:

Replace JavaScript-only date pickers with a properly-labeled <input type='date'> element with min and max attributes that bound the available scheduling window, plus a fallback set of three <select> elements (month, day, year) for browsers that do not support the native date picker. Delivery-window selectors must be a fieldset of properly-labeled radio buttons with descriptive text labels ('Today by 11:00 AM — order in next 60 minutes', 'Today after 2:00 PM — order in next 5 hours'), not color-coded buttons. Block-out dates must be conveyed by HTML disabled state plus visible text ('Sunday — bakery closed for pickup'), not color alone. Publish a phone-and-email fallback path for emergency same-day orders that the widget cannot accommodate, with stated callback time.

Wedding-Cake-Tasting Booking and Custom-Order Consultation Forms With Inaccessible Multi-Step Flows

Wedding-cake-tasting bookings and custom-order consultations are typically captured via multi-step forms in HoneyBook, Dubsado, Acuity Scheduling, or Calendly: the customer provides wedding date, guest count, venue, color palette, allergen requirements, dietary restrictions, and inspiration imagery, then selects a tasting appointment from a calendar. Common failures: placeholder-only labels that disappear once the customer types; allergen-and-dietary-restriction checkboxes presented as a card grid without proper fieldset/legend; inspiration-image uploads with no <input type='file'> fallback; calendar appointment-pickers that are JavaScript-only; multi-step focus loss between 'About Your Wedding' and 'Pick a Tasting Date.'

How to fix:

Use proper <label> elements—not placeholder text—for every form input. Allergen-and-dietary-restriction selections must be a <fieldset> with a <legend> and individual labeled checkboxes ('Peanut allergy', 'Tree-nut allergy', 'Celiac / gluten intolerance', 'Egg allergy', 'Dairy / lactose'). Inspiration uploads must offer <input type='file' multiple> as the primary control. Calendar appointment-pickers must allow keyboard navigation and announce selected slots to screen readers. Multi-step flows must move focus to the new step's heading and announce step changes via an ARIA live region. Send a confirmation email and SMS with the tasting date, time, and address; include a documented reschedule path.

Compliance Checklist

  • Allergen, ingredient, and cross-contamination information is published as semantic HTML tables with proper <th> headers (not photos, screenshots, or untagged PDFs)
  • Each product detail page lists the nine FALCPA major allergens with yes/no/may-contain disclosures, full ingredient list, and a plain-English cross-contamination statement
  • Menu page includes a structured allergen-filter (e.g., 'Filter to peanut-free items')
  • Every product photo has descriptive alt text in customer-meaningful terms (flavor, decoration, color palette, size), not 'cake1.jpg' or 'wedding cake'
  • Each product detail page includes a structured description with flavor, filling, frosting type, decoration style, available sizes, customization options, lead time, and allergen statement
  • Custom-cake builder uses native HTML form controls (<select>, radio buttons, <input type='number'>) with descriptive text labels, not drag-and-drop tier selectors or unlabeled color swatches
  • Live price updates in the cake builder are announced via an ARIA live region
  • Same-day-pickup date pickers use native <input type='date'> or properly-labeled <select> elements with min/max bounds and disabled states for blocked-out dates
  • Delivery-window selectors are fieldsets of radio buttons with descriptive text labels ('Today by 11:00 AM'), not color-coded buttons
  • Wedding-cake-tasting and custom-order consultation forms use proper <label> elements; allergen-and-dietary-restriction selections are a <fieldset> with a <legend>; calendar appointment-pickers allow keyboard navigation
  • Phone-and-email fallback paths are clearly published for same-day, emergency, and custom orders that the widget cannot accommodate
  • If 'gluten-free,' 'nut-free facility,' or similar allergen-claim marketing language is used, the supporting allergen disclosure is fully accessible (HTML, not images of text)
  • Accessibility statement is published, names the e-commerce and scheduling vendors, and provides a documented contact path for accessibility issues
  • Site has been audited with axe, Pa11y, or Lighthouse and manually tested with NVDA, VoiceOver, and TalkBack in the last 12 months

Further Reading

Other Industry Guides