Draft for legal review. This page is a working draft prepared for the Calyraen legal team to review and approve before launch. Wording, standards references, and contact details may change in the final version.
Calyraen designs and builds hardware, writes the software that runs on it, and operates a range of services online. We want as many people as possible to be able to use what we make, including people who rely on assistive technology or who browse in ways that suit their needs. This page explains what we are working toward, the steps we have taken, where we still fall short, and how to reach us if something gets in your way.
Last updated: July 6, 2026
Our commitment
Accessibility is part of how we think about design, not an afterthought bolted on at the end. We aim to make our website usable for people with a wide range of abilities, including those who use screen readers, keyboard navigation, screen magnification, voice control, or other assistive tools, and those who benefit from reduced motion, larger text, or higher contrast.
This is ongoing work. Accessibility is not a box we tick once. As we add pages, features, and products, we try to hold new work to the same standard as the rest of the site, and we go back to fix things we get wrong.
The standard we work toward
We use the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA as our target. These guidelines are a widely recognized reference for making web content more accessible, and level AA is a common benchmark for organizations that take accessibility seriously.
We want to be honest about what this means. WCAG 2.1 AA is the aim we design and test against. It is not a certified guarantee that every page and every element meets every success criterion at all times. Some areas of the site will meet the target better than others, and we describe known gaps below. We treat conformance as a direction of travel rather than a finished claim.
Measures we have taken
We have built and continue to refine a number of features intended to make the site more accessible:
- Keyboard navigation. You can move through interactive elements such as links, buttons, menus, and form fields using the keyboard, without needing a mouse or trackpad.
- Color contrast. We aim for text and important interface elements to have enough contrast against their background to remain readable.
- A dark theme. The site offers a dark appearance in addition to a lighter one, which can be easier on the eyes and helpful for people sensitive to bright screens.
- Semantic structure. We use meaningful headings, landmarks, and page structure so that assistive technology can present content in a logical order and let people jump between sections.
- Text alternatives. We aim to provide text descriptions for images and other non-text content that carry meaning, so the information is available to people who cannot see the image.
- Respecting reduced-motion preferences. If your device or browser is set to reduce motion, we aim to honor that setting and limit or remove non-essential animation.
We also try to write in plain language, keep layouts predictable, and make forms and error messages clear.
Known limitations
We do not want to over-claim. Parts of the site do not yet fully meet our target, and some content is harder to get right than others. Known and likely limitations include:
- Older pages, or pages that have not been reviewed recently, may not meet the same standard as newer work.
- Some complex or interactive components may not yet behave perfectly with every assistive technology or browser combination.
- Content supplied by third parties, or embedded from external services, may not meet the same standard and may be outside our direct control.
- Documents, media, and downloadable files may vary in how accessible they are.
If you run into a problem that is not listed here, we would still like to hear about it. Your reports help us find issues we have missed and decide what to fix first.
Requesting content in an alternative format
If you need information from this site in a different format, for example a plain-text version, a larger-print version, or content read out or described to you, please ask. We will do our best to provide the information in a way that works for you, or to help you get what you need another way.
To make a request, please contact us and tell us what you need and, if you can, which page or content it relates to.
Reporting a barrier
If any part of this website is difficult or impossible for you to use, please let us know. Helpful details include:
- the page or feature where you ran into the problem (a link or description is fine),
- what you were trying to do,
- what happened, or what stopped you, and
- the device, browser, or assistive technology you were using, if you are comfortable sharing that.
You do not need to include all of this to reach out. Even a short note helps. Please report barriers through our contact page.
We aim to acknowledge accessibility reports and respond within a reasonable time. If a fix will take a while, we will try to let you know and, where we can, suggest a way to get the information or complete the task in the meantime.
How we review accessibility
We review accessibility regularly rather than only when something is reported. This includes checking new and updated pages as part of our normal work, testing with keyboard and assistive technology where practical, and revisiting known issues over time. Feedback from people who use the site is an important part of this process, and reports from readers directly shape what we work on next.
As standards, tools, and our own products evolve, we expect this page and our practices to change with them. We will update the "Last updated" date above when we make meaningful changes.
Contact
For any accessibility request, question, or report, please contact us.