Instaustad's Approach to Accessibility

Accessibility is one of those things that's easy to treat as a checkbox rather than an ongoing responsibility. Here's an honest account of where things actually stand.

What we've built with accessibility in mind

Every interactive element on the site — buttons, links, form fields — is built to be reachable and usable with a keyboard alone, not just a mouse or touchscreen. Form fields have proper labels that screen readers can announce correctly, rather than relying only on placeholder text, which disappears the moment you start typing and isn't reliably read by assistive technology in the first place.

Color choices are checked for reasonable contrast between text and background, since low-contrast text is one of the more common accessibility failures on the web. We also respect a visitor's reduced-motion preference, so animations and transitions are minimized or removed for anyone who's set that preference at the operating system level.

Where we're honestly still catching up

We haven't run a full, formal accessibility audit against a standard like WCAG, and we're not going to claim a level of compliance we haven't actually verified. There are likely edge cases we haven't caught — a focus state that's harder to see than it should be in some browsers, or a page structure that could be clearer for screen reader navigation in a specific spot. We'd rather say this plainly than imply a level of polish we haven't confirmed.

Why this matters for a site like ours specifically

A tool built around reading and copying text should, at minimum, be genuinely usable by people who rely on screen readers or keyboard navigation — the irony of an inaccessible text-reading tool isn't lost on us. Getting this right isn't optional for the kind of site we're trying to be.

How to tell us if something isn't working for you

If you use assistive technology and run into something on this site that doesn't work the way it should, please tell us through the contact page, with as much detail as you can about what you were trying to do and what happened instead. Accessibility issues are often invisible to people who don't rely on the specific tool or setting involved, so direct reports are one of the only reliable ways we find out.

We intend to run a more thorough review over time rather than waiting for every issue to be reported individually, but we'd rather be honest that this is a work in progress than pretend it's already finished.