ShareCraft

Accessibility statement

Accessibility statement for ShareCraft.org · Last updated: 11 September 2026

ShareCraft is built for the Australian social sector. Many of the people who use it, and many of the people they work alongside, have a disability. A platform for this sector that cannot be used by everyone in it is not finished.

This statement sets out the standard we hold ourselves to, where we currently fall short of it, and how to tell us when something does not work.

Our commitment

We hold ShareCraft to WCAG 2.2 Level AA, the current version of the international standard for web accessibility. We treat it as a requirement of every stage of building, not as something checked at the end.

We are not there yet. This statement says plainly where we are, what we know is not good enough, and what we are doing about it.

How well ShareCraft conforms

ShareCraft is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the platform meets the standard, but some parts do not. We would rather tell you that than claim more than we can stand behind.

What works well

  • Every part of the platform can be operated with a keyboard alone, without a mouse.
  • Every interactive element shows a clear focus indicator, so you can see where you are.
  • Dialogs and pop-up panels keep keyboard focus inside them while open, and return it where it came from when closed.
  • Images carry text descriptions, and images that are purely decorative are hidden from screen readers rather than read aloud.
  • Text meets the required contrast against its background, and no status or meaning is carried by colour alone.
  • The platform respects your system setting for reduced motion.
  • Touch targets are at least 44 by 44 pixels, comfortably above the standard’s minimum.
  • Signing in supports password managers, and offers a sign-in link by email so you never have to memorise or retype a password.

What does not yet meet the standard

We recently audited ShareCraft against WCAG 2.2 Level AA. Fixes are being developed for the issues it identified. You may notice:

  • On some forms, if an error appears and you move back to the field, the field is not announced as containing an error. The error is read out when it first appears.
  • The sign-in, sign-up and password reset pages are missing the page structure that lets you skip straight to the main content.
  • Some information pages are missing that same page structure.
  • Placeholder text inside empty form fields is lighter than the required contrast. Every field also has a permanent visible label, so no information is lost.
  • On the “Find practices and communities” page, changing a filter updates the results without announcing that they have changed.
  • Some section tabs cannot be moved between with the arrow keys. They are all reachable with the Tab key.
  • Some dialogs read out a secondary control before their title.

If any of these is getting in your way, please tell us — it helps us order the work.

Where ShareCraft is up to

ShareCraft is in beta. Communities and organisations join by invitation while we finish the platform. We have chosen to publish this statement now, during beta, rather than waiting until everything above is fixed — partly because you are entitled to know, and partly because a commitment you can hold us to is worth more than one made after the fact.

How we test

We check accessibility in three ways.

Automated checks run against our code as it is written, catching missing labels, invalid markup and structural errors.

Keyboard testing is part of reviewing any change to the interface.

Screen reader testing is done by a person, using the same software you would use — VoiceOver on macOS and iOS, NVDA and JAWS on Windows, and TalkBack on Android. We concentrate on the journeys that matter most: signing in, reading a Field Guide, taking part in a community discussion, and completing a form.

Automated tools find perhaps a third of accessibility problems, and not the most important third. They do not replace a person using the platform the way you would.

This statement is based on a self-assessment carried out on 11 September 2026. We have not yet commissioned an independent audit. We intend to, and we will say so here when we have.

What ShareCraft works with

ShareCraft is designed to work with current versions of Chrome, Edge, Firefox and Safari, on Windows, macOS, iOS and Android, together with the screen readers named above.

It relies on HTML, CSS, JavaScript and WAI-ARIA. If JavaScript is turned off, parts of the platform will not work. We do not test older browsers, and some things may not work correctly in them.

Tell us if something does not work

If any part of ShareCraft is difficult or impossible for you to use, please tell us. You do not need to know why it is happening, or use any particular words to describe it — “I can’t get past the sign-in page with my screen reader” is a perfectly good report, and more useful to us than most.

Email support@sharecraft.org

Please tell us what you were trying to do, which page you were on, and what happened. If you know which browser and assistive technology you were using, that helps, but it is not necessary.

We will acknowledge your message within two business days and tell you what we intend to do and by when. If we cannot fix something quickly, we will say so honestly and offer another way to get what you need in the meantime.

If you need information held on ShareCraft in a different format — large print, plain text, or another accessible format — ask us and we will provide it.

If we do not get it right

We take this seriously and we would rather hear from you directly so we can fix it. If you are not satisfied with how we respond, you can contact the Australian Human Rights Commission, which handles complaints about disability discrimination under the Disability Discrimination Act 1992 (Cth).

humanrights.gov.au/complaints

Keeping this statement honest

We review this statement at least every six months, and whenever we make a significant change to the platform or fix something listed above.

A statement that is out of date is worse than no statement, because it tells you something untrue. If you find something on this page that no longer matches your experience — in either direction — please tell us.