Accessibility
The people who need this site are often reading it at the end of a shift on a phone. It is built to work there, with a keyboard, and with a screen reader, and we want to hear about anything that gets in the way.
Every word on this site is plain HTML that reads without scripts; the decision tree and every widget work from the keyboard and announce their state in text; controls are at least 44 pixels, body text at least 16, and colours meet contrast guidance. If something here does not work for you, write to hello@wguirb.com and we will fix it or give you the content another way.
How the site is built
- Readable without scripts. Every page is static HTML; the tree's four landings, the questions and the answers, the packages and the forms are all in the page before any script runs.
- Semantic structure. One heading at the top of each page, headings in order beneath it, landmarks for the masthead, main content and footer, labelled navigation, and a breadcrumb on every inner page.
- The decision tree by keyboard. Each fork's choices are buttons reachable with Tab and operated with Enter or Space; the current state ("fork 2, identifiers", "landing: likely exempt") is written in text in a live region as you go, and the reading appears beneath the tree in text. On a small screen the drawing scrolls sideways inside its own container; the page itself never does.
- Forms. Every field has a visible label, required fields are marked, status messages are announced, and inputs are at least 16 pixels so phones do not zoom.
- Chat, offer and menu. The chat launcher and panel, the seasonal offer and the mobile menu carry their expanded state, close on Escape, keep focus inside the dialog while it is open and return focus when it closes. The offer never opens the instant the page loads.
- Type and contrast. Body text is 17 pixels on a light ground; text and interactive colours are chosen to meet WCAG 2.1 AA contrast, including the light text on the dark footer.
- Motion. There is no autoplaying media and no animation beyond short transitions; nothing flashes.
- Drawings. Every drawing is an inline SVG with a text description, and nothing it shows is shown only in the drawing; the same fact is in the prose beside it.
Known limits
The tree's state is announced as it changes, but a screen reader user may find it quicker to use the fifteen written answers on the questions page, which cover the same four forks in prose. The chat depends on a network connection to the desk; if it cannot connect, it says so and points you to the form and the email address, both of which work without it.
Tell us
If any part of this site does not work with your browser, device or assistive technology, write to hello@wguirb.com and say what you were trying to do. We will fix what we can and, in the meantime, give you the content in another form. This page is revised as the site changes; last revised 23 August 2026.