Skip to content Skip to content

Accessibility

Accessibility Statement

Last updated: April 2026

AODA Compliant
WCAG 2.0 Level AA
OWASP Security Guidelines
IEC 62288 Marine Display

Our Commitment

AtMyBoat.com is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards to our web properties.

Standards We Follow

AtMyBoat.com aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.0, Level AA. These guidelines explain how to make web content more accessible to people with disabilities. Conformance with these guidelines helps make the web more usable for all people.

This site is also designed in compliance with the Accessibility for Ontarians with Disabilities Act (AODA), including the Integrated Accessibility Standards Regulation (IASR), as required for organizations operating in Ontario, Canada.

Measures We Have Taken

  • All text on this site meets a minimum 4.5:1 colour contrast ratio (WCAG 2.0 AA) against its background.
  • Body text is a minimum 18px throughout the site — no smaller text is used anywhere.
  • All interactive elements (buttons, links, form fields) have a minimum touch target of 48×48 pixels.
  • Every page includes a skip-to-content link as the first focusable element.
  • All images and icons include appropriate alt text or are marked as decorative.
  • All form inputs have associated labels.
  • The site is fully navigable by keyboard.
  • Focus indicators are visible on all interactive elements.
  • Page structure uses semantic HTML landmarks (main, nav, header, footer).
  • ARIA live regions are used for dynamic content updates (AI widget responses, form feedback).

Known Limitations

While we strive for full WCAG 2.0 AA conformance, some third-party components may not meet all accessibility requirements:

  • The community map (Leaflet/OpenStreetMap) is a visual tool. Map data is not available in a screen-reader-friendly format at this time. We plan to add a text-based alternative view in a future release.
  • The bbPress forum is a third-party WordPress plugin. We have not audited its full accessibility compliance.
  • The Stripe payment flow is operated by Stripe, Inc. and subject to Stripe's own accessibility commitments.

d3kOS Helm Display

The d3kOS marine navigation display (running on Raspberry Pi) is designed in compliance with IEC 62288 (Human Interface Requirements for Marine Navigation) and uses high-contrast colours, large touch targets (minimum 48px), and Fraunces/Nunito typefaces optimised for outdoor readability.

Security Practices

AtMyBoat.com designs and builds its web platform following the OWASP (Open Worldwide Application Security Project) guidelines, including the OWASP Top 10 for web applications and the OWASP Top 10 for Large Language Model (AI) applications. Security is treated as a design requirement, not an afterthought.

AI Assistant Protection

Our AI assistant is hardened against prompt injection, output manipulation, and abuse — following the OWASP LLM Top 10 framework.

Your Privacy

Questions you ask the AI are never stored or logged. Only anonymous token counts are recorded for usage monitoring.

Rate Limiting

All AI requests are rate-limited server-side to prevent abuse and protect service availability for all members.

Secure Payments

All payments are processed by Stripe, Inc. using TLS encryption. AtMyBoat.com never stores card numbers or payment credentials.

Input Validation

All user input is validated and sanitized server-side before processing. Malicious content is blocked before it reaches any external service.

HTTPS Only

All pages are served over HTTPS (TLS). Unencrypted HTTP connections are not accepted.

To report a security vulnerability, please contact us directly at skipperdon@atmyboat.com. We take all security reports seriously and aim to respond within 48 hours.

Feedback and Contact

We welcome feedback on the accessibility of AtMyBoat.com. If you experience any accessibility barriers, or if you need information in an alternate format, please contact us:

Formal Complaints (Ontario)

If you are not satisfied with our response, you may contact the Accessibility Directorate of Ontario:

This Statement

This accessibility and security statement was prepared in April 2026. It is reviewed and updated whenever significant changes are made to the site. The security section was added following the completion of OWASP LLM Top 10 hardening on the AI assistant.