Ask us a question

Legal

Accessibility Statement

Last updated: June 2, 2026

Bluefish builds software that clinicians, HIM teams, payroll administrators, and IT staff use every day. Accessibility isn't an afterthought for us — it's how the people we sell to do their jobs. This statement applies to the Bluefish Systems marketing website at bluefishsystems.com.

1. Our commitment

Bluefish is committed to making this website usable by the widest possible audience, including people with disabilities. We aim to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our internal standard. We treat accessibility as an ongoing practice, not a one-time audit — every new page is built and reviewed against the same bar.

2. Conformance status

The WCAG defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

This website is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully conform; the known gaps and our plan for them are listed in Section 6 below.

3. Measures we take

Accessibility is built into how we design, write, and ship the site:

  • Semantic HTML and structure. Pages use a logical heading order (one H1 per page, nested H2/H3 sections), landmark elements (header, nav, main, footer), and lists where lists belong.
  • Keyboard access. All interactive controls — links, buttons, forms, video controls — are reachable and operable with a keyboard, with a visible focus indicator that meets contrast requirements.
  • Skip-to-content. A "Skip to main content" link is available so keyboard and screen-reader users don't have to traverse the header on every page.
  • Color and contrast. Body text and meaningful UI meet the WCAG AA contrast threshold (4.5:1 for normal text, 3:1 for large text and meaningful non-text components). Our design tokens enforce a small, contrast-checked palette.
  • Reduced motion. The site honors the prefers-reduced-motion setting from your operating system. When it's on, we dial back or remove non-essential animation.
  • Text alternatives. Informative images carry descriptive alt text. Decorative graphics are marked as decorative so assistive technology can skip them. Product mocks have a summary aria-label describing what's shown.
  • Forms. Form fields have visible labels (not placeholders posing as labels), inline error messages, and predictable submission behavior. We avoid unannounced changes of context.
  • Video. Embedded product tour videos are short, are accompanied by visible context describing what they show, and include native browser controls. Captioning for the embedded tour videos is a known limitation we are actively working on — see Section 6.
  • Responsive layout. The site reflows down to a 320 px viewport without loss of content or functionality and supports OS-level text zoom up to 200% without horizontal scrolling on the primary content column.
  • Plain language. We avoid unnecessary jargon and define product names where they first appear.

4. Technical specifications

Accessibility on this site relies on the following technologies working in combination with your browser and any assistive technology you use:

  • HTML5
  • CSS (with design tokens, no hard-coded color values in components)
  • A small amount of JavaScript (progressive — the site reads and submits forms with JavaScript off, with limited interactive enhancements when it's on)
  • WAI-ARIA where ARIA is appropriate
  • MP4 / H.264 for embedded video

5. Compatibility with browsers and assistive technology

The site is designed and tested for compatibility with current versions of the major browsers (Chrome, Edge, Firefox, and Safari) on Windows, macOS, iOS, and Android. It is built to be usable with mainstream assistive technology, including screen readers (NVDA, JAWS, VoiceOver on macOS and iOS, and TalkBack on Android), OS-level zoom and high-contrast modes, and voice-control software.

Combinations we cannot reasonably test against may behave unpredictably; if that's the case for your setup, please tell us — see Section 8.

6. Known limitations and our plan

We are tracking and working on the following known gaps. We list them here so you know what to expect and how to get around them in the meantime.

  • Captions and transcripts for embedded product tour videos. The HealthPoint and Employee Portal tour videos do not yet ship with captions or a posted transcript. Mitigation: the surrounding page copy describes everything the video shows in writing, so no information is conveyed by video alone. If you need a transcript before we publish one, email sales@bluefishsystems.com and we will send one within two business days.
  • Some product mocks and posters are images. Where a screenshot or mock conveys meaningful information, we provide an aria-label or alt summary; if a summary is insufficient for your needs, ask us for the same information in another format (see Section 8).
  • External product microsites. Some Bluefish products live on their own websites (Capsa, Shield Tracker, SprocOptimizer). Those sites have their own accessibility postures and are not covered by this statement; if you encounter a barrier on one of them, you can still reach us through the contact below and we will route it.

7. Assessment approach

We assess accessibility through a combination of:

  • Manual code review against WCAG 2.1 AA on every new page before it ships;
  • Keyboard-only walkthroughs of the homepage, the HealthPoint sub-page, the Employee Portal sub-page, the About page, and the Contact / Demo flows on both desktop (1440 × 900) and mobile (375 × 812) viewports;
  • Automated accessibility checks using browser developer tools (Lighthouse, axe DevTools) as a quick screen — never as a substitute for manual review;
  • Console-clean verification (no thrown errors or accessibility warnings in the browser console at load and through the primary user flows).

This statement is self-prepared by the Bluefish team. We have not (yet) commissioned a formal third-party accessibility audit; if you require evidence of one as part of a procurement process, please contact us to discuss.

8. Feedback and contact

If you encounter an accessibility barrier on this website, or you need information on this site presented in a different format (large print, accessible PDF, plain text, audio, etc.), please tell us:

Email sales@bluefishsystems.com with the subject line "Accessibility feedback." Please include:

  • The page URL where you ran into the problem;
  • A short description of the barrier — what you were trying to do and what happened;
  • Your browser, operating system, and any assistive technology you were using (if you're comfortable sharing that);
  • How you'd like us to follow up with you.

What to expect from us. We aim to acknowledge accessibility feedback within two business days and to either fix the issue or provide the information you need in an alternative format while we work on a fix. For complex issues we will give you a realistic timeline.

9. Formal complaints

If you are not satisfied with our response, you may contact us again at the address above asking for escalation, and we will route your message to a senior team member who will respond directly.

10. Date of this statement

This statement was prepared on the date shown at the top of this page. It is reviewed each time we materially change the site.