Accessibility

Accessibility Statement

What we have done to make this site usable, what we have not verified, and how to tell us about a problem.

Effective date: to be set at publication

Oceanic Pacific Management, LLC wants this website to be usable by as many people as possible, including people who use assistive technology, navigate by keyboard, need larger text, or prefer reduced motion. We treat accessibility as part of whether the site works, not as an optional refinement.

What we have done

The following measures are built into this site:

  • Semantic HTML with proper landmark structure, so headers, navigation, main content, and footers are identifiable to assistive technology.
  • A single main heading per page and a logical heading order, so the structure of a page can be understood and navigated by heading.
  • A skip-to-content link as the first focusable element on every page.
  • Full keyboard operability, including the mobile menu, which can be opened, navigated, and closed without a mouse and returns focus sensibly. It also closes with the Escape key.
  • Visible focus indicators on every interactive element, with sufficient contrast against their backgrounds.
  • Text and background colors chosen to meet recognized contrast expectations for body text and interface elements.
  • No meaning conveyed by color alone. Status labels and the current navigation item are indicated by text, shape, or weight as well.
  • Descriptive alternative text for meaningful images, and empty alternative text for images that only repeat adjacent text.
  • Form controls with properly associated labels, clearly marked required fields, and hint text linked to its field.
  • Layout and text that reflow for small screens and remain usable when text is enlarged, with touch targets of a reasonable size.
  • Support for the reduced-motion preference. Where motion is used, it is subtle and is disabled when a visitor's system asks for less.
  • Content that does not depend on JavaScript in order to be read, and navigation that remains usable if scripting is unavailable.

Known limitations

We do not claim that this site is perfectly accessible, and we would not trust a site that did. Testing so far has been carried out by us using keyboard navigation, browser zoom, contrast checking, and automated tooling. It has not included a formal independent audit or systematic testing across the full range of assistive technologies and older devices.

Because of that, there are likely to be issues we have not found, particularly in combinations we have not tested. We are also aware that some accessibility qualities, such as clarity of language, are matters of judgment that benefit from outside feedback.

Standards we work toward

We use the Web Content Accessibility Guidelines as our reference point and aim to meet its Level AA success criteria. To be precise about what that means: it describes the standard we design and build against, and it is not a claim of certification, formal conformance, or completeness. No third party has assessed or certified this site.

Telling us about a problem

Accessibility feedback is genuinely useful to us, and reports of real barriers are the fastest way for problems to get fixed. A public contact address has not been published yet. Verified contact details will appear on the contact page as soon as they are available, and the accessibility feedback category there exists for exactly this purpose.

When the channel is open, the most helpful reports describe the page involved, what you were trying to do, what happened instead, and the browser and assistive technology you were using. We will acknowledge reports, explain what we can and cannot fix, and say when a fix is unlikely rather than leaving a report unanswered.

Questions about this policy?

The contact page explains how to reach OPM, including for corrections to anything on this site.

Go to the contact page