Accessibility statement
Accessibility.
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 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 ground it is 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 is spelled out in words beside it, 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
| Pairing | Needs | Measures |
|---|---|---|
| Body text on the stock | 4.5 to 1 | 14.86 to 1 |
| The quieter text on the stock | 4.5 to 1 | 8.45 to 1 |
| A link and a label, printed in the plate | 4.5 to 1 | 6.49 to 1 |
| The second plate, which only means something is wrong | 4.5 to 1 | 5.10 to 1 |
| Placeholder text, and a name whose access has ended | 4.5 to 1 | 4.64 to 1 |
| A tool call, printed in the plate on its tinted block | 4.5 to 1 | 5.69 to 1 |
| The quieter text on that same tinted block | 4.5 to 1 | 7.40 to 1 |
| The stock reversed out of the plate | 4.5 to 1 | 6.49 to 1 |
| The quieter text reversed out of the plate | 4.5 to 1 | 4.73 to 1 |
| The stock reversed out of the second plate | 4.5 to 1 | 5.10 to 1 |
| The edge of a field or a button against the stock | 3.0 to 1 | 6.49 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 done line on the home page is a drawing of a count. The list beneath it carries the same information and is the accessible equivalent, but the drawing itself is not described mark by mark.
- 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.