Accessibility Statement

Last reviewed: May 2, 2026

Website Bonanza, a brand of MF Automations LLC, is committed to making our website and the websites we deliver to customers accessible to people with disabilities. We believe that the open web should be usable by everyone, regardless of ability or assistive technology.

1. Conformance Target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA for our marketing site (thewebsitebonanza.com), our customer portal (portal.thewebsitebonanza.com), and the websites we deliver to paying customers. WCAG 2.1 AA is the standard referenced by the Americans with Disabilities Act (ADA) Title III as applied to commercial websites in cases such as Robles v. Domino's Pizza, and is the legal benchmark adopted by Section 508 of the U.S. Rehabilitation Act and the EU Web Accessibility Directive.

2. Current Status — Partial Conformance

We currently consider our site to be in partial conformance with WCAG 2.1 Level AA. "Partial conformance" means that some parts of the site do not yet fully meet the standard, but the bulk of the user journey (browsing slots, checking out, signing in, viewing your project, sending messages, downloading deliverables) has been built with accessibility in mind. Specifically, we have implemented:

Semantic HTML landmarks (<header>, <main>, <nav>, <footer>) so screen readers can navigate page structure.
A "Skip to main content" link as the first focusable element on every page.
Color-contrast ratios that meet or exceed 4.5:1 for body text and 3:1 for large text against our dark theme.
Keyboard-operable interactive elements — every button, link, and form control can be reached and activated using only Tab, Shift+Tab, Enter, and Space.
Visible focus indicators on all focusable controls.
Alt text on meaningful images; decorative graphics use empty alt="".
Form fields with associated <label> elements and inline error messages tied to inputs via aria-describedby.
Responsive layout that reflows down to 320 px wide without horizontal scrolling.
An accessible cookie-consent banner with a keyboard-reachable Decline option that does not autofocus.

3. Areas Under Active Improvement

We know we are not yet fully there. The following items are tracked and are being actively addressed:

Automated audits in CI. We are integrating axe-core into our build pipeline so that every change is checked against WCAG rules before merging. (Tied to gap #37 in our internal backlog.)
Portal aria coverage. Our customer portal has minimal aria-label coverage on icon-only buttons. We are adding accessible names to every icon-only control.
Focus management on route changes. Our single-page-app navigation in the portal does not yet move focus to the new page heading on route change. We are adding this.
Color-blind-safe charts. Where we display analytics charts, we are auditing palettes for distinguishability under deuteranopia, protanopia, and tritanopia simulations.
Customer-delivered websites. Each website we build for a customer goes through a manual accessibility review against WCAG 2.1 AA before delivery, but we are formalizing this into a documented checklist provided alongside the source-code handoff.
Captions / transcripts. We do not currently host video or audio content. If we add such content, we will provide captions and transcripts.

4. Limitations & Alternatives

Despite our efforts, some content may not be fully accessible. Known limitations include:

Third-party content embedded by customers in their delivered sites (e.g., a third-party booking widget a customer asks us to embed) may not meet WCAG 2.1 AA. We will flag this at delivery time.
Stripe Checkout (used during deposit payment) is operated by Stripe, Inc. We rely on Stripe's accessibility commitments; report issues with Checkout to Stripe support directly.
Some animations on the marketing landing page may auto-play. Users who have set prefers-reduced-motion in their OS settings will see static fallbacks; if you encounter motion that does not respect this preference, please report it.

If any limitation prevents you from completing a task on our site, please contact us at [email protected] and we will provide an alternative path (for example, completing checkout by phone or email).

5. Assistive Technologies We Test Against

We test against the most-recent stable version of:

NVDA on Firefox (Windows)
VoiceOver on Safari (macOS and iOS)
TalkBack on Chrome (Android)
Keyboard-only navigation in Chrome and Firefox (no mouse)
200% browser zoom and 400% zoom with reflow

6. Reporting an Accessibility Issue

If you encounter an accessibility barrier on Website Bonanza or on a website we delivered to you, please tell us. We treat accessibility reports as priority bug reports.

Email: [email protected] (subject line: "Accessibility issue")
Phone: +1 (305) 204-3886 (Mon–Fri, 9am–6pm ET)
Mail: MF Automations LLC, Attn: Accessibility, 8025 NW 4th Avenue, Miami, FL 33150, United States

When reporting, please include:

The page URL where the issue occurred.
A description of the problem and what you expected to happen.
The assistive technology and browser you were using (if applicable).

We aim to respond to accessibility reports within 2 business days and to resolve confirmed Level AA failures within 30 days, depending on complexity.

7. Formal Complaints

If you are not satisfied with our response, you may file a complaint with the U.S. Department of Justice Civil Rights Division at civilrights.justice.gov, or with the equivalent regulator in your jurisdiction. Nothing in this statement waives your rights under the ADA, Section 508, the EU Web Accessibility Directive, or other applicable law.

8. Review Cadence

This statement is reviewed at least annually and after any significant change to our site. The "Last reviewed" date at the top of this page reflects the most recent review.