Wedding Planner & Event Coordinator Website Accessibility Guide 2026 | ADA, EAA, Booking Forms, Vendor Galleries

Last updated: 2026-05-12

Wedding planners, event coordinators, destination-wedding designers, and corporate-event producers run a business that lives almost entirely inside a website: the public-facing portfolio, the inquiry-and-consultation form, the vendor-partner gallery, the styled-shoot Pinterest-board imports, the questionnaire that captures the couple's color palette and budget, the RSVP and wedding-website builder, the day-of timeline shared with vendors, and the post-event gallery delivery are all digital experiences and are increasingly the only channel through which prospects evaluate the planner before signing a $15,000–$150,000 contract. Following Robles v. Domino's Pizza (9th Cir. 2019), a planner'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 wedding planners 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 inquiry forms, image-only inspiration galleries, and inaccessible RSVP-website builders that the planner resells to couples. The visual-first, Pinterest-aesthetic templates that dominate the industry—Showit, Squarespace 7.1, The Knot Pro, Aisle Planner, HoneyBook portals—each ship with their own systemic accessibility failures. The customers most affected are disproportionately the couples who matter most to a planner's brand: a blind bride evaluating planners for a destination wedding, a deaf groom whose family includes deaf interpreters, a wheelchair-using mother of the bride trying to confirm venue ADA access, an autistic couple needing sensory-friendly accommodations. Planners marketing to EU-resident couples face EAA exposure as of June 28, 2025, with explicit e-commerce provisions for digital-service sales (online courses, planner templates, RSVP-website subscriptions). This guide covers the legal framework, the planner-specific failure patterns, and a concrete compliance checklist.

Legal Requirements

Law / Standard Effective Date Summary Penalty
ADA Title III In effect Wedding planners and event coordinators are places of public accommodation under ADA Title III in most U.S. circuits. The website is the primary lead-generation, consultation-booking, vendor-portfolio, and RSVP-builder 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 Planners marketing destination weddings to EU-resident couples, EU-based event coordinators, or planners selling digital products (RSVP-website subscriptions, planner templates, online courses, downloadable spreadsheets, wedding-timeline apps) to EU residents must bring their consumer-facing 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. The EAA explicitly lists 'consumer-facing e-commerce services' as a covered service, which includes the planner's online checkout, digital-product delivery, and subscription-based RSVP-website resale. 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.
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, with statutory damages that exceed bare federal injunctive relief. 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 'inclusive wedding planning' marketing) In effect Where the planner's website prominently advertises 'inclusive weddings,' 'accessible weddings,' 'weddings for every couple,' or similar diversity-and-inclusion marketing language but the website itself is not accessible, 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. We have no data on how often this pattern is pleaded alongside accessibility allegations and do not assert that it is common or that it affects settlement posture. FTC enforcement (rare for SMBs); state-AG enforcement and private causes of action under state UDAP statutes; restitution and treble damages in some states.
DOJ Title II Final Rule (28 CFR Part 35, Subpart H) 2027-04-26 / 2028-04-26 Planners that hold a contract with a public university, public-museum event venue, public library, state-park wedding venue, or county-run convention center to coordinate events are sub-contractors of a public entity. The DOJ's 2024 Title II Final Rule extends to information and services provided by sub-contractors on behalf of the public entity, including the planner's online consultation, vendor-selection, and RSVP-coordination flows used by event attendees. Compliance deadline: April 26, 2027 for jurisdictions serving 50,000 or more people; April 26, 2028 for smaller jurisdictions. Loss of public-venue vendor-list eligibility; DOJ enforcement; private litigation with attorneys'-fee shifting under 42 U.S.C. §12133.

Key Accessibility Issues in Wedding Planners & Event Coordinators

Inspiration Galleries and Styled-Shoot Portfolios Without Descriptive Alt Text

The inspiration gallery is the planner's single most powerful sales tool and is almost universally a wall of images with empty, filename, or theme-imported alt text ('IMG_3892.jpg', 'styled-shoot-final', 'wedding'). A blind bride evaluating whether a planner's aesthetic matches her vision—rustic-boho, modern-minimalist, classic-romantic, cultural-fusion—has no information from the gallery at all. Pinterest-board imports drag in alt text that describes the original pin context ('repinned from @brittanyfloraldesign'), not the visual content. Masonry-grid and lightbox-overlay implementations common to Showit, Squarespace, and HoneyBook portfolio modules typically also fail focus management when an image is opened in the lightbox, trapping screen-reader users or losing their place in the gallery entirely.

How to fix:

Write descriptive alt text for every gallery image in customer-meaningful aesthetic terms ('Outdoor garden ceremony with white wooden arch draped in greenery and ivory ribbon, rows of wooden cross-back chairs facing arch, blush rose petal aisle, photographed at golden hour' or 'Modern minimalist reception table with black linen runner, white plates, black-stemmed wine glasses, single white anthurium centerpieces, taper candles in black holders'). For Pinterest-imported pins, overwrite the imported alt text with custom descriptions. Lightbox modals must trap focus when opened, return focus to the originating thumbnail on close, and expose Previous/Next/Close as keyboard-operable buttons with visible focus indicators. Include a structured caption beneath each gallery section explaining the overall aesthetic and event type.

Consultation-Inquiry Forms Built on HoneyBook, Aisle Planner, and Dubsado With Placeholder-Only Labels

The consultation-inquiry form is where the $20,000–$150,000 sales cycle begins, and the CRM platforms common in the wedding-planning niche (HoneyBook, Aisle Planner, Dubsado, 17hats, Táve and others) each generate their own inquiry-form embed, so test the embed you actually use with a keyboard and a screen reader rather than assuming it is accessible. The most common pattern is placeholder-only labels: the 'Bride's Name' label disappears the moment the user starts typing, and screen readers either fail to read the label at all or read 'edit text' with no context. Wedding-date fields use custom calendar widgets that cannot be operated with a keyboard. Budget-range selectors are color-coded card grids without text labels. Multi-step flows ('About You,' 'About Your Wedding,' 'Inspiration Upload') lose screen-reader users' place between steps. Couple-of-two forms that allow the second partner to be added later fail to announce the dynamic field-group change.

How to fix:

Use proper <label> elements—not placeholder text—for every form input. Wedding-date inputs must be native <input type='date'> with min/max bounds, not custom calendars. Budget-range selectors must be radio buttons or <select> elements with descriptive labels ('Under $20,000', '$20,000–$40,000', '$40,000–$80,000', '$80,000–$150,000', 'Over $150,000'). Multi-step flows must move focus to the new step's heading and announce step changes via an ARIA live region ('Step 2 of 4: About Your Wedding'). When a second partner is added, focus must move to the new field group and the change must be announced. Provide a plain email-and-phone alternative inquiry channel documented in the accessibility statement.

Vendor-Partner Galleries and Preferred-Vendor Lists That Block Couples With Disabilities From Identifying Accessible Vendors

Planners typically maintain a preferred-vendor list (photographers, florists, caterers, DJs, officiants, rental companies) that the couple uses to assemble their team. The preferred-vendor directory is most often implemented as a styled card grid of vendor logos linking to vendor websites, with no information about each vendor's accessibility posture and no way for the couple to filter by wheelchair-accessible venues, sign-language-interpreter-friendly officiants, or sensory-friendly DJs. Critically, the preferred-vendor list is itself a contractual referral chain: when the couple's disabled guest is excluded by an inaccessible vendor the planner recommended, the planner is named in the resulting complaint.

How to fix:

Rebuild the preferred-vendor directory as a filterable HTML table or list with vendor name, service type, geographic range, and explicit accessibility-posture columns ('Wheelchair-accessible venue', 'Sign-language interpreter available', 'Sensory-friendly DJ setup', 'Accessible website with VPAT'). Require every preferred vendor to complete a short accessibility questionnaire annually and document the response. Vendor logos must be <img> elements with descriptive alt text including vendor name and service type. Add a clearly-named 'Accessibility considerations for your wedding' page to the planner site that walks couples through venue-accessibility questions, guest-accommodation planning, and vendor-vetting checklists.

RSVP-Website Builders Resold to Couples That Inherit the Vendor's Accessibility Defects

Many planners resell or recommend an RSVP-website builder (Joy, Zola Wedding, The Knot Wedding Websites, Riley & Grey, Aisle Planner couple-facing site, Withjoy) as part of the planning package. The couple's wedding guests—who include older relatives, disabled guests, and international family members—then use that site to RSVP, view registry, view travel-and-accommodation information, and view the day-of timeline. The default templates in every major RSVP builder have well-documented accessibility defects: video-background hero sections that autoplay with audio, image-only registry-item cards, multi-step RSVP forms with no error-summary on validation failure, and drag-and-drop seating-chart editors that cannot be operated with a keyboard. The planner is the party that selected, configured, and recommended the tool; the guests are the third parties harmed; the couple is the contractual middleman.

How to fix:

Before recommending an RSVP-website-builder vendor to clients, demand a current VPAT or Accessibility Conformance Report from the vendor and test the live RSVP flow with NVDA or VoiceOver and at 200% zoom. Configure the couple's wedding site to disable video autoplay, use templates that have documented accessibility commitments, and provide a phone-and-email RSVP fallback for guests who cannot use the website. Document the planner's RSVP-builder selection process and vendor-due-diligence record in the accessibility statement. When the vendor cannot produce a VPAT, switch.

Pinterest-Style Mood Boards, Color-Palette Pickers, and Inspiration Uploads Without Keyboard or Screen-Reader Support

The questionnaire that captures the couple's vision typically includes a color-palette picker, a Pinterest-board import or inspiration-image upload, and a mood-board builder. These tools are almost universally implemented as custom JavaScript widgets that fail every basic accessibility test: the color-palette picker is a draggable color wheel with no keyboard alternative; the Pinterest import is a third-party iframe with no title attribute; the inspiration upload is a drag-and-drop dropzone with no <input type='file'> fallback; the mood-board builder is a draggable canvas that is invisible to screen readers entirely. A blind bride trying to convey her aesthetic vision to the planner cannot use any of these tools and is forced into a phone-call-only intake that the planner's CRM is not designed to capture.

How to fix:

Replace drag-and-drop color pickers with a set of labeled color-swatch radio buttons or a labeled <input type='color'> with associated text-label override ('Sage green', 'Dusty blue', 'Champagne ivory'). Pinterest-board imports must accept a plain URL paste as an alternative to the iframe import. Inspiration uploads must offer a standard <input type='file' multiple> control alongside the drag-and-drop dropzone. Mood-board builders must be skippable: provide a 'Describe your vision in words instead' free-text field as a documented alternative. Capture phone-call intake notes directly into the same CRM record as the digital questionnaire so the planner's workflow is identical for screen-reader and sighted clients.

Compliance Checklist

  • Every inspiration-gallery and styled-shoot portfolio image has descriptive alt text in aesthetic terms (aisle setup, color palette, lighting, decor), not 'IMG_3892.jpg' or Pinterest-imported repin text
  • Lightbox modals trap focus when opened, return focus to the originating thumbnail on close, and expose Previous/Next/Close as keyboard-operable buttons with visible focus indicators
  • Consultation-inquiry forms (HoneyBook, Aisle Planner, Dubsado, 17hats, Táve) use proper <label> elements (not placeholder text), with native date pickers, radio-button budget selectors, and accessible multi-step flows
  • Couple-of-two and family-add inquiry flows announce dynamic field-group changes via ARIA live region and move focus to the new field group
  • Preferred-vendor directory is a filterable HTML table or list with vendor accessibility-posture columns; vendors complete an annual accessibility questionnaire
  • An 'Accessibility considerations for your wedding' page walks couples through venue, guest, and vendor accessibility planning
  • Recommended RSVP-website-builder vendor has a current VPAT, has been tested live with NVDA/VoiceOver, and the couple's site disables video autoplay and provides a phone/email RSVP fallback
  • Color-palette pickers, Pinterest-board imports, inspiration uploads, and mood-board builders all provide keyboard-operable and screen-reader-friendly alternatives, including a 'Describe your vision in words' free-text fallback
  • Phone-and-email alternative inquiry, consultation, and intake channels are clearly documented in the accessibility statement
  • Showit, Squarespace, and HoneyBook portfolio templates have been audited on both desktop and mobile (Showit ships two canvases)
  • If the planner holds a public-university, public-museum, public-library, or state-park venue vendor contract, the contract has been reviewed for accessibility requirements flowed down from the venue's own ADA Title II duties. Title II binds the public venue, not the planner; DOJ's dates for public entities are April 26, 2027 (larger entities) and April 26, 2028 (smaller entities)
  • Accessibility statement is published, names the CRM and RSVP-builder 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