adAccessibility
Usable by everyone on your team
Compliance work is done by people with different tools, different abilities, and not much patience for software that gets in the way. We want Adhera, and this site, to work for all of them.
The standard we work to
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, for this website and for the Adhera product. "Aim for" is the honest phrase: Adhera is pre-release, we have not had an independent audit yet, and this page lists what we know is not there. We will update it as the product changes.
What is in place on this site
- Keyboard. Everything on the site can be reached and operated with a keyboard, including the interactive examples on the home page. A skip link at the top of each page jumps past the navigation. Focus is always visible.
- Screen readers. Pages use real headings, landmarks and labels. The interactive examples announce what changed after each step, so they can be followed without seeing them. Decorative images are hidden from assistive technology.
- Colour and contrast. Body text and links meet the AA contrast ratio against their background in both the light and dark themes; the orange accent is used only at large sizes. Colour is never the only way something is shown; status is also given in words.
- Motion. Animations are short and stop when your system asks for reduced motion.
- Size and zoom. Layouts reflow to a single column at high zoom and on narrow screens. Buttons and other targets are at least 44 pixels tall. Text is real text, so your own font size settings apply.
- Forms. Every field has a visible label. Errors are described in words next to the field, and the first one receives focus.
What we know falls short
- The interactive examples on the home page are illustrations with several steps. They are keyboard-operable and announce their state, but following them with a screen reader takes more effort than reading a paragraph would. The same information is available in plain text on the partner terms and in the product's own guide.
- The Adhera product has not yet been tested end to end with a screen reader by someone who uses one daily. Tables and dialogs are built with accessible components, but we expect to find rough edges, and we would like to hear about them.
- Evidence files uploaded by customers, and documents produced for auditors, are only as accessible as their source. We do not alter customer files.
Tell us what doesn't work
If something on this site or in the product is hard or impossible for you to use, write to hello@adheraworks.com and say what you were trying to do, what happened, and what you were using (browser, screen reader, or other assistive technology). We read every message, we reply within two business days, and we treat a barrier as a defect to fix, not a request to consider.
If you are a design partner and something is in your way, raise it on the founder call and it goes to the front of the queue.