Accessibility Statement

MV Boats is committed to ensuring that our website, mvboats.com, is accessible to all individuals, including those with disabilities. We strive to provide an inclusive digital experience that meets or exceeds the requirements of applicable accessibility standards.

1. Our Commitment

This page says what we have actually checked and what we have not. It is deliberately narrower than most statements of its kind: MV Boats is one person, and a claim we cannot back is worse than no claim at all.

What we aim for:

• Providing an accessible and usable website for all visitors, regardless of ability or technology
• Meeting the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as published by the World Wide Web Consortium (W3C). Every build is tested against it automatically. There has been no independent audit, so we say “meeting” and not “certified”.
• Complying with the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act
• Continuously improving accessibility as technologies and standards evolve

2. Accessibility Features

Our website incorporates the following accessibility features:

Navigation & Structure

• Skip navigation link: A “Skip to content” link is provided at the top of every page, allowing keyboard users to bypass repetitive navigation
• Semantic HTML: We use proper heading hierarchy (h1–h6), landmarks (<nav>, <main>, <footer>), and semantic elements to ensure screen readers can navigate content effectively
• Consistent navigation: The navigation menu is consistent across all pages, with clear labels and logical ordering
• Logical tab order: Interactive elements follow a natural, logical focus order

Visual Design

• Color contrast: Text and interactive elements maintain sufficient contrast ratios against background colors, meeting WCAG 2.1 AA requirements
• Resizable text: All text is set using relative units (rem, em, clamp) and scales appropriately when users increase browser font sizes up to 200%
• Responsive design: The Site adapts to various screen sizes, orientations, and zoom levels, ensuring usability on mobile devices, tablets, and desktops
• No reliance on color alone: Information is not conveyed solely through color; text labels, icons, and other visual indicators are also used
• Reduced motion: Animations and transitions respect the prefers-reduced-motion operating system setting

Keyboard Accessibility

• Full keyboard navigation: All interactive elements (links, buttons, forms, modals) are accessible via keyboard
• Visible focus indicators: Focused elements display visible outlines or highlights to indicate the current position
• Escape key support: Modals and overlays can be closed using the Escape key
• No keyboard traps: Users can navigate freely without becoming trapped in any component

Images & Media

• Alternative text: All meaningful images include descriptive alt attributes. Decorative images are marked appropriately so screen readers can skip them
• Responsive images: Images use srcset and sizes attributes to load appropriate sizes for different devices

Forms & Interactive Elements

• Labeled form fields: All form inputs have associated labels, placeholders, or aria-label attributes
• Error identification: Form validation errors are clearly identified and described in text
• ARIA attributes: Interactive components use appropriate ARIA roles, states, and properties where native HTML semantics are insufficient
• Button labels: All buttons have accessible names, either through visible text or aria-label attributes

3. How this is tested, and what that misses

Every build runs axe-core against eleven pages at WCAG 2.1 A and AA plus its best-practice rules, and a violation fails the build. The check lives in the test suite rather than in somebody’s memory, so it cannot quietly stop running.

It found six real problems the first time it ran, in September 2026: a form control with no accessible name, an invalid definition list, links in body text distinguished only by colour, a dimmed panel whose text fell under the contrast floor, a skipped heading level, and two unnamed navigation landmarks. All six are fixed.

Automated testing catches roughly half of what matters. We have not done the following, and will keep saying so until we have:

• Testing with a real screen reader, no JAWS, NVDA, VoiceOver or TalkBack session has been run against this site
• Testing with voice control, switch access or screen magnification
• Any independent or third-party accessibility audit
• Testing with disabled users

Keyboard navigation, focus visibility, text at 200% and reduced-motion behaviour have each been checked by hand.

4. Browser Support

For the best accessible experience, we recommend using the latest versions of the following browsers:

• Google Chrome
• Mozilla Firefox
• Apple Safari
• Microsoft Edge

5. Known limitations

• Third-party embeds: the payment step is hosted by Stripe and the contact form posts to Formspree. Their accessibility is theirs, and we cannot fix it from here.
• Operator websites: every charter operator we list runs their own site. We link to them; we do not control them, and several are older sites that will not meet AA.
• Motion: content reveals as you scroll. That is switched off entirely for anyone whose system asks for reduced motion, but motion is the default.
• The seasonal guide is a PDF and has not been tagged for screen readers. Ask and we will send the same content as plain text.

6. What happens next

The automated check runs on every build and blocks a release that fails it. Beyond that, the honest position is that a screen-reader pass is the largest remaining gap, and it is the next thing worth doing. If you use one and something here does not work, telling us is worth more than any audit we could buy.

7. Feedback & Assistance

We welcome your feedback on the accessibility of mvboats.com. If you encounter any accessibility barriers, have difficulty accessing any content, or need information in an alternative format, please contact us:

MV Boats
Email: [email protected]
Subject line: Accessibility Feedback

When contacting us about an accessibility issue, please include:

• A description of the problem you encountered
• The page URL where the issue occurred
• The assistive technology or browser you were using
• What you were trying to do, and what happened instead

One person reads that address. You will get a reply, usually within a few days, and a straight answer about whether and when it can be fixed.

8. Legal Compliance

This accessibility statement is provided in accordance with:

• Americans with Disabilities Act (ADA), Title III: Ensuring equal access to places of public accommodation, which courts have interpreted to include websites
• Section 508 of the Rehabilitation Act: Federal accessibility requirements for electronic and information technology
• Web Content Accessibility Guidelines (WCAG) 2.1, Level AA: The internationally recognized standard for web accessibility
• European Accessibility Act (EAA): For visitors from the European Union, we aim to comply with applicable accessibility directives
• EN 301 549: The European standard for ICT accessibility requirements

9. Accessibility Statement Updates

This statement is reviewed and updated periodically. The “Last updated” date at the top of this page reflects the most recent revision. We will post any material changes to this statement on this page.