Solomia EventsSouth Florida
Prelaunch preview. Dates and services are confirmed only in writing.

Accessibility statement

Access is part of the hospitality plan.

The website is being designed toward WCAG 2.2 Level AA and for practical keyboard, screen-reader, zoom, motion, contrast, and form use.

Draft reviewed July 20, 2026

If a page or task is difficult to use, describe the URL, task, device, browser, and assistive technology in the contact form. Do not include sensitive health information.

Features built into the current experience

  • A keyboard-accessible skip link and semantic page landmarks.
  • Visible focus treatment and minimum-size interactive controls.
  • Meaningful labels, instructions, error associations, and status announcements on inquiry forms.
  • Responsive layouts intended to reflow without removing critical mobile functionality.
  • Text alternatives for informative images and empty alternatives where imagery is decorative.
  • Disclosure where media is conceptual rather than completed-event photography.
  • Reduced-motion support and a poster-first hero-media approach that considers reduced-motion and data-saving preferences.
  • Plain-language distinctions between starting prices, estimates, proposals, and confirmed bookings.

Known limitations

  • Automated and manual accessibility testing must be completed against the deployed production build, not only local source code.
  • Generated-image alternative text and public disclosures require editorial review alongside each final asset.
  • Third-party checkout, authentication, calendar, map, consent, or messaging interfaces may have accessibility behavior outside this site’s direct control.
  • No verified public phone or email alternative is currently published; the web contact form is the available feedback route.
  • A complete screen-reader matrix, high-contrast review, 200% and 400% zoom review, and mobile assistive-technology pass remain launch checks.

Testing and maintenance approach

The launch process should combine automated checks with keyboard-only navigation, screen-reader sampling, zoom and text-spacing tests, contrast review, reduced-motion review, touch-target checks, and real-device testing. Automated tools cannot establish conformance by themselves.

Accessibility issues should be prioritized by whether they block a core task such as comparing packages, understanding a policy, submitting an inquiry, reviewing a proposal, or completing payment.

Event accessibility

Website accessibility does not guarantee that every shoreline is physically accessible. Sand, slopes, carry distance, boardwalks, parking, drop-off, restrooms, heat, and tides can create barriers.

Clients can share functional needs during planning so the team can compare routes, seating, shade, restrooms, transport, private-property alternatives, and other reasonable options. Specific accommodations and availability must be confirmed for the chosen site and vendors.

Request help or report a problem

Use the contact form and begin the message with “Accessibility.” Include what you were trying to do and the page where the barrier occurred. An equivalent format or alternate planning route can be discussed, but timing and availability are not guaranteed in this draft statement.