Accessibility Statement

01Our commitment

Averro Technologies is committed to making averrotech.com usable by as many people as possible, including people who use screen readers, magnification, keyboard-only navigation, voice control, or who have reduced tolerance for motion.

We aim to meet WCAG 2.2 Level AA. We treat that as the target, not the ceiling, and we treat a reported barrier as a defect rather than a request.

02What has been built and measured

The following are not aspirations. Each was checked on the shipped site.

Colour and contrast

• Every foreground and background pair in the design system is verified against the WCAG AA thresholds by a script that reads the real values out of the stylesheet, so a palette change cannot quietly break contrast.
• Body copy renders at a contrast ratio of at least 4.5:1 and headings well above it; the lowest-contrast pair on the site currently measures 4.75:1.
• Colour is never the only means of conveying information. Where the site uses indigo or cyan to mark a state, that state also carries a label, a shape or a position.

Keyboard and focus

• All interactive elements are reachable and operable by keyboard.
• A visible focus indicator is applied site-wide with a 2px outline and a 3px offset, and is not suppressed anywhere.
• The mobile navigation can be closed with the Escape key as well as by tapping the toggle.
• Expandable content uses native <details> elements, so it works without JavaScript and announces its state correctly.

Structure and semantics

• Pages use one <h1> and a logical heading order below it.
• Landmarks — header, navigation, main content regions, footer — are marked up with the correct elements.
• Data that is genuinely tabular is presented in a real <table> with row and column headers, not a grid of styled boxes.
• Decorative illustrations are hidden from assistive technology; illustrations that carry meaning have a text alternative describing what they show.
• Links that leave the site are marked as such, visibly and in the accessible name.

Motion

• The site honours prefers-reduced-motion. Under that setting scroll reveals resolve immediately, page transitions are disabled, the animated backdrop paints a single static frame and never animates, and smooth scrolling is not started at all.
• The preference is honoured live, not only at page load, so changing it mid-session takes effect.
• Nothing on the site flashes, and no animation loops more than three times except the partner marquee, which pauses on hover and is hidden from assistive technology.

Touch and responsive layout

• Interactive targets are at least 44×44 CSS pixels on touch devices.
• The site is tested at 320, 360, 390, 430 and 768 pixels wide and reports zero horizontal document overflow at every one of them.
• Text reflows without loss of content or function; nothing depends on a fixed viewport width.
• Wide content such as the services comparison table scrolls inside its own container rather than pushing the page sideways.

03Known limitations

These are the things we know are not right, or not yet proven. We would rather publish them than let you discover them.

1. No audit by an external assessor. Testing so far has been automated plus manual keyboard checks by the team that built the site. That is not the same as an independent WCAG audit and we do not claim it is.
2. Not tested with every assistive technology. We have not yet completed structured testing with JAWS, NVDA, VoiceOver and Dragon across browsers. Until we have, any claim about screen-reader behaviour is a reasonable expectation rather than a verified result.
3. The comparison table needs horizontal scrolling on a small screen. The relationship it shows is two-dimensional and we judged a real table to be more accessible than flattening it into cards, but the trade-off is a scroll on narrow viewports.
4. The animated backdrop on the home page. It respects reduced-motion and it is decorative and hidden from assistive technology, but it has not been evaluated by anyone with vestibular sensitivity in a live session.
5. No skip-to-content link. The header is short and the navigation is a single list, so the cost of tabbing past it is low, but a skip link is standard and its absence is a gap.
6. Documents. Any PDF or Office document we publish in future may not meet the same standard as these pages. Ask us and we will provide the content in an accessible format.

04Tell us about a barrier

If any part of this site does not work for you, we want to hear about it — including if you are not sure whether it is us or your setup.

Email contactus@averrotech.com with “Accessibility” in the subject line. It helps if you can tell us the page, what you were trying to do, and what you use to browse — but send it even if you cannot.

What happens then

1. We acknowledge your message within two business days.
2. We reproduce the barrier and tell you what we found.
3. We fix it, or tell you plainly when we will and why it is taking that long.
4. If you needed information that was not reachable, we send it to you in a format that works while the fix is being made. You should not have to wait for a deploy to get an answer.

There is no charge, no form and no ticket queue. It goes to the same inbox as everything else and a person reads it.

05Standards and legal context

This statement is prepared with reference to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the World Wide Web Consortium.

In Australia, the Disability Discrimination Act 1992 (Cth) makes it unlawful to discriminate against a person on the basis of disability in the provision of goods, services and facilities, and the Australian Human Rights Commission has issued World Wide Web Access guidance recommending WCAG conformance as the means of meeting that obligation.

If you believe you have been discriminated against, you may complain to the Australian Human Rights Commission at humanrights.gov.au. You do not need to raise it with us first, though we would like the chance to fix it.

06How we assess and review

Accessibility is checked as part of the build rather than audited afterwards:

• a contrast script parses the live stylesheet and asserts every rendered colour pair clears AA;
• an automated mobile audit drives a real browser at five viewport widths and reports horizontal overflow, undersized touch targets and console errors;
• keyboard navigation and focus visibility are checked manually on each page that changes.

This statement is reviewed at least annually, and whenever the site changes materially. The date at the top of this page records the last review.