Accessibility

Our commitment

EventLinqs is built so that buying a ticket, organising an event, and navigating the platform are usable by everyone, including people with disability and people using assistive technology. Accessibility is a first-class engineering requirement, not an afterthought.

We treat accessibility defects as we treat any production defect: triaged, ticketed, and fixed. We do not ship features that introduce new barriers without a documented mitigation plan.

Conformance target

EventLinqs targets conformance to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across every public surface, including the homepage, event browse, event detail, checkout, organiser signup, and the help centre.

Every public page is gated by an automated axe-core scan in our continuous integration pipeline, with a target of zero violations before merge to the main branch. Manual testing covers keyboard-only navigation, screen-reader usage, and reduced-motion behaviour.

How we build

Our standing engineering practices include:

• Semantic HTML and ARIA only where native HTML is insufficient.
• Visible focus states on every interactive element, never removed.
• Touch targets of at least 44 by 44 pixels on mobile surfaces.
• Colour contrast at WCAG AA on body text and UI controls.
• Respect for the prefers-reduced-motion media query on every animation.
• Form fields that announce their label, state, and validation errors to screen readers.
• Captions and transcripts on any video content we publish.
• Plain-language copy. No jargon-as-progress.

Known limitations

We publish known limitations rather than hide them. As of the date above, the platform has the following accessibility limitations on our active backlog:

• Some third-party event imagery uploaded by organisers may lack descriptive alt text. We are rolling out organiser-side prompts to require alt text at upload.
• The interactive map view on city pages is being rebuilt with a fully keyboard-navigable list view as the default presentation.
• A small number of legacy event detail pages still use a hero with decorative animation. Reduced-motion is respected, and these are on a planned rebuild path.

These items are tracked publicly in our engineering log and will be cleared progressively before national launch.

Request a reasonable adjustment

If you need a reasonable adjustment to use EventLinqs, including alternative formats, additional time, or a different way of completing a checkout or organiser onboarding flow, contact us at hello@eventlinqs.comwith the subject line "Accessibility request". We aim to respond within one business day, Australian Eastern time.

Requesting an adjustment never affects the price you pay, the availability of tickets shown to you, or your standing on the platform.

Report a barrier

If you encounter a barrier on the platform, please report it. We need to know about it so we can fix it. Email hello@eventlinqs.comwith the subject line "Accessibility barrier" and as much of the following as you can share:

• The page URL where the barrier occurred.
• What you were trying to do.
• The device, browser, and assistive technology you were using.
• What you expected to happen and what happened instead.

We treat every report as a defect ticket. We will acknowledge receipt, share an investigation outcome, and tell you when the fix has shipped.

Legal context

EventLinqs is operated by an Australian sole trader (ABN 30 837 447 587) registered in Geelong, Victoria. We are subject to the Disability Discrimination Act 1992 (Cth) in Australia, and we align our accessibility practice with the World Wide Web Consortium's Web Content Accessibility Guidelines 2.1 at Level AA.

This statement is reviewed and updated as the platform evolves. The date at the top of this page reflects the most recent review.