Accessibility
Teamer should work for everyone in a course.
Last updated June 2026
University staff and students use Teamer in all sorts of ways, including by keyboard, with a screen reader, and with larger text or higher contrast. We build and test with that in mind so the platform is usable however someone gets there.
The standard we follow
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard most Australian universities procure against. We check our work with automated tooling and with manual keyboard and screen-reader testing, not just one or the other.
What that means in practice
Pages are built with proper headings and landmarks, so a screen reader can move through them in a sensible order. Every page has a unique title and a skip-to-content link for people who navigate by keyboard.
Interactive elements are reachable and operable by keyboard, with a focus outline that is always visible. Text and interface colours meet AA contrast, images and icons carry text alternatives, and forms have clear labels and error messages. Animations step aside when your system is set to reduce motion.
Where we are still working
Teamer is built and maintained by a small team, and accessibility is reviewed as new features ship rather than treated as a one-off. Some richer interactions, like arranging teams, are the areas we keep the closest eye on. If something is not working for you, telling us is the fastest way to get it fixed.
Tell us about a barrier
If you hit an accessibility barrier in Teamer, email with the page and what happened, and we will work with you to fix it. You can also read our page.