Accessibility

Last updated 10 November 2026

Buzzerify should work for everyone who uses it: the staff who run a venue's queue, and the customers waiting for their order. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

How we check

• Automated accessibility checks (axe) run against WCAG 2.2 level AA every time the code changes. They cover this website, sign-up and sign-in, the staff app (the queue, the counter screen, team, settings and billing) and the customer's order page.
• Pages fit a phone's screen, and animation is switched off for anyone whose device asks for reduced motion.
• We haven't had an independent accessibility audit yet. Until we do, these checks are our own.

If you can't hear the buzzer

The buzzer rings with sound, so it also tells customers in other ways:

• The order page changes to a large "READY" with the order number, and the browser tab's title says it's ready.
• On Android, the page can show a notification when the order is ready, and the phone vibrates while the page is on screen.
• Where the venue has switched texts on, a customer can ask for a text when the order is ready.
• Staff can see on their screen whether the customer has seen that the order is ready, and the queue tells them when to call the number out.

What we know doesn't work as well

• An iPhone can only be rung while the order page stays open. Closing the tab, or stopping its sound, means it can't ring. The page says so.
• iPhones don't let web pages vibrate. A customer who can't hear the ring on an iPhone relies on the screen, a text where the venue offers one, or staff calling the number out.
• The counter screen shows numbers in large type but makes no sound.

Tell us about a problem

If part of Buzzerify doesn't work for you, email hello@buzzerify.com and tell us the page and what happened. We'll reply and tell you what we can do about it.

If you're not satisfied with our response, you can contact the Australian Human Rights Commission (humanrights.gov.au).