Skip to content
Last reviewed 30 April 2026

Accessibility.

This statement describes the accommodations we have built into aurumquanta.com, the limitations we know about, and how to report any issues you encounter.

01

Our commitment

We aim to make aurumquanta.com usable by people with the widest reasonable range of abilities, including those who use screen readers, keyboard-only navigation, or reduced-motion settings. Accessibility is treated as part of ongoing engineering work, not a one-off compliance exercise.

This Site has not been formally audited or certified for conformance with the Web Content Accessibility Guidelines (WCAG). The list of accommodations in Section 3 reflects what is currently implemented in the codebase. If you encounter a barrier we have not anticipated, please report it (Section 5) and we will address it.

02

Standard we work towards

Our target is conformance with Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). This is the standard most commonly referenced by Australian Government procurement and by the Australian Human Rights Commission's World Wide Web Access advisory notes under the Disability Discrimination Act 1992 (Cth).

03

What we have implemented

The following accommodations are built into the Site today:

  • Reduced-motion support. Visitors who set the operating-system preference prefers-reduced-motion: reduce see a static version of the homepage background animation, and the animated dot on the engagement-process diagram is hidden.
  • Decorative elements hidden from assistive technologies. The animated background on the homepage and the directional dots on the process diagram are marked aria-hidden=“true” so they are not announced by screen readers.
  • Form status announcements. The contact form uses ARIA live regions so screen-reader users hear status changes during submission, success, and error states. Inputs have associated <label> elements.
  • Keyboard-accessible navigation. The site navigation, services dropdown, and mobile menu can all be operated with keyboard alone (Tab, Enter, Escape). The mobile menu uses role=“dialog” and aria-expanded to communicate state.
  • Skip-to-content link. On every page, the first focusable element is a “Skip to content” link, hidden by default and revealed on keyboard focus. Activating it bypasses the navigation and jumps focus directly to the page content, satisfying WCAG 2.4.1 (Bypass Blocks).
  • Semantic HTML. Page structure uses semantic landmark elements (<header>, <nav>, <main>, <article>, <footer>) with a single <h1> per page and a logical heading hierarchy.
  • Document language. The root <html> element declares lang=“en”.
  • Text-only content, no images of text. The Site does not use images of text for headings or paragraph copy, so users who increase browser text size or use screen-reader text-to-speech see and hear the same content as other visitors.
04

Known limitations

We are honest about what has not yet been done. Specifically:

  • No formal WCAG conformance audit. We have not yet engaged a third-party accessibility auditor or run a comprehensive automated audit (axe-core, Lighthouse, WAVE). Specific WCAG criteria may not be met.
  • Colour contrast not formally verified. The Site uses a dark background with cream and gold text. We believe most text combinations meet WCAG AA contrast ratios, but this has not been verified across every component. Syntax-highlighted code blocks use a third-party theme (github-dark-dimmed); some token colours may have lower contrast than ideal.
  • Limited screen-reader testing. We have implemented standard ARIA attributes but have not yet completed a full pass with VoiceOver, JAWS, or NVDA. If you encounter announcement issues, please report them.
  • Mobile dropdown menus rely on hover and focus. The services dropdown in the desktop navigation is opened by hover or keyboard focus. On touch devices, tapping the services link navigates directly to the services page rather than opening the dropdown; the same destinations are accessible via the mobile hamburger menu.
05

Reporting an issue

If you encounter an accessibility barrier on this Site, or if something is harder to use than it should be, please email contact@aurumquanta.com with the subject line “Accessibility”. We will:

  • Acknowledge your report within 5 business days.
  • Provide a substantive response, including either a fix or a planned remediation timeline, within 30 days.
  • Confirm the fix when it is deployed.

Where helpful, please describe: which page you were on, what you were trying to do, what assistive technology you were using (if any), and what happened.

06

Updates and review

This statement is reviewed and updated when material changes are made to the Site, and at minimum once every 12 months. The most recent review date is shown at the top of this page. When we add accommodations or fix limitations listed above, we will update Sections 3 and 4 to reflect the current state.

For all accessibility enquiries, contact contact@aurumquanta.com.