A site you can actually use.

We believe a website that calls itself "engineering-led" should be usable by everyone. We've designed pittwater.co with accessibility as a baseline rather than an afterthought, and we keep working on it.

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard most US and EU jurisdictions reference. We're not currently certified by a third-party auditor; the work below is what we've done in-house.

Keyboard navigation. Every interactive element on the site is reachable via Tab. A "skip to content" link is the first focus stop on every page, letting keyboard and screen-reader users bypass the navigation. Custom focus rings (lime-on-dark, 2px with offset) make the focused element unmistakable.

Semantic HTML. Every page uses one <main> landmark, <nav> for navigation, <footer> for the footer. Headings descend in order (h1 → h2 → h3) without skipping levels. Buttons and links use the correct element rather than divs-pretending-to-be-buttons.

Reduced motion. The cinematic page transitions, the home-page protocol marquee, and any other animation respect the prefers-reduced-motion media query. Users who've asked their OS to minimise motion get instant page changes and a static protocol band.

Color contrast. All body text meets WCAG AA at 4.5:1 minimum. Our dim text (cream-dim on ink-2) measures around 7:1, well above the threshold. Lime accent on dark ink exceeds AAA.

Icon-only buttons. Close buttons, social icons, and other icon-only controls carry aria-label values describing their purpose so screen-reader users know what they do.

Form labelling. Every input on the Contact form and the Careers application form is paired with an explicit <label>. Required fields are marked visually and programmatically.

Image alt text. Brand logos, case-study photos, and other meaningful images carry descriptive alt text. Purely decorative images use empty alt to keep screen readers from announcing them.

Page transitions. The fade-to-black curtain between pages is pointer-events: none so it cannot intercept clicks, and respects the reduced-motion setting (instant nav, no curtain).

Modal dialogs. The pop-ups on the /work and /monitoring pages (case studies, the incident-detail and fleet-detail views, and the lab-readout disclaimer) follow the same accessibility pattern: they receive focus on open, lock body scroll while open, close on Escape, close on backdrop click, and carry role="dialog" + aria-modal="true" for screen readers.

We try to be honest about gaps:

- Live camera feed. The live demo's video stream from our Brookfield office does not include closed captions — there is no spoken audio to caption, but the absence may be surprising. We'll add a "no audio · video only" notice on the player if visitors ask. - Brands "Play" mode. The physics-based bouncing logo wall on the /brands page is purely decorative motion. We respect prefers-reduced-motion (it doesn't auto-start), but the toggle button itself lets you opt into the motion if you choose. - AV calculators. The Tools section's calculators (FFT analyzer, signal generator, test patterns) involve dynamic visual updates and audio output. The audio tools require an explicit "start" button — they will not autoplay sound. The visual updates may be challenging for users with photosensitivity; we add a "pause" control where applicable, and we won't ship a test pattern with rapid flashing. - Third-party embeds. The Google Maps embed on the Contact page and the Cloudflare Stream player on the live demo come with their own accessibility characteristics. We don't control their internals; if you encounter an issue with either, tell us and we'll see what we can do. - /monitoring page motion. The "live" indicator next to the status bar pulses, and rows in the "what we just did" stream flash briefly when a new event arrives. Neither animation currently shortens under prefers-reduced-motion. If this is uncomfortable, the page works correctly without the animations — they're decorative — but we'd still like to know so we can add proper reduced-motion guards in a future pass. - CMS Studio. Our internal admin interface at /studio is not designed for public use and has not been audited for AA conformance. It's not part of the public site.

We don't believe any of these issues prevent the core information on the site from being accessible. If you find that one does — or any other issue we haven't listed — please tell us.

We test the site primarily with VoiceOver on macOS Safari, NVDA on Windows Firefox, TalkBack on Android Chrome, and at zoom levels up to 200%. The site should work with most modern combinations of browser and screen reader.

If you use a less common assistive technology and run into a problem, we'd genuinely like to hear about it — that's how we get better at this.

If you encounter an accessibility barrier on this website — something you can't read, can't interact with, or can't navigate to — please tell us. We aim to respond within five business days and to fix issues as soon as we're able.

Email: hello@pittwater.co Subject line: "Accessibility — [page or feature]" Mail: Pittwater, 487 Federal Rd, Brookfield CT 06804, USA

Your feedback shapes the next round of improvements. Even minor issues are worth a note.

If you've raised an issue and feel it hasn't been adequately addressed, you may file a complaint with the appropriate authority:

- United States — US Department of Justice, ADA section - European Union — your national accessibility body under Directive (EU) 2016/2102 - United Kingdom — the Equality Advisory and Support Service

We hope it doesn't come to that. The faster path is almost always emailing us directly.