Accessibility

This site has not been fully audited, so you won't find a conformance claim on this page.

Most accessibility statements open by promising WCAG 2.1 AA. We sell audits for a living, and we've written about why a cookie banner that offers a choice the site doesn't honor leaves a business worse off than no banner at all: the promise goes on the record and the behavior contradicts it. Publishing an unverified conformance claim here would be that same mistake, on our own house. What follows is the real state of it.

What we have actually tested

On July 26, 2026 we ran axe-core 4.12.1 against the WCAG 2.1 A and AA rule sets, in a desktop Chromium browser at 1280 pixels wide, on five pages:

• The home page
• Contact
• Contractors and trades
• Website Privacy Audit
• The LJM Construction case study

Three of those five returned no automated violations. We also checked the footer's contrast by hand, compositing each translucent text color over the dark green behind it, because automated tools skip the pairs they cannot resolve. The tightest one measured 4.81:1 against a 4.5:1 requirement. It passes, with very little room.

Automated testing catches roughly a third of real accessibility problems. It is a floor, not a verdict.

What we found and have not fixed

Case study statements get read twice. The large scroll-in lines on the three case study pages render every word twice, once faint and once animated, and neither copy is hidden from assistive technology. A screen reader announces "You You don't don't lose lose jobs jobs on on the the work." Anyone browsing with reduced motion turned on gets clean text, so this only reaches people who don't.

A label on the Website Privacy Audit page fails contrast. The brass "The free tool" label measures 2.81:1 against the cream behind it, and it needs 4.5:1. Our own written design rules say brass never carries text on a light surface, so this one is us breaking a rule we wrote down.

A button on that same page is reachable but never announced. The animated console in the hero is hidden from screen readers on purpose, since it is decoration. Its "Reject all cookies" button is still in the keyboard tab order, so someone tabbing through the page lands on a control their screen reader says nothing about.

All three are small fixes. They are logged, and this page changes when they ship, not when we decide to do them.

What we have not checked at all

The gaps in the testing matter as much as the gaps in the site:

• No testing with a real screen reader. No VoiceOver, no NVDA, no JAWS.
• No full keyboard walkthrough. We confirmed focus styles exist in the stylesheet, not that every control shows a visible one.
• No zoom or reflow testing at 200 percent.
• No testing on a phone, and no touch targets measured.
• Nothing past the first step of the guided brief, which is a multi-step flow we have not audited.
• Twenty-five of the site's thirty page templates, including the blog, the city pages, and the free tools.

The standard we are working toward

WCAG 2.1 Level AA. That is a target and not a description of where this site is today. When we can say a page conforms because it was tested rather than because it was built carefully, this page will say so, page by page, with the date.

Telling us about a problem

Email hello@sealandco.studio. Tell us which page, what happened, and if you know them, your browser and any assistive technology you were using.

One person reads that inbox. You'll get a reply within two business days and a straight answer about whether we can fix it and roughly when. If something here is blocking you from reaching us or getting information you need, say that, and we'll get it to you another way while the fix waits its turn.

Last reviewed

July 26, 2026. We re-run this when the findings above are fixed, or in three months, whichever lands first.