Accessibility, by design.

Readable by everyone who needs it.

We build Octus to be usable by as many people as possible, regardless of device, browser, or assistive technology.

Accessibility is not a compliance checkbox for us. The whole company exists to make proof legible to the people who need to act on it, so a site some readers could not use would contradict the point.

This statement explains the standard we hold ourselves to, what we have built in, where we know we still fall short, and exactly how to tell us when something blocks you.

WCAG 2.2, level AA.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the benchmark most widely referenced by accessibility law in the United States and abroad.

WCAG is organized around four principles. Content should be:

• PerceivableText alternatives for non-text content, sufficient color contrast, and layouts that reflow without loss of meaning.
• OperableEverything reachable and usable by keyboard alone, with no time traps and no motion that cannot be turned off.
• UnderstandablePredictable navigation, clear labels, and plain language wherever the subject allows.
• RobustValid, semantic markup that works across browsers and assistive technologies.

The choices baked into the site.

These are deliberate, recurring decisions across every page, not one-off fixes:

• StructureSemantic landmarks and a logical heading order, so screen readers can navigate by region and outline.
• KeyboardEvery link, button, and interactive control is reachable and operable by keyboard, with a visible focus state.
• ContrastBody text and essential UI meet or exceed the AA contrast ratio against our dark and light surfaces.
• TextReal text rather than images of text, and layouts that reflow when you zoom to 200% or resize the window.
• Images & chartsDecorative imagery is hidden from assistive tech; meaningful figures carry text alternatives and the underlying numbers are stated in the content.
• FormsInputs have associated labels, and errors are described in text, not by color alone.

Movement you can switch off.

Some pages animate, charts draw on as they scroll into view, sections fade up, the hero carries quiet video. Motion can be a problem for people with vestibular conditions, so none of it is essential to understanding the content.

If your device or browser is set to "reduce motion," we honor it: scroll reveals, chart draw-on, and looping idle effects are disabled, and content appears in its final state immediately. You can set this in your operating system's accessibility settings, and the site will respect it automatically on your next visit.

What we test against.

We design to current web standards, which means the site should work with any standards-compliant assistive technology. We routinely check against:

• Screen readersVoiceOver on macOS and iOS, and NVDA on Windows.
• BrowsersThe current and previous major versions of Chrome, Safari, Firefox, and Edge.
• InputKeyboard-only navigation and OS-level zoom and text-scaling.

If you use a different combination and hit a wall, tell us, real-world reports are how we catch what testing misses.

Where we're not there yet.

We would rather name our gaps than pretend they don't exist. As of the date above, we're aware of these:

• Data chartsOur animated charts expose their figures as text, but do not yet ship a full tabular alternative for every series. The underlying numbers are always stated nearby.
• Embedded videoThe hero video is decorative and silent, so it carries no captions. No information is lost if it does not play.
• Third-party linksPages we link out to (social platforms, partners) set their own accessibility standards, which we do not control.

We're actively working these down. If something here is blocking you specifically, the section below gets it to a human fast.

Found something that blocks you? Tell us.

If any part of this site is hard or impossible to use with your setup, we want to know, and we treat it as a real bug, not feedback to file away.

Email accessibility@octusnetwork.com. To help us reproduce it quickly, include the page, what you were trying to do, and the browser plus assistive technology you were using. A screenshot or screen recording helps but is never required.

We aim to acknowledge every report within two business days and to fix confirmed barriers as fast as we reasonably can. If a fix will take time, we'll tell you the plan and offer another way to get what you needed in the meantime.

A human, not a form.