Accessibility Statement

1. Our commitment

We want everyone to be able to use our products, including people who use screen readers, keyboard-only navigation, magnification, voice control or other assistive technology. Accessibility is treated as part of building the product, not as a later cleanup.

2. The standard we work to

We aim to meet WCAG 2.1 Level AA across levier.co.za and all LEVIER products. In practice that means:

• Text contrast of at least 4.5:1, and 3:1 for large text and meaningful interface elements.
• Every interactive control reachable and operable by keyboard, with a visible focus indicator.
• Semantic HTML and ARIA where needed, so screen readers announce structure and state correctly.
• Meaningful text alternatives for images, icons and charts.
• Form fields with associated labels, and errors described in text rather than colour alone.
• Never using colour as the only way information is conveyed.
• Layouts that reflow without horizontal scrolling down to 320 px wide, and remain usable at 200% zoom.
• Respecting the prefers-reduced-motion setting for animation.
• Touch targets of at least 44 × 44 px on mobile.

3. Current status

We assess our products against WCAG 2.1 AA using a combination of automated testing, keyboard walkthroughs and screen reader checks. Conformance varies by product and by screen. We consider our marketing pages substantially conformant, and our application interfaces partially conformant — meaning most of the standard is met, with known exceptions below.

4. Known gaps we are working on

We would rather tell you where we fall short than claim conformance we have not verified. Current known issues:

• Data-dense tables in Count and Build can be difficult to navigate with a screen reader when many columns are visible. We are adding proper header associations and a simplified view.
• Map interfaces in Transport rely on a third-party mapping component whose keyboard support is limited. We are adding a text-based list view of the same information as an equivalent alternative.
• Charts and dashboards do not yet all expose their underlying values as text or a data table.
• Merchant storefronts on Sell are partly controlled by the merchant, who can supply their own images and copy. We provide accessible templates and components, but we cannot guarantee that every merchant supplies alternative text.
• Some animated transitions on marketing pages need finer prefers-reduced-motion handling.

5. What we test with

We test against current versions of Chrome, Safari, Firefox and Edge, using VoiceOver on macOS and iOS and NVDA on Windows, plus keyboard-only navigation. If you use a different combination and hit a problem, please tell us — it helps us widen coverage.

6. Tell us about a barrier

If something on our sites or in our products is difficult or impossible for you to use, email admin@levier.co.za. It helps if you can include:

• The page or screen where it happened, with a URL if you have one.
• What you were trying to do.
• The browser, operating system and assistive technology you were using.

We aim to acknowledge accessibility reports within 5 working days and to give you a fix or a workaround, with a timeframe, within 20 working days.

7. Getting help another way

If you cannot complete something in the product because of an accessibility barrier, contact us and we will help you complete it another way — by email or over the phone — at no extra cost, while we work on the underlying fix.

8. Review

We review this statement at least annually, and whenever we ship a significant interface change. The effective date above reflects the last review.