← Home

Accessibility Statement

Our commitment to making this site usable by everyone, what we have done, what we know is still imperfect, and how to tell us about a barrier you encounter.

1. Our commitment

Diagnostic Solutions Group is committed to making diagnosticsolutionsgroup.com usable by the widest possible audience, including people with disabilities. Our public-sector and clinical-system customers depend on our information being reachable through assistive technology, on slow connections, on older hardware, and across a range of devices. Accessibility is part of how we treat that audience.

2. Conformance target

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C Web Accessibility Initiative. We treat WCAG 2.2 AA as our standard because it is the version most commonly referenced by U.S. regulators, by procurement requirements such as Section 508, and by international authorities including the EN 301 549 standard used in the European Union.

3. What we have done

The following design and engineering choices were made specifically to support accessibility:

  • Semantic HTML. The site is built with standard semantic elements (header, nav, main, section, article, footer, headings in document order) so that screen readers and other assistive technology can present the structure correctly.
  • Alternative text. Informative images carry descriptive alt attributes. Decorative images are marked aria-hidden="true" or carry empty alt text so that assistive technology skips them.
  • Color contrast. Text and interactive elements are designed against the dark theme to meet or exceed the WCAG 2.2 AA contrast ratios (4.5:1 for normal text, 3:1 for large text and meaningful non-text contrast).
  • Keyboard navigability. All interactive controls (links, buttons, navigation) can be reached and operated with a keyboard. Focus order follows the visible document order.
  • Visible focus. Focus styles are preserved so keyboard users can see where they are on the page.
  • ARIA labels for icon-only controls. Where a control is represented by an icon or image rather than text (for example, the brand mark or social-style links), an accessible name is supplied via aria-label or visually hidden text.
  • Descriptive link text. Links are written so that their purpose is clear from the link text alone, without reliance on surrounding context. We avoid "click here" and "learn more" as standalone link text.
  • Reduced motion. Animated and transitional effects respect the user's prefers-reduced-motion setting and are reduced or removed when a visitor has indicated a preference for reduced motion in their operating system.
  • Responsive layout. The site adapts to a range of viewport sizes, supports text resizing, and remains usable when the browser is zoomed up to 200% without loss of content or functionality.
  • Language declared. The page language is declared on the html element so that screen readers use the correct pronunciation rules.
  • Form labels and contact pattern. The public site does not currently include data-collection forms. Contact uses a plain mailto: link with descriptive text. Any future forms will be built with explicit labels and accessible error messaging.

4. Known limitations

We know the site is not perfect. Areas we have identified for ongoing improvement include:

  • Decorative SVG and animated overlays. Some sections (the hero molecule field, certain section dividers, and animated overlays on product cards) use inline or external SVG. These are marked decorative and should be ignored by assistive technology, but the rendering of decorative SVG inside object elements can vary by screen reader. We continue to test and refine.
  • Third-party content. Web fonts are loaded from a third-party content delivery network (Google Fonts). On slow connections or when third-party hosts are blocked, system fallback fonts are used, which may shift layout slightly during page load. We use font-display: swap behavior to reduce invisible text.
  • Animated typography and reveal effects. Some headings and sections use entry animations. These respect prefers-reduced-motion, but if an environment does not signal that preference correctly, the animation will still play. The underlying content is delivered to assistive technology regardless of animation state.
  • Live data widgets. The current public site does not include live data widgets. If we add them in the future (for example, a procurement-status indicator or a live announcement), we will commit to providing equivalent text content and accessible status announcements.
  • PDF and document content. Where we link to PDF specifications, regulatory letters, or third-party documents, we cannot guarantee the source document was authored to AA accessibility standards. We work to provide an HTML equivalent or summary alongside any such link.
  • Legacy blog content and embeds. Insights posts are authored as static HTML by our team and reviewed for accessibility, but older posts may not meet our current standards as they evolve. We update posts when we identify a barrier.

5. Compatibility

The site is designed to be compatible with current versions of major browsers (Chromium-based browsers including Chrome and Edge, Mozilla Firefox, and Apple Safari) on desktop and mobile, and with assistive technologies that support modern web standards, including:

  • NVDA and JAWS on Windows
  • VoiceOver on macOS and iOS
  • TalkBack on Android
  • Orca on Linux
  • Browser zoom up to 200% and operating system text scaling
  • High-contrast and forced-colors modes (Windows High Contrast and equivalents)

We do not test against discontinued browsers (for example, Internet Explorer) and the site is not designed to support them.

6. Assessment approach

Our accessibility work combines manual review by our team (keyboard-only walkthroughs, screen-reader spot checks, contrast checks against the published palette) with automated tooling integrated into our build process. We do not currently engage an external auditor on a recurring basis, and we do not publish an Accessibility Conformance Report (ACR / VPAT) for this site. Government buyers who require an ACR for procurement may request one for products via the contact address below, and we will work to provide it.

7. Reporting an accessibility issue

If you encounter a page, control, or piece of content that is difficult or impossible to use with assistive technology, please tell us. We treat accessibility reports as priority issues.

Email Info@diagnosticsolutionsgroup.com with the subject line "Accessibility Issue." Please include:

  • The URL of the page where you encountered the issue;
  • A short description of what you were trying to do and what went wrong;
  • The assistive technology, browser, and operating system you were using, if you know;
  • Any screen shots, recordings, or other materials that help us reproduce the issue (optional).

We aim to acknowledge accessibility reports within five business days and to provide a substantive response, fix, or workaround as quickly as the complexity of the issue allows.

8. Alternative ways to reach us

If a barrier on the site prevents you from contacting us in writing, you can ask a friend, family member, advocate, or other agent to email on your behalf. We will work with whichever channel makes the conversation possible.

9. Changes to this statement

We will update this statement when our conformance status, known limitations, or testing approach changes. The "Last updated" date at the top of the page reflects the most recent change.