Legal

Accessibility

We want Home Lotts to be usable by everyone, including people who navigate by keyboard, use a screen reader, or cannot rely on colour alone. This page says what we have done and what is still imperfect.

Last reviewed: September 2026Target: WCAG 2.2 level AA

Our commitment

Home Lotts targets the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Accessibility is treated as a requirement here, not a stretch goal — a ticket tracker that only works for sighted mouse users is not much use to the people most likely to be keeping track of a dozen tickets.

This is a self-assessment. We have not carried out a full independent audit, and we do not claim a certification that nobody has issued.

What we have done

Keyboard

  • every interactive control — links, buttons, tabs, filter chips, switches, form fields and modals — is reachable and operable by keyboard, in a logical order;
  • a “Skip to content” link is the first focusable element, so you can bypass the navigation;
  • focus is visible on every control, using a high-contrast outline that does not depend on colour alone to be seen;
  • Escape closes any open dialog or navigation drawer, and focus returns to the control that opened it.

Structure and assistive technology

  • one h1 per page, with a logical heading hierarchy below it;
  • landmarks — header, nav, main, footer — labelled so they can be skipped by name;
  • each page has a distinct title that updates as you move between sections;
  • controls have accessible names, including icon-only buttons such as “Add ticket” and “Close dialog”;
  • status changes — a saved ticket, an exported file, a recorded prize — are announced in a live region rather than failing silently.

Colour and contrast

  • body text meets or exceeds a 4.5:1 contrast ratio against its background; large text meets 3:1;
  • status is never communicated by colour alone — “Winner”, “Results available” and “No prize” all carry text, and ticket status also has a text label beside the meter;
  • the digit-by-digit matching display pairs a filled style with a text summary such as “4 of 6 digits matched”, so the result is available without seeing the shading.

Motion, text and zoom

  • countdown tickers and transitions stop when Reduce motion is switched on in Profile → Preferences;
  • the operating system’s reduced-motion preference is respected automatically;
  • text reflows without horizontal scrolling at 200% zoom and at 320 CSS pixels wide;
  • layouts use relative units, so browser text-size settings are honoured.

Content

  • warnings and cautions are written as text, not conveyed by an icon alone;
  • data tables carry real headers;
  • documents on this site are written in plain English and structured with headings you can jump between.

Known limitations

We would rather list these than imply perfection:

  • Full independent audit not yet completed. The page above is a self-assessment against WCAG 2.2 AA, not a verified conformance claim.
  • Countdown tickers update every second. For a user of assistive technology who is not on the page at that moment, this can generate repeated announcements. Reduce motion removes the ticker entirely.
  • The application is client-side only. Because your data lives in browser storage, some browser privacy configurations — or clearing site data — will remove it. We provide CSV and JSON exports to mitigate this, but this is an inherent property of the design.
  • Older browsers. Interface features such as :has() require a reasonably current browser. In an older browser, some form highlighting may not appear, though the app remains usable.
  • Third-party destinations. Lotteries and retailers linked from our site are outside our control and are not covered by this statement.

Workarounds

If something on this site is difficult to use, these usually help:

  • Reduce motion — switch off the countdowns in Profile → Preferences, or set reduced motion in your operating system.
  • Zoom — every page is usable at 200% and above. If text is still too small, increase your browser’s base font size; the layout is built on relative units.
  • Export your data — “Export CSV” in Profile gives you every ticket in a plain spreadsheet that any assistive technology can read, including screen readers and Braille displays.
  • Tabular data — the printed version of a ticket page, via your browser’s print function, produces a simple text layout.
  • Contact us — if none of that works, email us and we will help you get the information you need, in a format that suits you.

Browser and device support

Tested and supported on current versions of Chrome, Edge, Firefox and Safari, on desktop and mobile. The app relies on modern CSS and JavaScript features, so very old browsers may render it imperfectly.

The app also works with JavaScript disabled for the legal and informational pages on this site — those are ordinary HTML pages. The ticket tracker itself obviously requires JavaScript, as it runs entirely in your browser.

Report a barrier

If you hit a barrier — a control you cannot reach, a contrast problem, a screen reader that announces something confusing, or a page that simply does not work for you — please tell us.

Email access@thehomelott.com with the page you were on and what happened, or use the contact page. We aim to acknowledge accessibility reports within three business days and to give you a timeframe for any fix.

Details that genuinely help: the browser and assistive technology you are using, the page URL, and the specific control or text involved. “This does not work for me” is already useful — you do not need to diagnose it.

Standards and enforcement

The Australian government requires most services, including commercial ones, to meet the Web Content Accessibility Guidelines. This site is intended to meet WCAG 2.2 level AA.

If we do not resolve an accessibility problem, you can contact the Australian Communications and Media Authority, which handles accessibility complaints. We would much rather you told us first — see the contact page.

PreviousAffiliate disclosure