1. Our commitment
Lake Pulse is committed to making our website, portal, and mobile app usable by everyone who cares about their lake, including people who use screen readers, keyboard navigation, magnification, or other assistive technology.
2. Standard we work toward
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines are the widely accepted benchmark for making digital content perceivable, operable, understandable, and robust.
3. What we have implemented
- Semantic HTML with a single, meaningful heading structure per page.
- Keyboard access to all interactive controls, with visible focus states.
- Text and interface color contrast checked against WCAG AA thresholds.
- Descriptive alternative text on informative images.
- Labeled form fields with clear, text-based error messages.
- Responsive layouts that reflow at 320px width and support zoom to 200%.
- Respect for reduced-motion preferences in animations.
4. Known limitations
Some areas are still being improved. We are aware of the following:
- Complex data visualizations and maps may be difficult to interpret without sight. We provide data tables or summaries on request.
- Third-party content — embedded videos, payment forms, and vendor documents — may not fully meet our standard.
- Older PDF reports may lack full tagging. We will supply an accessible version on request.
5. Requesting assistance or an alternate format
If any part of Lake Pulse is not accessible to you, we will help directly and provide the information in another format — a phone walkthrough, a plain-text summary, or an accessible document. There is no charge for this.
6. Reporting a barrier
Email info@lakepulse.co with the page address, what you were trying to do, and the assistive technology and browser you use. You can also use our contact form.
We acknowledge accessibility reports within 2 business days and aim to resolve confirmed barriers within 30 days, or explain the timeline if a fix will take longer.
7. Assessment and review
We evaluate accessibility using a combination of automated testing, keyboard and screen reader review, and manual contrast checks during design and development. This statement is reviewed at least annually and after significant changes to the platform.


