Our commitment
Colleges and universities serve every student, so Rook has to work for every student and staff member too. Accessibility is part of how we design, build, and test Rook, not a later fix.
The standard we follow
We build rook.work and every school's Rook site to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That goes beyond WCAG 2.1 AA, the level required by the Department of Justice's 2024 rule under Title II of the Americans with Disabilities Act, and it supports schools' Section 508 and procurement requirements.
Conformance status
Rook partially conforms to WCAG 2.2 Level AA. "Partially" means some content may not yet fully meet the standard. We don't know of any failures today, but we haven't yet completed a full manual audit with screen readers, so we won't claim full conformance until we have.
What we build in
- Everything works with a keyboard, with a visible focus indicator and a "Skip to main content" link.
- Pages use real headings, landmarks, and lists, and each page has a unique title and one main heading.
- When a page changes, focus moves to its heading and the change is announced to screen readers.
- Every form field has a label; errors are listed at the top of the form and linked to their fields.
- Text and controls meet contrast minimums, and status is never shown by color alone.
- Pages reflow to 320 pixels wide and stay usable when text is enlarged to 200%.
- Animation is minimal and turns off when your device asks for reduced motion.
- Touch targets are at least 24 by 24 pixels.
Known limitations
- Automated tools catch only some accessibility problems, and our manual screen reader testing isn't complete yet.
- Photos on rook.work are decorative and have no text descriptions; nothing on the page depends on them.
- Payment pages are provided by Stripe, and email apps are outside our control.
Compatibility
Rook is designed for current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, and for use with screen readers such as NVDA, JAWS, VoiceOver, and TalkBack, keyboard-only navigation, and browser zoom.
How we check
- Self-assessment by the team that builds Rook.
- Automated axe-core checks against WCAG 2.2 AA on our pages and the job-list embed, at desktop and mobile sizes, before any change ships; a violation blocks the change.
- Accessibility linting of every screen's code.
- Manual keyboard and zoom checks as features are built.
Schools evaluating Rook can ask us for our accessibility documentation.
Feedback and help
If something in Rook doesn't work for you, email howdy@redizoo.com. Tell us the page and what happened. We'll reply within 5 business days, and we'll help you finish what you were doing another way while we fix it. We can also provide information from this site in another format on request.