leadably.io
Legal

Accessibility statement

Effective date: 20 May 2026 · Version 2.0 · Last reviewed: 20 May 2026

Leadably is committed to making leadably.io (the "Site") — and every website we ship for clients — usable by the widest possible audience, including people with disabilities. Accessibility is not a checklist we apply at the end of a project; it is a constraint we design from the first wireframe.

1. Conformance target

We target compliance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as published by the World Wide Web Consortium (W3C). Our approach aligns with:

  • the Disability Discrimination Act 1992 (Cth) and the Australian Human Rights Commission's World Wide Web Access: Disability Discrimination Act Advisory Notes;
  • the EU Web Accessibility Directive (Directive (EU) 2016/2102) and Harmonised Standard EN 301 549 V3.2.1, where the Site is accessed from the EEA;
  • UK Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, where relevant to public-sector client engagements;
  • Title III of the United States Americans with Disabilities Act (ADA) as currently interpreted by US federal courts in relation to commercial websites.

Where a client engagement specifies a higher standard (for example WCAG 2.2 AAA, or a specific public-sector procurement requirement), the Engagement Agreement governs.

2. Measures we take

To meet that target on the Site, we apply the following measures on an ongoing basis:

  • Semantic HTML — landmarks, headings, lists, buttons and links are used for their actual semantic purpose, not styled into generic <div> elements.
  • Colour contrast — text/background pairs meet or exceed the 4.5 : 1 contrast ratio required by WCAG AA, and 3 : 1 for large text and meaningful non-text content.
  • Keyboard support — every interactive element, including custom components, modals and accordions, can be reached and operated using a keyboard alone, with a logical focus order.
  • Visible focus — a clearly visible focus indicator is shown on every interactive element when keyboard-focused.
  • Reduced motion — entrance animations, parallax, smooth-scroll and decorative motion are disabled for visitors with prefers-reduced-motion.
  • Screen-reader friendly markup — ARIA labels, roles and states are added only where native HTML cannot do the job, and they are tested with screen readers rather than guessed.
  • Touch targets — interactive controls measure at least 44 × 44 CSS pixels on touch devices, in line with WCAG 2.2 Success Criterion 2.5.8 (Target Size — Minimum).
  • Form accessibility — every form field has a programmatically associated label, errors are announced to assistive technology, and validation messages are descriptive rather than colour-only.
  • Alternative text — informative images carry meaningful alt text; decorative images are marked as such so they are skipped by screen readers.
  • Language declared — the document language is set in <html lang> so assistive technology renders text correctly.
  • Resizable text and zoom — content reflows up to 200% zoom without horizontal scrolling on common break-points, per Success Criterion 1.4.10 (Reflow).

3. Compatibility

The Site is designed to be compatible with the current and previous major versions of:

  • Apple Safari (macOS and iOS) with VoiceOver;
  • Google Chrome (Windows, macOS, Android) with TalkBack and ChromeVox;
  • Microsoft Edge (Windows) with Narrator;
  • Mozilla Firefox (Windows and macOS) with NVDA or JAWS;
  • Windows Magnifier, macOS Zoom and other OS-level magnification utilities.

We do not test against browsers more than two major versions old, or against unsupported operating systems. Some features may degrade gracefully but are not actively maintained on those platforms.

4. Known limitations

Despite our best efforts, some content on the Site may not yet be fully accessible. We are aware of, and working to remediate, the following:

  • Embedded 3D scenes (e.g. Spline-hosted hero visuals) are decorative and are paused onprefers-reduced-motion, but the underlying canvas may not expose meaningful alternative text to all screen readers. A text alternative describing the scene is provided in the surrounding markup.
  • Client case-study screenshots may include text-in-image that is not always replicated in a body-text equivalent. Where this affects comprehension, please request a transcript using the contact route below and we will provide one within five business days.
  • Third-party embeds (such as forms, payment widgets or analytics) inherit the accessibility of the provider's product. We choose providers based on documented accessibility conformance, but cannot guarantee parity in every case.

5. Feedback and reporting a barrier

We welcome feedback. If you encounter any accessibility barrier on the Site — or on a site we have built for a client — please contact us:

  • Email: hello@leadably.io with the subject line "Accessibility".
  • In your message, please tell us: the page URL, the device/operating system/browser/assistive technology you were using, a description of the problem, and what you were trying to do.

We will acknowledge accessibility reports within two (2) business days. We aim to resolve confirmed accessibility issues within fourteen (14) days, or to provide a written remediation timeline where a fix requires more time. There is no charge to you for reporting or for accessing the alternative format of any content we provide.

6. Alternatives

If part of the Site is not accessible to you, we will provide the information you need in an alternative format on request, free of charge. Options include plain-text email, accessible PDF, a structured Word document, or a real-time conversation. Please specify your preferred format.

7. Formal complaint and escalation

If we have not adequately addressed your concern, you may escalate to the relevant body in your jurisdiction:

  • Australia — Australian Human Rights Commission (AHRC), which handles complaints under the Disability Discrimination Act 1992 (Cth): humanrights.gov.au.
  • European Economic Area — the national enforcement body designated under the Web Accessibility Directive in your country.
  • United Kingdom — the Equality Advisory and Support Service (EASS).
  • United States — the U.S. Department of Justice, Civil Rights Division (ADA).

8. Evaluation methodology

Our accessibility position is evaluated through a combination of:

  • Automated audits — Lighthouse, axe-core and Pa11y are run against every page on each deployment;
  • Manual review — keyboard traversal, screen-reader walk-through (VoiceOver, NVDA), focus-order verification, and contrast spot-checks against the design tokens;
  • User feedback — reports received via the channel in section 5;
  • Periodic full review — a complete WCAG 2.2 AA conformance review is performed at least every twelve (12) months.

9. Statement scope

This statement applies to the leadably.io domain and its sub-domains. It does not cover client-owned websites we have previously built or third-party websites linked from the Site. Each client engagement carries its own accessibility statement and remediation pathway documented in the relevant Engagement Agreement.

10. Updates

This statement was last reviewed on the date shown at the top of this page. We update it whenever we make a material change to the Site, identify a new limitation, or complete a remediation milestone.

This statement is informational and does not waive any right or remedy available to you under applicable disability, discrimination or consumer-protection law.