Accessibility at Zenna
Last updated: August 31, 2026Zenna is the hiring platform built by Rokstars Global HRM. Accessibility is not a feature we added to it. It is one of the requirements we started with, and it shapes how every page, form, and workflow is built.
We build this way for a straightforward reason. When a product works for the people with the hardest access needs, it works better for everyone. Designing so that someone using only a keyboard, or only a screen reader, can finish a task from start to end means the same task is clearer and faster for every other person too, including anyone on a phone, in bright sun, on a slow connection, or working one handed.
The standards we hold ourselves to
Zenna serves employers and candidates in both Canada and the United States, and we design and test against the recognized standards in both:
- Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the international standard set by the World Wide Web Consortium.
- The Accessibility for Ontarians with Disabilities Act (AODA), Ontario's law covering accessible information and services.
- The Americans with Disabilities Act (ADA), the United States civil rights law covering access to digital services.
Who we build for
Accessibility is often talked about as if it means one group. It does not. The work reaches many different people:
- People who navigate by keyboard instead of a mouse, whether from a motor or mobility condition, tremor, repetitive strain, or simple preference.
- People who are blind or have low vision and use a screen reader or magnification.
- People who need clear structure, plain labels, and predictable behaviour, including many with cognitive or learning differences.
- People who cannot rely on colour to carry meaning.
- Anyone facing a temporary or situational limit, from a broken arm to a bright screen to a one handed moment.
Building for the first people on that list is what opens the door for the rest.
If you need an accommodation
Applying should never mean choosing between your privacy and your shot at a role. If you need an accommodation at any point in the hiring process, use the Accessibility and accommodations section on the role you are interested in, and tell us what would help.
Asking changes nothing about your candidacy. An accommodation request is never scored by Zenna, it never counts against you, and it plays no part in deciding on a candidate who is qualified for the role. And it does not vanish into an inbox. A real advisor reviews every request, takes ownership of it, and gets back to you. Your request has a person's name on it.
What we have built into the platform
This is not a checklist we ran once. These are things the platform actually does, on the pages a candidate or a client uses every day:
- Full keyboard access. Every interactive element, menu, and dialog can be reached and operated without a mouse.
- Tested with real assistive technology, including JAWS, NVDA, and VoiceOver, not automated scanners alone.
- Semantic structure. Real headings, real lists, and page landmarks, so a person can move through a page by its structure instead of reading every word.
- Controls that say what they do. Every link and button carries meaningful text. There is no "click here" and no unlabelled button.
- Labelled forms with clear errors. Every field is properly labelled, and when something is wrong the message is specific and announced, not just a red outline.
- Announced updates. When the platform saves, changes a status, or loads new information, that change is announced as it happens, so nothing changes silently.
- Dialogs that behave. Pop-up dialogs move focus to their heading when they open, close on the Escape key, return focus to where you were when they close, and hold the rest of the page still behind them, so you are never lost.
- Meaning never carried by colour alone. Where colour signals something, text and shape carry the same message. A candidate's fit score, for instance, always appears as a number, a colour, and a written label together, so it reads clearly whether or not you can see colour.
- Sufficient contrast. Text, headings, and controls meet the WCAG 2.1 AA contrast minimums.
- A choice of light or dark mode, so each person can pick the brightness and contrast that suits them.
Tested by people, not only tools
Automated checkers catch some issues and miss many. So the platform is reviewed and tested by people who use assistive technology in their daily lives, and accessibility is checked as the platform changes, not signed off once and forgotten.
An ongoing commitment
Accessibility is never finished, because the platform keeps growing. As we add features, we build and test them to the same standard. When we find a barrier, we treat it as a defect to fix, not an optional extra. We would rather hear that something did not work for you than have you quietly give up on it.
Assistive technology we test with
- JAWS with Chrome and Edge on Windows
- NVDA with Chrome and Firefox on Windows
- VoiceOver with Safari on macOS and iOS
- TalkBack with Chrome on Android
- Keyboard-only navigation across all major browsers
Tell us about a barrier
If any part of Zenna is difficult or impossible for you to use, we want to know, and we will help. Email us at team@zennahr.com and we respond within one business day.
Formal complaints
If you are not satisfied with how we have responded, you can contact the accessibility body in your jurisdiction:
- In Ontario, Canada: the Accessibility Directorate of Ontario, which handles complaints under the AODA.
- In the United States: the United States Department of Justice, which receives ADA complaints about digital accessibility.