Accessibility Statement

Last reviewed: 2026-07-22

Coro is committed to making our website usable by as many people as possible, including people with disabilities. Accessibility is part of how we think about quality, and we treat it as ongoing work rather than a one-time project. This statement explains the standard we work toward, where we stand today, how we test, what we know still needs improvement, and how to reach us if something is not working for you.

Our commitment

We want everyone who visits coro.net to be able to find information, understand it, and interact with our site. Accessibility is an ongoing effort for us, not a one-time project. We treat it as part of how we build and maintain the site, and we improve it over time as we identify and fix issues.

Measures to support accessibility

To support this commitment, Coro takes the following measures: we incorporate accessibility considerations into our website design and development processes, designate internal responsibility for accessibility matters, and plan to provide relevant accessibility training to applicable employees as our accessibility program matures. We are committed to continuously enhancing these measures and expanding our accessibility efforts over time.

The standard we are working toward

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These guidelines, published by the World Wide Web Consortium (W3C), explain how to make web content easier to use for people with a wide range of disabilities, including visual, hearing, motor, and cognitive differences.

WCAG 2.2 Level AA is our target. It is the goal we design, build, and remediate against, not a claim that every page currently meets it.

Accessibility practices and features

As part of our efforts toward WCAG 2.2 Level AA conformance, the website relies on HTML, WAI-ARIA, CSS, and JavaScript to support accessibility. These technologies are required for the site to function correctly with browsers, assistive technologies, and plugins.

We aim to support the latest versions of major browsers, such as Chrome, Firefox, Safari, and Edge, together with widely used assistive technologies such as JAWS, NVDA, and VoiceOver, and we work to maintain broad compatibility. Users are encouraged to keep their browsers and assistive technologies up to date for the best experience.

The site is designed to support the following accessibility features. These reflect our ongoing accessibility efforts and do not represent a guarantee that every page or feature currently meets these objectives in full:

• Keyboard accessibility. The site is designed so that functionality can be operated using a keyboard alone.
• Alternative text for non-text content. The site provides text alternatives for non-text content where applicable.
• Text resizing. The site supports text resizing up to 200% without loss of content or functionality.
• Avoidance of flashing content. The site is designed to avoid content that flashes in ways that could pose a risk to users with photosensitive conditions.

Current status

Based on limited automated testing to date, parts of coro.net do not yet conform to WCAG 2.2 Level AA. We have not yet completed the manual and assistive-technology testing needed to assess full Level AA conformance, so what follows is a preliminary self-assessment rather than a finished evaluation. We describe the specific gaps we are aware of in the “Known limitations” section below, and we are working through them on a remediation schedule.

We are honest about this because we would rather tell you clearly where the gaps are than overstate what we have achieved. We do not claim that the site is fully accessible or fully compliant with any accessibility standard or law.

We do not use an accessibility overlay or widget (a third-party script that claims to automatically make a site accessible). We have chosen to invest in the underlying accessibility of the site itself, because we believe that produces a more reliable experience for people who use assistive technology.

How we test

We currently evaluate key pages of the site using automated accessibility scanning (the axe-core testing engine). Automated tools are useful and catch many common problems quickly, but they have known limits. Many important checks, such as whether a page makes sense when navigated by keyboard or read aloud by a screen reader, can only be found through manual review and testing with assistive technologies.

Because of this, our current testing gives us only partial coverage. We are planning broader manual review and testing with assistive technologies to close that gap and to guide our fixes, and we will update this statement as that work progresses.

Known limitations

Despite our efforts, some parts of this website are not yet fully accessible. Based on our own current review, we are aware of the following issues, and we are working to correct them:

• Icon and image links in the header and footer. Some of these links may not yet have descriptive names, which can make them harder to understand with a screen reader.
• Embedded third-party forms. Some fields and buttons in forms provided by external services may not have complete labels, which can make them harder to use with a screen reader. We are working to correct these.
• A decorative animation. One decorative animation on the site exposes some non-standard accessibility markup.
• Color contrast. At least one component includes text whose color contrast against its background is lower than the standard recommends, which can make it harder to read.

We are remediating these items on a schedule and will update this statement as they are resolved. This list reflects what we currently know and may not be complete. If you run into a barrier that is not listed here, please tell us using the contact details below.

Feedback and alternative access requests

We welcome your feedback on the accessibility of our website. If you have trouble using any part of the site, notice a problem we have not listed, have a suggestion, or need an alternative way to access information or functionality, please email us: [email protected].

When you contact us, it helps if you can include:

• The web address (URL) of the page.
• A short description of the problem.
• The device, browser, or assistive technology you were using, if you know it.

You do not need to include any of this to reach out. Any detail you can share helps us reproduce and fix the issue faster, but a simple note is welcome too. We aim to acknowledge accessibility messages within 5 business days, and we will work with you to resolve the issue and to remediate the underlying problem on the site. This response window is a goal we work toward, not a guarantee, and more complex issues may take longer to resolve.

If any content or function on the site is not accessible to you, we will work with you to provide the information or help you complete the task through an alternative method, such as by email or another format that works better for you. You do not need to explain why you need an alternative.

Updates to this statement

Accessibility is ongoing work, and this statement reflects a point in time. We treat it as a living document, and we will review and update it as we complete remediation, broaden our testing, and as the site changes.