Accessibility Statement

Last updated: January 2026

Our commitment

Medical ANS is committed to making medicalans.com usable for the widest possible audience, including people who rely on assistive technology. Accessibility is not a checkbox for us — it reflects the same standard of care we bring to the healthcare environments we serve.

We design and build to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Where we fall short, we treat it as a defect to be fixed, not a feature to be debated.

Conformance status

This website is designed to be partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully meet the accessibility standard — see Known limitations below for specifics.

Our conformance target is full WCAG 2.1 Level AA across all pages owned and authored by Medical ANS.

Measures we take

To make this site accessible, we apply the following practices across design, content, and build:

  • Semantic structure. Pages use proper HTML landmarks, headings, and lists so that assistive technology can navigate them by region and hierarchy.
  • Keyboard navigation. All interactive elements — links, buttons, the main navigation menu, and the contact form — are reachable and operable using a keyboard alone. A "Skip to content" link is provided on every page.
  • Visible focus. Keyboard focus is always visible, with a focus indicator that meets contrast requirements.
  • Color and contrast. Text and meaningful interface elements are designed to meet or exceed WCAG AA contrast ratios. Color is never used as the only way to convey information.
  • Text and zoom. Content uses relative units and reflows cleanly when text is enlarged up to 200% or when the page is viewed on narrow screens.
  • Images. Meaningful images include descriptive alternative text. Decorative images are marked so that assistive technology can skip them.
  • Forms. Form inputs are paired with visible labels, use appropriate input types, and surface errors in text — not by color alone.
  • Plain language. We write in plain, direct language and avoid unexplained jargon. Where industry terms are necessary, we define them in context.
  • Motion and timing. The site does not auto-play media, does not rely on time limits, and avoids animation that could trigger vestibular or seizure conditions.

Compatibility

medicalans.com is designed to work with the current and previous major versions of Chrome, Safari, Firefox, and Edge on desktop and mobile. It is tested with screen readers including NVDA and JAWS on Windows and VoiceOver on macOS and iOS.

The site does not depend on JavaScript to deliver its content; core information and navigation remain usable if scripts are disabled.

Assessment approach

We evaluate accessibility through a combination of methods: automated checks during the build process, manual keyboard and screen-reader testing on representative pages, and periodic third-party review. We re-test when we ship significant changes to design or navigation.

Known limitations

We are aware of the following areas where the site does not yet fully meet our standard. We are working through them on a published schedule:

  • Third-party content. Embedded video, downloadable PDFs, and content sourced from partner organizations may not yet meet WCAG 2.1 AA. We are progressively replacing or remediating these assets.
  • Older case study and resource documents. Some older PDF resources predate our current accessibility standard and are being reformatted.
  • Complex data visuals. Where charts or diagrams appear, we are adding longer text descriptions alongside them.

Feedback

If you encounter an accessibility barrier on medicalans.com — or if a page works for you but you can see how it could work better — please write to [email protected]. Useful detail includes the page URL, the assistive technology or browser you were using, and a description of what you were trying to do.

We aim to acknowledge accessibility reports within two business days and respond substantively within five. We treat accessibility reports the same way we treat security reports: as defects that need fixing, not complaints to be managed.

Formal complaints

If you are not satisfied with our response to an accessibility concern, you may escalate to [email protected]. We will work in good faith to resolve the issue.