What we are aiming for, what we have checked, what we have not, and how to get help.
Last updated 2026-10-04. Applies to hub.woodagencylife.com and hub.warprecruit.com.
The short version. We want every agent to be able to use the Hub, and we are working toward
WCAG 2.2 Level AA. We have checked the main screens with an automated tool and fixed
what it found, but we have not had an outside audit or tested with every assistive technology, so there may be
gaps. If anything is hard for you to use, tell us. We will fix it, and in the meantime we will take your numbers by text or phone so
you are never shut out.
1. Our aim
The Wood Agency provides the Hub for its agents and for the team hubs it hosts. We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA,
on every screen an agent uses. We describe the Hub as working toward that standard, not as fully conforming to it, because we have not verified every screen
by hand.
2. What we have checked
On 2026-10-03 we ran the open-source axe-core checker (version 4.12) against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules on a phone-sized screen, plus three checks of our own that it cannot make. It covered:
the sign-in screen;
Home, Log Activity, Stats, Steps, Team (including the network board) and Profile;
the pop-ups: the updated-terms screen, the join-a-team sheet, the delete-account sheet, the add-to-home-screen sheet and the badge celebration;
the owner's Agency page, as agency and team owners see it, including its network options;
Home's “Connect your team” card, and the team code and QR code on the Team screen;
Messages: the list of conversations, a conversation (including a message that has not sent yet and the delete buttons), the new-message sheet, an owner writing an announcement, an agent who has not joined a team, and the Messages card on Home;
an owner choosing who an announcement is for, an announcement with a join button and the join screen it opens, and Home's “Who do you report to?” card;
the Terms of Use, Privacy Policy and this Accessibility Statement.
Our own three checks: every form field has a real label (a placeholder is not a label, and the automated tool accepts one), nothing can be used with a mouse or finger but not a keyboard, and every button and link has a name.
What those checks found, and we fixed: faded text colors without enough contrast; 28 form fields on Log Activity and Profile that a screen reader would have announced as “0” or as nothing at all; the 32 activation steps, which could be ticked off by tapping but not by keyboard; and pop-ups that did not take keyboard focus. They report no remaining findings on those screens. The check runs again whenever we release a change.
An automated check finds only part of the problems a person can run into. It cannot tell whether a screen makes sense when read aloud, or whether the order of a page is logical.
3. What we have not checked yet
A full walk-through of every screen with a screen reader (VoiceOver on iPhone, TalkBack on Android) and with a keyboard alone.
Messages with a screen reader. New messages in an open conversation are announced by a live region, and every control has a name, but nobody has used Messages with VoiceOver or TalkBack yet.
A by-hand walk-through of the owner's Agency page. It has had the automated checks, but nobody has used it with a screen reader.
An audit by an outside accessibility specialist.
Switch access, voice control and screen magnifiers. We have not tested them.
4. How the Hub is built to help
Zoom and text size: you can pinch to zoom and the Hub follows your system text size; pages reflow to a phone screen without sideways scrolling.
Contrast and targets: text meets the 4.5:1 contrast ratio on the screens we checked, and buttons and links meet the minimum touch-target size.
Labels and errors: form fields have labels, and sign-in and save problems are announced to screen readers when they happen.
Keyboard: the controls on the screens we checked can be reached and used with a keyboard. The dial counter also answers to the Space, C, A and Z keys.
Pop-ups: when one opens, keyboard focus moves into it and stays there until you close it with Esc or its button, and then returns to where you were. The updated-terms screen is the one exception to Esc, because it has to be answered.
Messages: opening a conversation puts keyboard focus on its Back button, Esc goes back to the list, and on a computer Enter sends a message while Shift+Enter starts a new line. Message text is 16 pixels or larger (names and times are 12), and a message that did not send says so in words and offers a retry.
QR code: the team link's QR code comes with a text description, and the same link and team code are written out beside it, so nothing depends on being able to scan.
Another way to enter numbers: you never have to tap the counter. Log Activity lets you type your numbers into labeled boxes instead.
Motion: the Hub respects your device's “reduce motion” setting.
No time limits on reading or entering anything.
5. Known limits
The Hub has no “skip to main content” link. It uses headings and landmarks instead.
Charts and badge artwork are visual. If one is hard for you to use, we will give you the same information as text.
The Hub links to pages we do not run (Zoom, WhatsApp, GroupMe, carrier and licensing portals). Their accessibility is up to them.
We build for current versions of common browsers and test mostly in Chrome. Older browsers may not work well.
6. If something does not work for you
Tell us what you tried, what happened, and the device and browser if you know them. We will fix it, and we aim to answer within five business days.
Until it is fixed we will take your numbers by text or phone so you can still be counted, and we will give you any information the Hub shows in whatever form works for you.