Accessibility.
In force from 16 September 2026
The short version
Board Badger is built to WCAG 2.2 at level AA. It has not been independently audited, and nothing here has been tested with a screen reader user, only with automated tools.
Every page works from the keyboard, nothing is dragged, and colour never carries a meaning on its own. Contrast and labels are checked automatically on every build. Report a barrier to hello@boardbadger.com.
This summary is here to be read. The clauses below are what actually binds.Board Badger is meant to be usable by anybody with a client project to run, and by anybody at the client who has been sent a link to one. This statement sets out the standard it is built to, what is in place, and what is not.
The standard
Board Badger is built to WCAG 2.2 at level AA. It has not been independently audited, so this is the standard it is built to rather than a certified result, and it is stated that way deliberately.
Measures in place
- Every page is operable from the keyboard, and the focus indicator is always visible.
- Headings, lists, tables and form labels are real markup, so assistive technology receives the same structure a sighted reader does.
- Nothing is dragged. A task moves between its three states by pressing a button that names the state, which is the one interaction a pointer-only gesture would have made impossible.
- Colour never carries a meaning on its own. A task's state is written out in words beside it.
- There is one sheet, and it is the same for everybody. Nothing depends on a setting a reader has to find.
- There is no animation, no carousel, no automatic movement and no timed content.
- The service works at any window width down to a phone, and text can be enlarged without the layout breaking.
What is checked automatically
The standard above is a statement of intent, so these are the parts of it a machine can decide, checked on every build. The measurements are taken from the colours this page is printed in, not copied from a report.
| Criterion | What is checked |
|---|---|
| 1.4.3 Contrast (minimum) | Every colour the stylesheet sets text in is measured against the worst ground it can be printed on. The build reads those colours out of the stylesheet itself and refuses one that is not in the table below. |
| 1.4.1 Use of colour | A task's state and how long it has waited are both spelled out in words on the row, so no meaning is carried by colour alone. The words are read off the rendered board. |
| 3.3.2 Labels or instructions | Every visible input on every public page carries a label or an aria-label, read off the rendered markup rather than off the component that printed it. |
| 4.1.2 Name, role, value | Anything that changes something is a form with a button, never a link. Signing out is the one on every page, and it is read off the markup too. |
The contrast measurements
Every colour the stylesheet sets text in is measured against the ground, which is the darker of the two surfaces, so a pairing that clears it clears both. The two rows with a floor of 3 are not text: they are the edge of a field you type into and the ring that marks what the keyboard is on. A control bounded by a hairline rather than a field edge, such as the button that revokes somebody, is identified by the words written on it, and its box is not measured here.
| Pairing | Needs | Measures |
|---|---|---|
| Body text against the ground | 4.5 to 1 | 16.65 to 1 |
| The quieter text beside it, against the ground | 4.5 to 1 | 5.54 to 1 |
| A count or a caption, against the ground | 4.5 to 1 | 4.63 to 1 |
| The owner's side, against the ground | 4.5 to 1 | 7.27 to 1 |
| The client's side, against the ground | 4.5 to 1 | 7.70 to 1 |
| Settled, against the ground | 4.5 to 1 | 5.80 to 1 |
| Reversed out of the accent | 4.5 to 1 | 4.54 to 1 |
| Reversed out of the accent as the pointer rests on it | 4.5 to 1 | 5.77 to 1 |
| Reversed out of the owner's side | 4.5 to 1 | 7.93 to 1 |
| Reversed out of the ink, on a chosen state | 4.5 to 1 | 18.15 to 1 |
| Initials in the badger's butter | 4.5 to 1 | 4.75 to 1 |
| What the badger says, in his butter | 4.5 to 1 | 6.61 to 1 |
| The quieter text on a code ground | 4.5 to 1 | 5.18 to 1 |
| Under a week, in its own chip | 4.5 to 1 | 5.47 to 1 |
| One to two weeks, in its own chip | 4.5 to 1 | 5.18 to 1 |
| Two to four weeks, in its own chip | 4.5 to 1 | 4.75 to 1 |
| Over a month, in its own chip | 4.5 to 1 | 5.30 to 1 |
| Over a month, against the ground | 4.5 to 1 | 6.43 to 1 |
| Settled, in its own chip | 4.5 to 1 | 5.47 to 1 |
| The accent as words, against the ground | 4.5 to 1 | 5.29 to 1 |
| Transcript text on its dark ground | 4.5 to 1 | 15.87 to 1 |
| A reply in the transcript | 4.5 to 1 | 6.86 to 1 |
| A label in the transcript, on its darker bar | 4.5 to 1 | 5.99 to 1 |
| A label in the transcript | 4.5 to 1 | 5.84 to 1 |
| The prompt in the transcript | 4.5 to 1 | 4.58 to 1 |
| The edge of a field you type into, against the ground | 3.0 to 1 | 3.35 to 1 |
| The focus ring, against the ground | 3.0 to 1 | 4.17 to 1 |
What the automated pass does not decide
An audit that lists only what it covers reads as a clean bill of health, and this is not one. Automated checking is not an audit and does not substitute for one.
- Whether a heading actually describes what follows it.
- Whether the reading order makes sense when the layout is ignored.
- Whether an error message says what to do next rather than only what went wrong.
- Whether anything here works for somebody who is actually using a screen reader.
Known limitations
- The bar on each board in the list of boards is a drawing of two counts. It is named with both figures and the two numbers are printed beside it, but it is not described segment by segment.
- On a board, the control that hands a task over appears when the pointer or the keyboard reaches that task, and is always shown on a touch screen.
- The command line is a single text field with no suggestions. Somebody who cannot remember the wording has to use the buttons instead, which all do the same jobs.
- Email is plain and simple, but has not been tested in every mail client.
- Nothing here has been tested with a screen reader user, only with automated tools.
Reporting a barrier
Anything that gets in the way should be reported to hello@boardbadger.com, with what happened and what was being used at the time. Reports are read by the Operator and acted on. Where something cannot be fixed quickly, the reporter will be told that rather than left waiting.
Enforcement
Board Badger is a private sector service and is not subject to the public sector accessibility regulations, but the Equality Act 2010 applies. Anyone dissatisfied with the response to a report may raise it with the Equality Advisory and Support Service.
Ask, and the wording gets fixed rather than explained.