Coastal Bay Digital LLC is committed to making DeweyIQ usable by everyone who needs it — the pool pros who run their business on it, and the homeowners who use the customer portal. This statement describes where we actually stand, including what is not fixed yet.
Our commitment
Accessibility is treated as part of building the product, not as a pass we make afterward. New interface work is reviewed against the standard below before it ships, and reported barriers are handled as defects rather than feature requests.
We do not use an accessibility overlay, toolbar, or widget. Those tools do not make a site conformant, they frequently interfere with the assistive technology a person already has configured, and marketing them as automatic compliance has drawn federal enforcement. We fix the underlying code instead.
The standard we follow
DeweyIQ targets Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This covers the DeweyIQ marketing site, the DeweyIQ web application, the field technician app, and the customer portal.
WCAG 2.1 Level AA is the standard referenced by the U.S. Department of Justice for Title II entities, by Section 508 for federal procurement, and by EN 301 549 in the EU, so meeting it is what lets a municipality, parks district, or enterprise buyer procure DeweyIQ.
Conformance status
Partially conformant with WCAG 2.1 Level AA. “Partially conformant” means most of the product meets the standard, but some content does not yet fully conform. The specific gaps are listed under Known limitations.
We are stating this rather than claiming full conformance because we have not completed an independent third-party audit. When we do, we will publish the result here and update this section.
What we have done
In July 2026 we completed an accessibility review across the entire product and remediated what it found. That work included:
- Color contrast. Our brand color was darkened so that text and interface components set on it clear the 4.5:1 and 3:1 contrast thresholds, and secondary text was adjusted for the same reason. Both the light and dark themes were corrected. (1.4.3, 1.4.11)
- Keyboard operability. Interactive controls are reachable and operable by keyboard, with a visible focus indicator that is not suppressed. (2.1.1, 2.4.7)
- Skip navigation. A “Skip to main content” link is the first focusable element on every page, so keyboard and screen reader users are not forced through the navigation on each load. (2.4.1)
- Reduced motion. Decorative, looping, and transform-driven animation is neutralized for anyone whose system requests reduced motion. Essential feedback — focus, hover, opening and closing — is deliberately kept, because removing it would remove information. (2.3.3)
- Structure and labels. Landmarks and heading order, accessible names on icon-only controls, labeled form fields, and error messages that name the field and the problem in text rather than color alone. (1.3.1, 1.4.1, 3.3.1, 3.3.2, 4.1.2)
- Responsive layout. Content reflows on small screens and under zoom without horizontal scrolling or loss of function. (1.4.10)
Known limitations
Despite the work above, the following are not yet at Level AA. Each entry names the affected WCAG success criteria and what you can do today.
- Interactive mapsWCAG 1.1.1, 2.1.1, 4.1.2
Route, dispatch, and service-area maps draw their stops onto a canvas layer that screen readers cannot enumerate, and markers are not reachable by keyboard.
What to do instead: Every map is a secondary view of data that also exists as a list. The tech route screen opens on the stop list by default; the map is a toggle, not the only way through.
- Charts and dashboardsWCAG 1.1.1, 1.3.1
Reporting charts render as SVG with limited structural semantics, so a screen reader announces the chart region but not the series values.
What to do instead: The underlying figures are shown as labeled numbers and tables on the same screens. Report exports contain the same values as text.
- Generated PDFsWCAG 1.3.1, 1.3.2
Invoices, statements, agreements, purchase orders, and financial reports are generated as untagged PDFs, so reading order and table structure are not exposed to assistive technology.
What to do instead: Every one of these documents is also available as an HTML screen in the app or the customer portal, which is the accessible path. Ask us and we will send any document in an accessible format.
- Embedded payment fieldsThird-party component
Card entry fields are embedded directly from our payment processor. We do not control their markup and cannot remediate them ourselves.
What to do instead: Customers can pay by any other method their pool company accepts. We track the processor's conformance and will change providers if it does not hold.
- Screen reader coverageAssessment gap
Our July 2026 review was automated testing plus manual keyboard and contrast testing. Full manual screen reader testing across every workflow is in progress, not finished.
What to do instead: Tell us where you got stuck and we will prioritize that workflow. See Report a barrier below.
If a barrier you hit is not on this list, we have not found it yet. Please tell us — that is how it gets fixed.
Compatibility
DeweyIQ is built to work with current versions of Chrome, Edge, Safari, and Firefox on desktop, and Safari on iOS and Chrome on Android on mobile, each paired with the platform screen reader. It is not tested against browsers more than two major versions old, and Internet Explorer is not supported.
DeweyIQ relies on JavaScript. Where a feature depends on a device capability such as location or the camera, we ask for permission at the moment you use the feature and the surrounding screen stays usable if you decline.
Report a barrier
If any part of DeweyIQ blocks you, tell us and we will treat it as a defect. You do not need to identify the WCAG criterion or use any particular wording — describing what you were trying to do and what happened is enough.
- Email: hello@DeweyIQ.com — put “Accessibility” in the subject line so it routes correctly.
- Phone: (234) 339-3947, Monday to Friday, 9:00am–5:00pm Eastern.
- Web: our contact form.
We aim to acknowledge accessibility reports within 2 business days and to come back with either a fix or a dated plan within 10 business days. If we cannot fix something quickly, we will tell you the workaround and add it to the limitations table above.
If we do not resolve your report to your satisfaction, you can contact the U.S. Department of Justice ADA Information Line at 800-514-0301 (TTY 800-514-0383) or file a complaint at ada.gov.
Procurement & VPAT
Government, education, and enterprise buyers usually need an Accessibility Conformance Report based on the Voluntary Product Accessibility Template (VPAT), covering WCAG 2.1 AA, Section 508, and EN 301 549. We are preparing one. Until it is published, email hello@DeweyIQ.com and we will send the current conformance detail and the remediation schedule for the items listed above.
DeweyIQ is not currently offered in the European Union. If that changes, we will publish the accessibility statement the European Accessibility Act requires.
How we assessed this
This statement reflects a self-assessment completed in July 2026, carried out by Coastal Bay Digital LLC using automated testing across the application together with manual keyboard-only and contrast testing. It has not been independently audited, and manual screen reader testing is still in progress.
We review this statement at least every six months, and whenever we ship a change that affects anything described here. It was last reviewed on August 14, 2026. Next scheduled review: February 2027.