Accessibility

We want everyone to be able to access this site and reach us through it, whatever device or assistive technology they use. This page explains what we’ve built in, where we know we fall short, and how to tell us when something doesn’t work for you.

Last updated: September 19, 2026

On this page: Our target · What’s built in · Where we stand · Known limitations · Browsers and assistive technology · Tell us about a barrier · How we keep this current

Our target

Sopra Health Comms, LLC builds soprahealth.com to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the international standard for making web content usable by people with visual, hearing, motor, and cognitive disabilities, and Level AA is the level most organizations and regulators treat as the practical benchmark.

We treat accessibility as part of good design, not a compliance layer added at the end. The choices below were made when the site was designed and are checked again when pages change.

What’s built in

These are the specific things the site does, not general intentions.

Structure and navigation

  • Every page uses standard landmarks (header, navigation, main content, footer) so screen reader users can jump between regions.
  • Each page has one main heading that names the page, and the browser tab title is unique to that page.
  • The page language is declared as English so screen readers use the right pronunciation rules.
  • The top navigation is the same on every page, and a way to contact us appears in the same place in the header and footer throughout the site.

Keyboard and focus

  • Everything you can do with a mouse you can do with a keyboard: links, buttons, expandable sections, and form fields are all reachable with Tab and operable with Enter or Space.
  • On small screens the menu is behind a button that announces whether the menu is open or closed to assistive technology.
  • Expandable sections use the browser’s built-in disclosure element rather than custom scripting, so they work with keyboards and screen readers by default.

 

Color and contrast

  • The site’s color palette was checked against WCAG AA contrast requirements when it was designed. Body text sits on the page background at roughly 14.8:1, well above the 4.5:1 minimum. The smallest text on the site, used for captions and notes, is about 5.3:1 or better.
  • Every text-and-background pairing in the palette, including the accent colors used to mark our three service areas, meets or exceeds 4.5:1. The lowest pairing on the site is about 4.8:1.
  • Color is never the only way information is shown. Links are distinguishable from surrounding text, required form fields are marked with a symbol as well as color, and section themes are named in words, not just tinted.

 

Text and layout

  • Body text is set at 17 pixels with generous line spacing, and reading measures are capped so lines don’t run too long on wide screens.
  • Text is real text, not images of text, so it can be resized, reflowed, and read aloud.
  • The layout adapts to screen size and to browser zoom. Content reflows into a single column on narrow screens rather than requiring sideways scrolling.
  • The two typefaces we use have standard system fallbacks, so the site remains readable if web fonts fail to load.

 

Motion

  • Nothing material on the site plays, moves, or animates automatically.
  • If your device is set to reduce motion, the site turns off its own animations and smooth scrolling and moves between sections instantly.

 

Images

  • Every image has a written description (alt text) that says what the image shows. Images on this site are illustrative; none of them carry information that isn’t also in the text.
  • Images have their dimensions set in the page so content doesn’t jump around while they load.

 

Forms and tables

  • Every field on the contact form has a label that’s connected to the field, so screen readers announce it and clicking the label focuses the field.
  • Required fields are marked, and instructions appear before the field they apply to, not after.
  • Fields support browser autofill for names, email, phone, and organization, so you don’t have to retype details your browser already knows.
  • The essay index is a table with essay headers and clear buttons so screen readers can read each cell with its heading.

Where we stand

We believe the site meets WCAG 2.2 Level AA. That assessment is our own, based on how the site was designed and built and on checks with keyboard navigation and browser accessibility tools. We haven’t commissioned an independent third-party audit. If we do, we’ll say so here.

Because the site has no accounts, no logins, and no drag-and-drop interactions, several WCAG 2.2 criteria that address those features don’t arise. The ones that do apply, such as not asking you to re-enter information you’ve already given, are met.

Known limitations

We’d rather tell you what we know than claim perfection. As of the date above:

  • Heading levels on a few pages. Some pages, including this site’s Corporate, News, and Who We Help pages, move from the main heading directly to third-level headings without a second level. Screen reader users navigating by heading may notice the gap. 
  • Third-party services. Our forms are supported by Brevo (SendInBlue), our email newsletter is available on Substack, and we maintain a LinkedIn page. Their subscription forms, emails, and pages are built and hosted by those companies, and we can’t change how accessible they are. If you have trouble subscribing using our forms or subscribing, email us and we’ll add you directly.
  • AI-generated imagery. Some photographic-style images on the site are AI-edited rather than original photographs. Their descriptions say what the picture depicts; they don’t depict real people or events.
  • Testing coverage. We test with keyboard navigation and current browser tools, but we haven’t tested every combination of browser and screen reader. If something behaves differently for you, that’s exactly the report we want so that we can fix it.

Browsers and assistive technology

The site is built with standard HTML, CSS, and a small amount of JavaScript, and follows the WAI-ARIA authoring practices where native HTML isn’t enough. It’s designed to work with current versions of Chrome, Firefox, Safari, and Edge, and with screen readers such as NVDA, JAWS, VoiceOver, and TalkBack. The site remains readable and navigable with JavaScript turned off.

Tell us about a barrier

If any part of this site is hard to use, or you can’t get to something you need, email us at info @ soprahealth.com with “Accessibility” in the subject line. It helps to include:

  • The address of the page where you had the problem.
  • What you were trying to do and what happened instead.
  • The browser, device, and any assistive technology you were using.

We’ll reply as soon as possible. If the problem is something we can fix, we’ll tell you when it’s done. If it will take longer, we’ll give you the information or help you were looking for another way in the meantime. You can also call us at 941-424-3900.

Please don’t include patient-identifiable information or confidential material in your message.

How we keep this current

We review this statement whenever the site changes significantly, and at least once a year. When we change an item, we update it here. The date at the top reflects the last review.