Accessibility
What is done,
and what is not.
This is a statement of practice, not a certificate. Nobody outside this business has audited OneBookPlus against WCAG 2.1 Level AA, so we do not say we meet it. Below is the work that is genuinely in the software, the gaps we already know about, and the one thing you can do that fixes things fastest.
The standard we work to
We build toward the Web Content Accessibility Guidelines 2.1 at Level AA, which is the level Australian government and industry guidance points at, and we take the Disability Discrimination Act 1992 as the reason rather than the ceiling. Working toward a standard and meeting it are different things, and the difference is the whole point of the second list on this page.
In place today
Every item here is something in the shipped code that can be pointed at, not something we intend to do.
Skip to main content
The first thing the keyboard reaches on every page is a skip link, so a keyboard or switch user does not have to tab through the whole navigation to get to the page.
A visible focus ring, everywhere
A single global rule draws a two-pixel brand outline on whatever has keyboard focus, with an offset so it is not swallowed by the control's own border. It cannot be switched off per component.
Touch targets built to 44 pixels
The shared buttons, links and form controls carry a 44 pixel minimum height, which is the size a finger can hit reliably. Older screens built before that rule are still being brought up to it.
Motion that respects your settings
Every entrance animation checks the reduced-motion setting on your device first, and renders the content in place when it is on. The stylesheet cuts transitions and scroll effects at the same time.
Dates a screen reader can read
Formatted dates carry a machine-readable value alongside the human one, so assistive technology announces a real date rather than spelling out an abbreviation.
Light and dark, on every screen
Dark mode is not a partial theme applied to some pages. It is a token system, so the same page works in both, and it follows your operating system unless you override it.
Icons that do not carry meaning alone
Decorative icons are hidden from assistive technology so they are not announced as noise. A control that is only an icon carries a text label of its own.
Windows High Contrast mode
When forced colours are on, cards, badges, buttons and links get explicit borders drawn in the system colours so the structure of a page does not collapse into a flat field.
Australian English, declared
Pages declare Australian English, so a screen reader uses the Australian voice and reads GST, ABN and BAS, and currency and dates, the way they are said here.
What we know is not right yet
Published because a statement that lists only the good half is worse than no statement. If one of these is the thing standing between you and your work, say so and it moves up the list.
No independent audit, so no conformance claim
We work toward WCAG 2.1 Level AA and we have not been measured against it by anyone outside this business. Until that happens, this page will describe practice and will not claim a standard.
Colour contrast has not been checked page by page
An internal review in September 2026 found contrast failures on live pages, including a review byline on light backgrounds and the heading in the cookie consent banner in dark mode. Those are being corrected. The review was not exhaustive, so we will not tell you the rest of the site passes.
Nothing automated checks this in our build
There is no accessibility linter or automated scan between a change and production. A regression is found by a person using the software or by someone telling us, which is slower than it should be and is why the report route below matters.
The documents we generate are not tested for accessibility
Invoices, quotes and statements go out as PDFs, and those PDFs have not been tested against the accessible-document standard. If you need one in another format, ask and we will send it.
Data-heavy screens have not been walked end to end
The ledger, the reports and the calendar have been built with labelled controls, but no one has yet completed a full task on them with a screen reader from start to finish. We are not going to imply otherwise.
Some parts are not ours
Card payment fields are rendered by Stripe and follow Stripe's accessibility work rather than ours. Where an embedded component blocks you, tell us anyway: we can usually route around it.
The iOS app is a separate assessment
This statement covers the website and the web application. The iOS app carries accessibility labels throughout and inherits the system settings for text size, contrast and motion, but it has not been reviewed to the same level as the web and this page does not speak for it yet.
Tell us what blocked you
With no automated check in our build, a report from someone using the software is the fastest way a barrier gets found. It is not a favour to us and it does not need to be a polished description.
Email support@onebookplus.com.au and put the word accessibility in the subject line. Tell us the page, what you were trying to do, and what you use to get around: a screen reader and its version, keyboard only, magnification, or reduced motion. If it is easier to describe out loud than to write, say that and we will work with whatever you send.
A barrier is handled as a support request under the targets we publish, which are usually answered the same business day, Australian hours. If it stops you finishing a task with no way around it, it is treated as the top severity band, not as a suggestion for later.
If you need something we cannot fix quickly, ask for it another way. We can send an invoice, a statement or an export in a different format while the underlying screen is being fixed.
If you are not satisfied with how we handle a report, you can raise it with the Australian Human Rights Commission, which takes complaints under the Disability Discrimination Act 1992. We would rather hear from you first, but that route exists and you do not need our permission to use it.
Last reviewed and updated: by Bishal Shrestha