Accessibility

We want everyone to be able to use SupportFinder, including people who use a screen reader, a keyboard, zoom or other assistive technology.

Last reviewed 11 October 2026.

Our aim

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on the public site and in the provider portal.

The site has not had an independent accessibility audit. We do not claim that it fully meets WCAG 2.2 AA. This page says how we check, what we know is not right yet, and how to tell us about a problem.

How we check

  • Automated checks. We run axe, an open-source accessibility checker, and our own checks for colour contrast, target size, the names of buttons and links, and form errors. They run on the main pages and on more than 100 recorded states of the public site and the provider portal, such as open menus, dialogs, error messages and search results. Each result is compared with a saved record, so a change shows up.
  • Keyboard. The checks press Tab forwards and backwards through each page and state. They check that you can see where focus is, and that it is not hidden under the bar at the top of the page.
  • Zoom and small screens. Pages are checked at widths from 320 to 1,280 pixels for content that runs off the side. A width of 320 pixels is about what a 1,280-pixel screen shows at 400% zoom.
  • Reduced motion. If your device asks for less motion, the site scrolls in one step instead of sliding.
  • Three browser engines. Phone layouts, reduced motion, focus and the colour themes are also checked in Chromium, Firefox and WebKit. These are the engines behind Chrome and Edge, Firefox and Safari.
  • What a screen reader is given. We read the names, roles and messages the page gives to assistive technology, and log where focus goes after each action. This is not the same as using a screen reader.
  • Reviews. We read the code of new features and try them with the keyboard. We look at focus, names, roles and how errors are announced. Problems found in these reviews are fixed with a test that failed first.

Automated checks find many problems, but not all of them. Passing them does not show that the site fully meets WCAG 2.2 AA.

What we have fixed recently

  • New controls measured. On 10 October 2026 we measured 52 new or changed controls at phone, tablet and desktop widths, in light and dark themes. We checked size, colour contrast, focus and names. We found five problems and fixed all of them, each with a test.
  • Focus and messages. Focus no longer drops to the top of the page when a button hides itself after you press it. In the provider portal, the message after you ask to change your email is now read out. A search reads out how many providers it found.
  • Recorded states. In our October 2026 checks of the recorded states, axe found no problems. No text failed the colour contrast check, and no focused control was hidden under the bar at the top of the page.
  • Help in the same place. On 11 October 2026 we added a “Need help?” box at the bottom of every page, in the same place each time. It lists phone services for interpreters, people who are deaf or hard of hearing, First Nations people, the NDIS and the NDIS Commission.
  • Plain guides. On 11 October 2026 we added short guides for young children, leaving hospital and leaving school.

What we know is not right yet

  • No testing with assistive technology users yet. We have not tested the site with people who use screen readers, voice control or other assistive technology. We have not tested it ourselves with NVDA, JAWS or VoiceOver either. This is the biggest gap in our checking.
  • No independent audit. All of the checks on this page are our own.
  • New pages not yet in our recorded checks. The three guides and the “Need help?” box, added on 11 October 2026, are not yet part of the recorded-state checks described above.
  • New search filters. The “How is your plan managed?” and “Complex or high support needs” filters, added on 11 October 2026, have not had an accessibility review yet.
  • The map. The map on a listing uses map images from OpenFreeMap, a third party. We do not control how they look, such as the size and colour of street names. The map shows up to 25 locations. Every location is also listed as text under the map, with its address and a Directions link. If the map does not load, the list still works.
  • Focus in other browsers. The full Tab walk runs in Chromium only. Firefox and Safari have their own tests for problems we have found before, but not a full walk.
  • Older browsers. In browsers older than Chrome 105, Safari 15.4 or Firefox 121, a focused link or button can sit under the bar at the top of the page.
  • Spelling suggestions. When you type a place in the Near field, some screen readers may not read the “Did you mean” label above suggested spellings. The words are on screen, and the error message also says “Did you mean”.
  • Words from providers and registers. Descriptions and service details come from providers and public registers. We show them as given, so they may not be in plain English.

Other formats and getting help

We do not have Easy Read, Auslan, audio or large print versions of the site. If you need information from SupportFinder in another format, email contact@supportfinder.io and say what would help, so we can work out what is possible.

We do not have our own phone line. Email is the only way to contact us. A family member, carer, support coordinator or advocate can email us for you.

If you would rather talk to someone, the “Need help?” box at the bottom of this page lists phone services. For an interpreter, call TIS National on 131 450. If you are deaf or hard of hearing, or have a speech impairment, the National Relay Service can help you make a call.

Report an accessibility problem

Email us about an accessibility problem, or write to contact@supportfinder.io. It helps to tell us:

  • the page, or what you were looking at
  • what you were trying to do, and what happened
  • your device and browser, and any assistive technology you use.

Sam Young handles these reports. We may write back to ask a question or to tell you what changed. We do not promise a time for a reply or a fix.

If you are not happy with how we respond, you can contact the Australian Human Rights Commission.

A concern about the care a provider gives is not an accessibility problem with this site. The NDIS Commission handles those: Provider conduct concerns.

Who runs SupportFinder

Operated by Sam Young, a sole trader trading as Support Finder. ABN 73 921 039 985. Contact

Menu

Appearance